I have now inventoy 1.0.34 running only it does not work anymore (also the 1.0.26 does not work).
I think this is because the IP address given by the third party (the router) is a.b.c.20 for example while iVentoy only respond to ip address a.b.c.201 till a.b.c.221.
(I saw in WireShark the IP address given to the PXE Interface).
The DHCP server is in the same subnet (a.b.c.1/24) , On this DHCP server I configured option 66 and 67 (bootfile and next server).
I see that the PXE interface gets it's IP address but not within the configured range, even if I bind the PXE mac address to an IP address within the range it still doesn't work.
Looks like the iVentoy server does not respond at all? In the firewall I permit all traffic to and from the program 'iVentoy_64.exe'
The iVentoy is running on a Windows Server 2016.
Hello, I have been trying to find an easier alternative to implement the multi boot ISOs. I believe we can use UAPI.1 (The Bootloader Specification) to our advantage if we add two new keys to the conf file. I have also made the proposal to add those keys in the official github discussion thread for UAPI. I have written a detailed blog on how this will solve the need for hardcoded configs for each distribution. I will highly appreciate if the Ventoy dev takes a look at it and provides feedback on what I am trying to achieve. The blog is: https://splayer.4plt.ch/blogs/2-the-vent...index.html
I am also looking for feedback on the correctness of the facts I have presented in the blog.
If this is not the correct place to post this then I sincerely apologize and request to guide me to a proper channel.
Thank You.
First of all, big thanks to Longpanda, I know many people said it too many times, but I really wanted to thank to Longpande for keep developing this tool. It has been a great contribution to the whole IT world.
I work for a company that specializes in supporting supermarkets, we are developing HW and SW to enable stores, restaurants, petrol stations and many others. Some of our specific HW (and some 3rd party HW) struggles to boot in UEFI. Those machines ignore the UEFI standard and have troubles to boot from anything else in some circumstances (large drives) other than Microsoft's bootloader (/EFI/Microsoft/Boot/bootmgfw.efi).
I have created diagnostics tool for our engineers based on Ventoy using various ISO utilities, BIOS updates, the usual open source tools available and some specific to our machines. To make sure it boots on all UEFI machines, I had to modify the ventoy.disk.img.xz, unpack it, mount it and do the below:
From /EFI/BOOT/ copy BOOTX64.EFI, MokManager.efi, grub.efi and grubx64_real.efi into newly created folder: /EFI/Microsoft/Boot/
In /EFI/Microsoft/Boot/ rename BOOTX64.EFI to bootmgfw.efi
repack the ventoy.disk.img with xz
Once I install the ventoy, it works great. I could only copy the X64 EFI binaries as there is not enough space on the 32MB EFI FAT partition, which is fine as this only affectes our X64 machines (we don't use any other architecture).
My humble question would be if perhaps other people approach you to do something similar as some other BIOSes may ignore the UEFI specs and just look for Microsoft bootloader as the only option. If that's the case, would you consider adding these files so all UEFI firmware would work?
Attached screenshot shows the original /EFI/BOOT/ files on the left and the newly added (copied) /EFI/Microsoft/Boot/ files on the right.
Using iventoy with "Sterlec" AIO ISOs, the WinPE system boots fine, but the applications don't load into memory. If I do the same type of boot via USB, everything works fine. Why don't the applications load over the network?
Alguem ai pode me ajuda ja testei varias versao do iventoy, varias iso diferente , e sempre mesmo problema , carrego o iventoy inicia tudo normal, mas vou vou no outro pc pra da boot aparece boot pxe iventoy e volta para bios
aqui esta aqui log
2026/05/22 13:14:44.476 [PXE] [WinLog] ================== WinMain Log Init Ok =================
2026/05/22 13:14:44.476 [PXE] [WinLog] Original current directory is E:\SISTEMAS\iventoy-1.0.31
2026/05/22 13:14:44.491 [PXE] [WinLog] Ext log C:\Users\Leonard\AppData\Local\iVentoy\log.txt
2026/05/22 13:14:44.491 [PXE] ==========================================================
2026/05/22 13:14:44.491 [PXE] ##########################################################
2026/05/22 13:14:44.491 [PXE] ################### IVENTOY FREE RUN #####################
2026/05/22 13:14:44.491 [PXE] ##########################################################
2026/05/22 13:14:44.491 [PXE] ==========================================================
2026/05/22 13:14:44.507 [PXE] ##################### IVENTOY Windows x86_64 (Free Edition) ################
2026/05/22 13:14:44.507 [PXE] system cpu core number: 8
2026/05/22 13:14:44.507 [PXE] Module <Log> init start ...
2026/05/22 13:14:44.507 [PXE] Module <Log> init OK ...
2026/05/22 13:14:44.507 [PXE] Module <Plat> init start ...
2026/05/22 13:14:44.507 [PXE] NIC:<Realtek PCIe GBE Family Controller> Type:6
2026/05/22 13:14:44.507 [PXE] IP=<192.168.150.153> Mask=<255.255.255.0>
2026/05/22 13:14:44.507 [PXE] Gateway list <192.168.150.1>
2026/05/22 13:14:44.507 [PXE] Find Gateway <192.168.150.1>
2026/05/22 13:14:44.507 [PXE] Before nic name not found, now add new
2026/05/22 13:14:44.507 [PXE] NIC:<Bluetooth Device (Personal Area Network)> Type:6
2026/05/22 13:14:44.507 [PXE] IP=<0.0.0.0> Mask=<0.0.0.0>
2026/05/22 13:14:44.507 [PXE] Skip zero IP address
2026/05/22 13:14:44.507 [PXE] Module <Plat> init OK ...
2026/05/22 13:14:44.507 [PXE] Module <Cfg> init start ...
2026/05/22 13:14:44.507 [PXE] Module <Cfg> init OK ...
2026/05/22 13:14:44.507 [PXE] Module <MAC> init start ...
2026/05/22 13:14:44.507 [PXE] mac addr db init ...
2026/05/22 13:14:44.569 [PXE] mac addr db init OK, total 57419 records
2026/05/22 13:14:44.569 [PXE] Module <MAC> init OK ...
2026/05/22 13:14:44.569 [PXE] Module <Tarfs> init start ...
2026/05/22 13:14:44.648 [PXE] iventoy.dat <8777916> <15831040> <c87b647b>
2026/05/22 13:14:44.929 [PXE] Extract iventoy.dat success.
2026/05/22 13:14:44.929 [PXE] ##########################################################
2026/05/22 13:14:44.929 [PXE] #################### iVentoy 1.0.31 ####################
2026/05/22 13:14:44.929 [PXE] ##########################################################
2026/05/22 13:14:44.929 [PXE] tarfs find 190 files
2026/05/22 13:14:44.929 [PXE] Module <Tarfs> init OK ...
2026/05/22 13:14:44.929 [PXE] Module <OS> init start ...
2026/05/22 13:14:44.929 [PXE] cpio buf:000001F058DFC040 len:5007360 fixoff:968
2026/05/22 13:14:44.929 [PXE] Module <OS> init OK ...
2026/05/22 13:14:44.929 [PXE] Module <IMG> init start ...
2026/05/22 13:14:44.929 [PXE] Scan iso directory for all image files ...
2026/05/22 13:14:44.944 [PXE] Dyn:0 Add ISO <iso/WindowsPE.ISO> ID:1 size:4740581376 type:1
2026/05/22 13:14:44.944 [PXE] [1] Phase1 parse image <iso/WindowsPE.ISO> <UDF> 1 starting...
2026/05/22 13:14:45.226 [PXE] [1] This is standard Windows ISO.
2026/05/22 13:14:45.226 [PXE] [1] img <iso/WindowsPE.ISO> <UDF> OS type:Windows
2026/05/22 13:14:45.226 [PXE] [1] collect wim files for <iso/WindowsPE.ISO> ...
2026/05/22 13:14:45.226 [PXE] [1] Find in /efi/microsoft/boot/bcd ...
2026/05/22 13:14:45.226 [PXE] [1] Find wim flag:</sources/boot.wim>
2026/05/22 13:14:45.226 [PXE] [1] Find wim flag:</sources/boot.wim>
2026/05/22 13:14:45.226 [PXE] [1] wim </sources/boot.wim> already exist
2026/05/22 13:14:45.226 [PXE] [1] Find in /boot/bcd ...
2026/05/22 13:14:45.226 [PXE] [1] Find wim flag:</sources/boot.wim>
2026/05/22 13:14:45.226 [PXE] [1] wim </sources/boot.wim> already exist
2026/05/22 13:14:45.226 [PXE] [1] Find wim flag:</sources/boot.wim>
2026/05/22 13:14:45.226 [PXE] [1] wim </sources/boot.wim> already exist
2026/05/22 13:14:45.226 [PXE] [1] [WIM 0] /sources/boot.wim [Seek:20146176 Size:669648512 RecSeek:0]
2026/05/22 13:14:45.226 [PXE] [1] collect wim files finished.
2026/05/22 13:14:45.226 [PXE] [1] Phase1 parse image <iso/WindowsPE.ISO> finished success
2026/05/22 13:14:45.226 [PXE] ================= PXE IMG DUMP =================
2026/05/22 13:14:45.226 [PXE] [1] <WindowsPE.ISO> <4740581376> <UDF> <Windows> <Wim:0/1>
2026/05/22 13:14:45.226 [PXE] ================================================
2026/05/22 13:14:45.226 [PXE] Module <IMG> init OK ...
2026/05/22 13:14:45.226 [PXE] Module <DHCP> init start ...
2026/05/22 13:14:45.226 [PXE] Module <DHCP> init OK ...
2026/05/22 13:14:45.226 [PXE] Module <TFTP> init start ...
2026/05/22 13:14:45.226 [PXE] Module <TFTP> init OK ...
2026/05/22 13:14:45.226 [PXE] Module <HTTP> init start ...
2026/05/22 13:14:45.241 [HTTP] HTTP API service is running on 0.0.0.0:26000 ...
2026/05/22 13:14:45.241 [PXE] EnableWindow open link button
2026/05/22 13:14:45.304 [PXE] Module <HTTP> init OK ...
2026/05/22 13:14:45.304 [PXE] Module <BLK> init start ...
2026/05/22 13:14:45.304 [PXE] Module <BLK> init OK ...
2026/05/22 13:14:45.304 [PXE] <535735305a57776f55696b67513239795a53685554536b67615463744d7a63334d434244554655675143417a4c6a517752306836>
2026/05/22 13:14:45.304 [PXE] <4d444d774d4441794d4441774e4441774d4455774d4441774d4459774d4441334d4441774f4441774d446b3d>
2026/05/22 13:14:45.304 [PXE] 5db1124ca698f4da2e32544783f2f118c66302142fb7e70fa2a6ad496c3f01d7
2026/05/22 13:14:45.304 [PXE] ====================== SYSTEM IP LIST ===================================
2026/05/22 13:14:45.304 [PXE] [1] 192.168.150.153 255.255.255.0 192.168.150.1 Realtek PCIe GBE Family Controller
2026/05/22 13:14:45.304 [PXE] =========================================================================
2026/05/22 13:14:45.304 [PXE] OS language 1 en_us
2026/05/22 13:14:45.304 [PXE] PXE cofigure recovery ...
2026/05/22 13:14:45.304 [PXE] data/config.dat not found, no need for recovery.
2026/05/22 13:14:45.319 [PXE] link button already enabled, no need to dissable.
2026/05/22 13:14:47.389 [HTTP] API request: <{"method":"sysinfo"}>
2026/05/22 13:14:47.464 [HTTP] API request: <{"method":"sys_ip_list"}>
2026/05/22 13:14:47.492 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2026/05/22 13:14:55.956 [HTTP] API request: <{"method":"get_config_all"}>
2026/05/22 13:14:58.100 [HTTP] API request: <{"method":"get_img_summary"}>
2026/05/22 13:14:58.100 [HTTP] API request: <{"method":"get_dir_tree"}>
2026/05/22 13:14:58.100 [HTTP] API request: <{"method":"get_img_tree"}>
2026/05/22 13:15:00.130 [HTTP] API request: <{"method":"sys_ip_list"}>
2026/05/22 13:15:00.138 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2026/05/22 13:15:01.537 [HTTP] API request: <{"method":"check_firewall"}>
2026/05/22 13:15:01.537 [PXE] Check for firewall rule <E:\SISTEMAS\iventoy-1.0.31\iVentoy_64.exe>
2026/05/22 13:15:01.794 [PXE] No block rule find
2026/05/22 13:15:01.808 [HTTP] API request: <{"method":"start_server","ip":"192.168.150.153","mask":"255.255.255.0","gw":"192.168.150.1","pool_begin":"192.168.150.200","pool_end":"192.168.150.219","dns_server":""}>
2026/05/22 13:15:01.808 [PXE] Update Mask[255.255.255.0 --> 255.255.255.0] GW[192.168.150.1 --> 192.168.150.1]
2026/05/22 13:15:01.808 [PXE] iVentoy service is starting ...
2026/05/22 13:15:01.808 [PXE] iVentoy 1st time start, do img recover ...
2026/05/22 13:15:01.808 [PXE] PXE cofigure image recovery ...
2026/05/22 13:15:01.808 [PXE] data/config.dat not found, no need for recovery.
2026/05/22 13:15:01.808 [DHCP] Old IP pool [0.0.0.0 - 0.0.0.0] unuseable, free dhcp db.
2026/05/22 13:15:01.808 [PXE] [1] Phase2 parse image <iso/WindowsPE.ISO> <UDF> starting...
2026/05/22 13:15:01.808 [PXE] [1] is standard 64bit Windows
2026/05/22 13:15:01.808 [PXE] [1] Patch BCD file for Windows 64bit
2026/05/22 13:15:01.822 [PXE] This is a good standard BCD file
2026/05/22 13:15:01.822 [PXE] [1] Patch BIOS BCD file success
2026/05/22 13:15:01.822 [PXE] This is a good standard BCD file
2026/05/22 13:15:01.822 [PXE] [1] Patch UEFI BCD file success
2026/05/22 13:15:01.822 [PXE] [1] locate wim data (wims:1) ...
2026/05/22 13:15:01.822 [PXE] [1] ExtraBuf totlen:1122172 tool:1120980 autonum:0 injectlen:0
2026/05/22 13:15:01.822 [PXE] [1] @@ locate wim file </sources/boot.wim> ...
2026/05/22 13:15:01.822 [PXE] [1] @@@ overlen=8 overoff=2588904 fe_entry_size_offset=2588728 start_block=304 file_offset=20146176
2026/05/22 13:15:01.836 [HTTP] API request: <{"method":"query_status"}>
2026/05/22 13:15:01.849 [PXE] [1] read lookup offset:669262344 size:383800
2026/05/22 13:15:01.849 [PXE] [1] search pecmd.exe 000001F05ABE5368
2026/05/22 13:15:01.849 [PXE] [1] search reg SYSTEM 000001F05AC26140
2026/05/22 13:15:01.849 [PXE] [1] find system lookup entry_id:7579 raw_size:6402048
2026/05/22 13:15:01.863 [PXE] [1] 1017976 6402048 chunk_num=196
2026/05/22 13:15:01.875 [PXE] [1] last chunk_size:3192 decompresslen:12288 tot:6402048
2026/05/22 13:15:01.875 [PXE] [1] find registry cmdline i:6393072 offset0x617d10)6389008 size0x56)86
2026/05/22 13:15:01.875 [PXE] [1] start offset is 0x618d14(6393108)
2026/05/22 13:15:01.875 [PXE] [1] registry setup cmdline:<Pecmd.exe Main %Windir%\system32\Pecmd.ini>
2026/05/22 13:15:01.875 [PXE] [1] @ directly use pecmd.exe 000001F05ABE5368
2026/05/22 13:15:01.875 [PXE] [1] find replace file at 000001F05ABE5368
2026/05/22 13:15:01.875 [PXE] [1] search hash <a58bae4d147d3ab1e818fb893d65e11f1c13707e>
2026/05/22 13:15:01.875 [PXE] [1] find replace lookup entry_id:4349 raw_size:855040
2026/05/22 13:15:01.880 [PXE] [1] 821580 855040 chunk_num=27
2026/05/22 13:15:01.880 [PXE] [1] last chunk_size:1874 decompresslen:3072 tot:855040
2026/05/22 13:15:01.880 [PXE] [1] jump exe </win/vtoypxe64.exe> len:157184 alignlen:157184
2026/05/22 13:15:01.880 [PXE] [1] jump_exe_len:157184 bin_raw_len:2134464 bin_align_len:2136064
2026/05/22 13:15:01.880 [PXE] [1] windows locate wim finish
2026/05/22 13:15:01.880 [PXE] [1] Windows virt data new <Windows> ...
2026/05/22 13:15:01.880 [PXE] [1] /boot/bootfix.bin not exist
2026/05/22 13:15:01.880 [PXE] [1] efisys_noprompt.bin not exist
2026/05/22 13:15:01.880 [PXE] [1] UDF fill override data ...
2026/05/22 13:15:01.880 [PXE] [1] PdSizeOffset=530624 tagOffset=530432
2026/05/22 13:15:01.880 [PXE] [1] UDF tag valid OK, should match it.
2026/05/22 13:15:01.880 [PXE] [1] UDF tag refresh OK.
2026/05/22 13:15:01.880 [PXE] [1] ## virt wim file </sources/boot.wim> <669648512> <New:673906688> ...
2026/05/22 13:15:01.880 [PXE] [1] file_entry and extend data in the same block.
2026/05/22 13:15:01.880 [PXE] [1] fix tag override 224[2588688 - 2588912] 2588728 2588672 56
2026/05/22 13:15:01.880 [PXE] [1] ## virt BIOS BCD file 24576 28672 28672...
2026/05/22 13:15:01.880 [PXE] [1] file_entry and extend data in the same block.
2026/05/22 13:15:01.880 [PXE] [1] fix tag override 224[2517008 - 2517232] 2517048 2516992 56
2026/05/22 13:15:01.880 [PXE] [1] ## virt BIOS BCD file 24576 28672 28672...
2026/05/22 13:15:01.880 [PXE] [1] file_entry and extend data in the same block.
2026/05/22 13:15:01.880 [PXE] [1] fix tag override 224[4130832 - 4131056] 4130872 4130816 56
2026/05/22 13:15:01.880 [PXE] [1] find target file, name_len:18, offset: 914280, upadte hash
2026/05/22 13:15:01.880 [PXE] [1] update replace lookup entry_id:4349
2026/05/22 13:15:01.880 [PXE] [1] find meta lookup entry_id:7675, update resource head and hash(1735024)
2026/05/22 13:15:01.880 [PXE] [1] Virt data ISO file size: 4740581376 5414545408
2026/05/22 13:15:01.880 [PXE] [1] ================ OVERRIDE DUMP ================
2026/05/22 13:15:01.880 [PXE] [1] <0> [ 530432 - 530944 512 ]
2026/05/22 13:15:01.880 [PXE] [1] <1> [ 2588672 - 2589184 512 ]
2026/05/22 13:15:01.880 [PXE] [1] <2> [ 2516992 - 2517504 512 ]
2026/05/22 13:15:01.880 [PXE] [1] <3> [ 4130816 - 4131328 512 ]
2026/05/22 13:15:01.880 [PXE] [1] ================ OVERRIDE DUMP ================
2026/05/22 13:15:01.880 [PXE] [1] ================ VIRT RANGE DUMP ================
2026/05/22 13:15:01.880 [PXE] [1] <iso/WindowsPE.ISO> WIM:1/1
2026/05/22 13:15:01.880 [PXE] [1] <01> [4740581376 - 5410230272 669648896 ] Remap
2026/05/22 13:15:01.880 [PXE] [1] <02> [4740581376 - 4740581584 208 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] <03> [5410230272 - 5412366336 2136064 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] <04> [5410387556 - 5410388580 1024 ] iVentoy Param
2026/05/22 13:15:01.880 [PXE] [1] <05> [5412366336 - 5414103040 1736704 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] <06> [5413280616 - 5413280636 20 ] WIM BIN CHK
2026/05/22 13:15:01.880 [PXE] [1] <07> [5414103040 - 5414488064 385024 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] <08> [5414320520 - 5414320540 20 ] WIM BIN CHK
2026/05/22 13:15:01.880 [PXE] [1] <09> [5414486820 - 5414486840 20 ] WIM META CHK
2026/05/22 13:15:01.880 [PXE] [1] <10> [5414488064 - 5414516736 28672 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] <11> [5414516736 - 5414545408 28672 ] Memory
2026/05/22 13:15:01.880 [PXE] [1] ================ VIRT RANGE DUMP ================
2026/05/22 13:15:01.880 [PXE] [1] Phase2 parse image <iso/WindowsPE.ISO> finished success
2026/05/22 13:15:01.880 [PXE] Update ipxe menu 1 ...
2026/05/22 13:15:01.880 [PXE] ================= IMG TREE DUMP =================
2026/05/22 13:15:01.880 [PXE] WindowsPE.ISO [1] <WIMS:1/1>
2026/05/22 13:15:01.880 [PXE] ================================================
2026/05/22 13:15:01.880 [HTTP] HTTP PXE service starting ...
2026/05/22 13:15:01.880 [TFTP] TFTP service starting ...
2026/05/22 13:15:01.880 [DHCP] DHCP service starting in Internal mode ...
2026/05/22 13:15:01.880 [BLK] BLK service starting ...
2026/05/22 13:15:01.880 [PXE] Now save iventoy config data ...
2026/05/22 13:15:01.880 [HTTP] NBD service is running on 192.168.150.153:10809 ...
2026/05/22 13:15:01.880 [SCSI] ISCSI service is running on 192.168.150.153:3260 ...
2026/05/22 13:15:01.880 [PXE] iventoy config data (data/config.dat) save OK
2026/05/22 13:15:01.880 [PXE] =================================================================
2026/05/22 13:15:01.880 [PXE] iVentoy 1.0.31 Windows x86_64 (Free Edition) is running now ...
2026/05/22 13:15:01.880 [PXE] =================================================================
Hi, I was following this guide https://www.ventoy.net/en/doc_ventoy2disk.html with vtsi file and then Rufus asked me to confirm that it will delete all data on the disk. It would be helpful if the guide mentioned that despite rufus saying it will delete everything, nothing will get deleted actually.
Hi there!
I installed CachyOS in a virtual machine using Hyper-V (with option "generation 2" selected). Then I installed the vtoyboot script (vDisk Boot Plugin --> latest vtoyboot-1.0.36 release) and converted the VHDX file to VHD so it could boot with Ventoy.
The installation boots and runs fine in Hyper-V.
I then renamed the *.vhd file to *.vtoy. At boot, in Ventoy, I selected the correct CachyOS vtoy file, but it does not load and I receive the following error shown below. If I press Enter, after a few moments the same message appears again.
Quote:You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
I followed this exact same procedure with Linux Mint and it works correctly in Ventoy, but for some reason CachyOS does not.
Do you have any idea why?
I have recently set up a 128GB USB stick with Ventoy thus:
sudo bash Ventoy2Disk.sh -i -L FZV3 -r 20000 /dev/sdc
On the main partition of the stick I have placed 4 versions of Linux Mint
linuxmint-20.3-mate-64bit.iso
linuxmint-21.3-cinnamon-64bit.iso
linuxmint-21.3-mate-64bit.iso
linuxmint-22.3-mate-64bit.iso
Each of these versions of Linux Mint has a 2GB persistence file associated with it. I created a 2GB Persistence file using CreatePersistentImg.sh, then copied the file to the USB stick into the same folder as the isos, and then renamed it to suit the particular iso. Then I used:
sudo bash VentoyPlugson.sh /dev/sdc
...and the browser-based configuration utility to associate the persistence file with the appropriate iso. I repeated this process for all the 4 versions of Linux Mint.
All this worked very well! All 4 versions boot OK with or without persistence, and I have verified that the persistence is actually working as it should.
Now comes the problem. I want to try out LMDE7, so I went through the same steps as above with the LMDE7 iso, and then associating it with a 2GB persistence file using the browser-based configuration utility. It all looked like it had gone OK, no obvious error messages.
After doing this I can boot into LMDE7 using the Ventoy stick, and the option for persistence appears on the Ventoy menu as expected - but the persistence does not work.
It would be great to get the persistence working for LMDE7. Can anybody help, please?
Ventoy is 1.1.10 x86_64.
Ventoy Version in Disk: 1.1.10
Disk Partition Style : MBR
Secure Boot Support : YES
0x617d10)6389008 size
