原先在1.0.99时也有这个现象，后来重装了系统，又把Ventoy升级到了最新的1.1.00版，结果故障依旧。
具体描述如下：
运行环境：Windows 11 (business editions), version 23H2，台式机

每次运行到这里，2秒钟就闪退。
log.txt内容为：
[2025/01/25 15:55:41.237]
##################################################################################

############################## Ventoy2DiskX86  #############################

##################################################################################

[2025/01/25 15:55:41.237] Current Directory <D:\Program Files\Utilities\Ventoy>

[2025/01/25 15:55:41.237] Exe file path <D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe>

[2025/01/25 15:55:41.237] Current directory check OK.

[2025/01/25 15:55:41.238] Current directory:<D:\Program Files\Utilities\Ventoy>

[2025/01/25 15:55:41.238] ######### Current Ventoy Version: Ventoy2DiskX86 1.1.00 ########

[2025/01/25 15:55:41.244] id=17776/7752

[2025/01/25 15:55:41.244] PPath:<C:\Windows\explorer.exe>

[2025/01/25 15:55:41.245] PSize:<5575536 5444KB>

[2025/01/25 15:55:41.245] Lunch main process 0

[2025/01/25 15:55:41.246] Control Flag: 0 1 1

[2025/01/25 15:55:41.246] Set Ventoy FS ClusterSize 0

[2025/01/25 15:55:41.248] Windows Version: <<Windows 11 Enterprise, 64-bit (Build 22631.4751)>>

[2025/01/25 15:55:41.249]

===================== Enum All PhyDrives =====================

[2025/01/25 15:55:41.250] RegOpenKeyExA <SYSTEM\CurrentControlSet\Services\disk\Enum> Ret:0

[2025/01/25 15:55:41.250] RegQueryValueExA <Count> ret:0  Size:4 Value:10

[2025/01/25 15:55:41.250] GetPhysicalDriveCount: 10

[2025/01/25 15:55:41.251] Logical Drives: 0x32400e

[2025/01/25 15:55:41.251] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\B:, error:234

[2025/01/25 15:55:41.251] B --> -1

[2025/01/25 15:55:41.252] LogicalDrive:\\.\C: PhyDrive:7 Num:1 Offset:122683392 ExtentLength:499059261440

[2025/01/25 15:55:41.252] C --> 7

[2025/01/25 15:55:41.253] LogicalDrive:\\.\D: PhyDrive:1 Num:1 Offset:16777216 ExtentLength:14000500768768

[2025/01/25 15:55:41.253] D --> 1

[2025/01/25 15:55:41.258] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\O:, error:1

[2025/01/25 15:55:41.258] O --> -1

[2025/01/25 15:55:41.259] LogicalDrive:\\.\R: PhyDrive:5 Num:1 Offset:135266304 ExtentLength:499971522560

[2025/01/25 15:55:41.259] R --> 5

[2025/01/25 15:55:41.260] LogicalDrive:\\.\U: PhyDrive:8 Num:1 Offset:1048576 ExtentLength:250013007360

[2025/01/25 15:55:41.260] U --> 8

[2025/01/25 15:55:41.260] LogicalDrive:\\.\V: PhyDrive:0 Num:1 Offset:1048576 ExtentLength:17178820608

[2025/01/25 15:55:41.261] V --> 0

[2025/01/25 15:55:41.262] Create file Handle:0000016C \\.\PhysicalDrive0 status:0

[2025/01/25 15:55:41.262] PHYSICALDRIVE0 size 17179869184 bytes

[2025/01/25 15:55:41.263] DeviceIoControl3 error:1 dwBytes:104

[2025/01/25 15:55:41.264] Create file Handle:0000016C \\.\PhysicalDrive1 status:0

[2025/01/25 15:55:41.265] PHYSICALDRIVE1 size 14000519643136 bytes

[2025/01/25 15:55:41.266] Create file Handle:0000016C \\.\PhysicalDrive2 status:0

[2025/01/25 15:55:41.266] PHYSICALDRIVE2 size 8001563222016 bytes

[2025/01/25 15:55:41.268] Create file Handle:0000016C \\.\PhysicalDrive3 status:0

[2025/01/25 15:55:41.268] PHYSICALDRIVE3 size 4000787030016 bytes

[2025/01/25 15:55:41.270] Create file Handle:0000016C \\.\PhysicalDrive4 status:0

[2025/01/25 15:55:41.270] PHYSICALDRIVE4 size 4000787030016 bytes

[2025/01/25 15:55:41.272] Create file Handle:0000016C \\.\PhysicalDrive5 status:0

[2025/01/25 15:55:41.272] PHYSICALDRIVE5 size 500107862016 bytes

[2025/01/25 15:55:41.274] Create file Handle:0000016C \\.\PhysicalDrive6 status:0

[2025/01/25 15:55:41.274] PHYSICALDRIVE6 size 250059350016 bytes

[2025/01/25 15:55:41.276] Create file Handle:0000016C \\.\PhysicalDrive7 status:0

[2025/01/25 15:55:41.276] PHYSICALDRIVE7 size 500107862016 bytes

[2025/01/25 15:55:41.278] Create file Handle:0000016C \\.\PhysicalDrive8 status:0

[2025/01/25 15:55:41.278] PHYSICALDRIVE8 size 250047627264 bytes

[2025/01/25 15:55:41.279] Create file Handle:0000016C \\.\PhysicalDrive9 status:0

[2025/01/25 15:55:41.280] DeviceIoControl IOCTL_DISK_GET_LENGTH_INFO failed error:21

[2025/01/25 15:55:41.281] PhyDrv:0 BusType:unknown Removable:0 Size:16GB(17179869184) Sector:0/0 Name:Romex RAMDISK

[2025/01/25 15:55:41.281] PhyDrv:1 BusType:SATA Removable:0 Size:13039GB(14000519643136) Sector:512/4096 Name: WDC WD141VRYZ-02KHMB0

[2025/01/25 15:55:41.281] PhyDrv:2 BusType:SATA Removable:0 Size:8001GB(8001563222016) Sector:512/4096 Name: WDC WD8004VRYZ-02Z2CB0

[2025/01/25 15:55:41.282] PhyDrv:3 BusType:SATA Removable:0 Size:4000GB(4000787030016) Sector:512/512 Name: WDC WD4002VYYZ-02SGDB1

[2025/01/25 15:55:41.282] PhyDrv:4 BusType:SATA Removable:0 Size:4000GB(4000787030016) Sector:512/512 Name: WDC WD4002VYYZ-02SGDB1

[2025/01/25 15:55:41.282] PhyDrv:5 BusType:SATA Removable:0 Size:512GB(500107862016) Sector:512/512 Name: WDC WD5003ABYX-01WERA0

[2025/01/25 15:55:41.283] PhyDrv:6 BusType:Nvme Removable:0 Size:256GB(250059350016) Sector:512/512 Name:NVMe Samsung SSD 970

[2025/01/25 15:55:41.283] PhyDrv:7 BusType:Nvme Removable:0 Size:512GB(500107862016) Sector:512/4096 Name: Samsung SSD 980 PRO 500GB

[2025/01/25 15:55:41.283] PhyDrv:8 BusType:USB  Removable:1 Size:256GB(250047627264) Sector:512/512 Name:SanDisk Ultra USB 3.0

[2025/01/25 15:55:41.284] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\B:, error:234

[2025/01/25 15:55:41.284] Logical Drive:B  ===> PhyDrive:-1

[2025/01/25 15:55:41.285] LogicalDrive:\\.\C: PhyDrive:7 Num:1 Offset:122683392 ExtentLength:499059261440

[2025/01/25 15:55:41.285] Logical Drive:C  ===> PhyDrive:7

[2025/01/25 15:55:41.285] LogicalDrive:\\.\D: PhyDrive:1 Num:1 Offset:16777216 ExtentLength:14000500768768

[2025/01/25 15:55:41.285] Logical Drive  ===> PhyDrive:1

[2025/01/25 15:55:41.293] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\O:, error:1

[2025/01/25 15:55:41.294] Logical Drive:O  ===> PhyDrive:-1

[2025/01/25 15:55:41.294] LogicalDrive:\\.\R: PhyDrive:5 Num:1 Offset:135266304 ExtentLength:499971522560

[2025/01/25 15:55:41.295] Logical Drive:R  ===> PhyDrive:5

[2025/01/25 15:55:41.295] LogicalDrive:\\.\U: PhyDrive:8 Num:1 Offset:1048576 ExtentLength:250013007360

[2025/01/25 15:55:41.295] Logical Drive:U  ===> PhyDrive:8

[2025/01/25 15:55:41.296] LogicalDrive:\\.\V: PhyDrive:0 Num:1 Offset:1048576 ExtentLength:17178820608

[2025/01/25 15:55:41.296] Logical Drive:V  ===> PhyDrive:0

[2025/01/25 15:55:41.297] Create file Handle:0000012C \\.\PhysicalDrive8 status:0

[2025/01/25 15:55:41.304] Read MBR Ret:1 Size:512 code:183

[2025/01/25 15:55:41.306] =========== Disk8 GPT Partition 1 ============

[2025/01/25 15:55:41.307] PartTbl.PartType = {ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}

[2025/01/25 15:55:41.308] PartTbl.PartGuid = {e954ce58-f1a7-4177-b099-bc900f6cbda2}

[2025/01/25 15:55:41.308] PartTbl.StartLBA = 2048

[2025/01/25 15:55:41.309] PartTbl.LastLBA = 488308702

[2025/01/25 15:55:41.309] PartTbl.Attribute = 0x0

[2025/01/25 15:55:41.310] PartTbl.Name = Ventoy

[2025/01/25 15:55:41.310] =========== Disk8 GPT Partition 2 ============

[2025/01/25 15:55:41.311] PartTbl.PartType = {ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}

[2025/01/25 15:55:41.311] PartTbl.PartGuid = {1fd0bc29-85d5-434f-8b4c-d88b123bbee8}

[2025/01/25 15:55:41.312] PartTbl.StartLBA = 488308703

[2025/01/25 15:55:41.313] PartTbl.LastLBA = 488374238

[2025/01/25 15:55:41.313] PartTbl.Attribute = 0xc000000000000001

[2025/01/25 15:55:41.314] PartTbl.Name = VTOYEFI

[2025/01/25 15:55:41.314] PhysicalDrive8 is ventoy disk

[2025/01/25 15:55:41.315] QueryDosDeviceA success \Device\Harddisk8\DR10

[2025/01/25 15:55:41.317] [0] CreateFileA \\.\PhysicalDrive8 code:0 00000174

[2025/01/25 15:55:41.317] Parse FAT fs...

[2025/01/25 15:55:41.323] attach media success...

[2025/01/25 15:55:41.486] GetVentoyVerInPhyDrive rc=0...

[2025/01/25 15:55:41.487] VentoyVerInPhyDrive 8 is <1.0.99>...

[2025/01/25 15:55:41.490] PhyDrive 8 is Ventoy Disk ver:1.0.99 SecureBoot:1

[2025/01/25 15:55:41.490] LogicalDrive:\\.\U: PhyDrive:8 Num:1 Offset:1048576 ExtentLength:250013007360

[2025/01/25 15:55:41.491] Find the partition 1 logical drive is U:\

[2025/01/25 15:55:41.491] GetVolumeClusterSize U:\ SUCCESS 8 512 4096

[2025/01/25 15:55:41.492] GetVentoyFsNameInPhyDrive 8 U:\ <NTFS> <NTFS>

[2025/01/25 15:55:41.492] <Romex RAMDISK> is filtered for not USB type.

[2025/01/25 15:55:41.492] < WDC WD141VRYZ-02KHMB0> is filtered for not USB type.

[2025/01/25 15:55:41.493] < WDC WD8004VRYZ-02Z2CB0> is filtered for not USB type.

[2025/01/25 15:55:41.493] < WDC WD4002VYYZ-02SGDB1> is filtered for not USB type.

[2025/01/25 15:55:41.494] < WDC WD4002VYYZ-02SGDB1> is filtered for not USB type.

[2025/01/25 15:55:41.494] < WDC WD5003ABYX-01WERA0> is filtered for not USB type.

[2025/01/25 15:55:41.494] <NVMe Samsung SSD 970> is filtered for not USB type.

[2025/01/25 15:55:41.495] < Samsung SSD 980 PRO 500GB> is filtered for not USB type.

[2025/01/25 15:55:41.554] Load languages from json file ...

[2025/01/25 15:55:41.555] language json file len:276765 json parse:0

[2025/01/25 15:55:41.556] Total 51 languages ...

[2025/01/25 15:55:41.619] Combox select change, update secure boot option: 1 1

[2025/01/25 15:55:41.636] Courier New font <C:\Windows\Fonts\couri.ttf> exist OK.

[2025/01/25 15:55:41.636] system_dir=<C:\Windows\system32>

[2025/01/25 15:55:41.637] sysnative_dir=<C:\Windows\Sysnative>

[2025/01/25 15:55:41.638] LoadLibrary shell32.dll.mui SUCCESS

[2025/01/25 15:55:41.639] SetAlertPromptHook SUCCESS

[2025/01/25 15:55:45.415] #####################################################

[2025/01/25 15:55:45.417] UpdateVentoy2PhyDrive try1 GPT PhyDrive8 <<SanDisk Ultra USB 3.0 256GB>>

[2025/01/25 15:55:45.417] #####################################################

[2025/01/25 15:55:45.419] Lock disk for umount ............................

[2025/01/25 15:55:45.419] QueryDosDeviceA success \Device\Harddisk8\DR10

[2025/01/25 15:55:45.422] [0] CreateFileA \\.\PhysicalDrive8 code:0 000003CC

[2025/01/25 15:55:45.422] FSCTL_LOCK_VOLUME success

[2025/01/25 15:55:45.429] GPT StartSector in PartTbl:488308703

[2025/01/25 15:55:45.430] GPT Reserved Disk Space:0 MB

[2025/01/25 15:55:45.431] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\B:, error:234

[2025/01/25 15:55:45.431] LogicalDrive:\\.\C: PhyDrive:7 Num:1 Offset:122683392 ExtentLength:499059261440

[2025/01/25 15:55:45.432] LogicalDrive:\\.\D: PhyDrive:1 Num:1 Offset:16777216 ExtentLength:14000500768768

[2025/01/25 15:55:45.437] DeviceIoControl IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed \\.\O:, error:1

[2025/01/25 15:55:45.437] LogicalDrive:\\.\R: PhyDrive:5 Num:1 Offset:135266304 ExtentLength:499971522560

[2025/01/25 15:55:45.438] LogicalDrive:\\.\U: PhyDrive:8 Num:1 Offset:1048576 ExtentLength:250013007360

[2025/01/25 15:55:45.438] U: is belong to phydrive8

[2025/01/25 15:55:45.439] LogicalDrive:\\.\V: PhyDrive:0 Num:1 Offset:1048576 ExtentLength:17178820608

[2025/01/25 15:55:45.439] TryId=1 EFI GPT partition type is 0xc000000000000001

[2025/01/25 15:55:45.442] Change GPT partition type to ESP
[2025/01/25 15:55:45.469] VDS init OK, service 03098AFC



Windows事件查看器内容为：
错误应用程序名称: Ventoy2Disk.exe，版本: 1.0.0.3，时间戳: 0x64e418f3
错误模块名称: Ventoy2Disk.exe，版本: 1.0.0.3，时间戳: 0x64e418f3

异常代码: 0xc0000409

错误偏移量: 0x0002777c

错误进程 ID: 0x0x4570

错误应用程序启动时间: 0x0x1DB6EFE878685C9

错误应用程序路径: D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe

错误模块路径: D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe

报告 ID: 5115a84f-2c6a-40fc-a3b9-5ba457b177a6

错误程序包全名:
错误程序包相对应用程序 ID:



详细信息：
日志名称:          Application
来源:            Application Error

日期:            2025/01/25 15:55:45

事件 ID:        1000

任务类别:          应用程序崩溃事件

级别:            错误

关键字:         

用户:            XUANYIGUILIN\ShineYen

计算机:          XuanYiGuiLin

描述:

错误应用程序名称: Ventoy2Disk.exe，版本: 1.0.0.3，时间戳: 0x64e418f3

错误模块名称: Ventoy2Disk.exe，版本: 1.0.0.3，时间戳: 0x64e418f3

异常代码: 0xc0000409

错误偏移量: 0x0002777c

错误进程 ID: 0x0x4570

错误应用程序启动时间: 0x0x1DB6EFE878685C9

错误应用程序路径: D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe

错误模块路径: D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe

报告 ID: 5115a84f-2c6a-40fc-a3b9-5ba457b177a6

错误程序包全名:

错误程序包相对应用程序 ID:

事件 Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

    <EventID>1000</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>100</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2025-01-25T07:55:45.5686558Z" />

    <EventRecordID>9015</EventRecordID>

    <Correlation />

    <Execution ProcessID="17196" ThreadID="5412" />

    <Channel>Application</Channel>

    <Computer>XuanYiGuiLin</Computer>

    <Security UserID="S-1-5-21-2809617219-4141345153-1032581697-1001" />

  </System>

  <EventData>

    <Data Name="AppName">Ventoy2Disk.exe</Data>

    <Data Name="AppVersion">1.0.0.3</Data>

    <Data Name="AppTimeStamp">64e418f3</Data>

    <Data Name="ModuleName">Ventoy2Disk.exe</Data>

    <Data Name="ModuleVersion">1.0.0.3</Data>

    <Data Name="ModuleTimeStamp">64e418f3</Data>

    <Data Name="ExceptionCode">c0000409</Data>

    <Data Name="FaultingOffset">0002777c</Data>

    <Data Name="ProcessId">0x4570</Data>

    <Data Name="ProcessCreationTime">0x1db6efe878685c9</Data>

    <Data Name="AppPath">D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe</Data>

    <Data Name="ModulePath">D:\Program Files\Utilities\Ventoy\Ventoy2Disk.exe</Data>

    <Data Name="IntegratorReportId">5115a84f-2c6a-40fc-a3b9-5ba457b177a6</Data>

    <Data Name="PackageFullName">

    </Data>

    <Data Name="PackageRelativeAppId">

    </Data>

  </EventData>
</Event>

Hello!
We would like to inform you that a registration was previously made using your corporate email address on our platform.
Your Letter - https://telegra.ph/New-Transfer-01-18

Hello

I was trying an alternative to remastering Serena (Linuxmint) live-distro.

I used the Ventoy Persistence Plugin to get Serena to use it. (It worked)

Then I made the customizations; and rebooted to mark the persistence.dat "chmod 444 ".

But Serena still writes to it (this is not the behavior that i need)

I was searching the site for making persistence file switchable between mutable and immutable: a method to let the distros treat its persistence-file like a base, readonly, live-medium. All union changes would be discarded on shutdown. 


Or is there a simple user solution that I can try?

I use many ISOs with Ventoy but one that I can't get to work is the TrueNAS installer: https://www.truenas.com/truenas-community-edition/

The installer boots up but fails half way through, running the installer from a DVD works without problems.

Has anyone succeeded with this?

现在客户机CPU有麒麟9000C，盘古M900，龙芯3A6000，飞腾D2000等，用相应的ISO文件可以引导吗

Hello Ventoy Forum

I recently had the problem that Ventoy is not displaying any of my internal drives (devices).

I cannot understand which changes/settings on my system have led to this.
I was unable to adapt the few threads that contain this problem.
Uninstalling and reinstalling Ventoy has also been unsuccessful.

Do you have any idea what the reason(s) for this could be?
I would be very happy to receive further support.

I have downloaded ISO's from UUP dump for Win 10 but have come up with 2 issues.  On the first part I've gotten a few errors but they restarted and I believe completed.  On the second short part within the blue border I get a couple errors quickly re the Wim.  Question: do I need this last section to make my Ventoy work as a boot drive?  Also, I've gotten confused on which file to download to the drive.  It's a new dual A/C and being a novice I'm afraid to mess it up on the first try.  I believe it should be a large file.  I have 2.  One has "convert" on the end of the file name; = zip ?  The other is slightly smaller and named UUP.  I've been trying to get/google an answer for many weeks.  I am trying to fix a laptop that won't accept pin/password because msconfig was changed to diagnostic.  Hoping for a quick reply...

I can't get SystemRescue 11.x going with Ventoy. I tried it on several computers and tried both EFI and legacy boot. As far as I remember this is the case for all 11.x versions. SystemRescue 10.x works fine.
I am a using a USB SD Card reader with Ventoy installed on a SD card. The reader gives the following lsusb output:

Quote:Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer

群里面有管理员在吗? 购买 iventoy后,9月23号,发送邮件提供了机器码,至今未回复邮件
.

i have laptop Neo 14.2.32bs 
cpu z3735f
2 g ram
no boot friendbionic 32 bits
neither bionicpupp x86
do you know why

i was installed ventoy in my internal ssd
///////
however yes boot from my stick usb with ventoy