I installed, updated and prepared a windows 11 individual installation with some basic user configuration we use here. The iso file gets around 20 Gig big. If starting iventoy via the play button it runs into this message "Info, Service unavailable, the page will close!"
I used "Dism /Capture-Image" to capture the installation and "oscdimg\oscdimg.exe" to create the iso.

The log says nothing useful for that, see attachtment.



If I put the standard installtion install.wim from the windows 11 installation image into the source dir for creating the iso, iventoy starts as expected. Means for me, that least my iso creation process should work.

Maybe the general question is, is Iventoy a tool to deploy ISO images with pre installed software in such big images at all?



Regards

   Thomas

When you boot ventoy from an iso file, the condition for the iso file to be loaded and booted successfully is that the iso file must be in the ventoy drive. If the iso file is not in the ventoy drive, the iso file will not be mounted and will result in the iso file booting failing.

I've installed the current version of Ventoy on a USB thumb drive, leaving about 40GB space free at the end.

I created 3 additional partitions in the free space, FAT32 for ` /GRUB/grubx64.efi `, a swap partition, then a single ext4 partition to install Linux (grub, EFI mode).

Then I added a ` /ventoy/ventoy_grub.cfg ` grub configuration file to use under the [F6] key option in Ventoy.

Everything works as expected except one small issue. I've tested the USB in vbox on Linux, and booted directly on my EFI HP pc. Similar results are the [F6] key does not bring up a boot menu if Ventoy is started in EFI mode.

When starting Ventoy in MBR mode, the [F6] grub menu shows up, Ventoy themed, and the Linux OS boots and runs well.

Is there a solution for this? All my computers are EFI except one old box I still have available.

Also, how would I manually add my ` ventoy_grub.cfg ' entries directly to Ventoys grub menu, to eliminate having to use [F6].

On BOTH the USB drives on which I run Ventoy, I now as of a few days ago, get an error message on trying to boot which says:

"Verifying ..... data failed. Security Policy Violation .... data failed. Something went seriously wrong".

I can't read all of it because it is in tiny print and only on the screen for a short period. I any event, Ventoy won't boot and I gather from some somewhat apocryphal reports I have seen, that it has something to do with something MS has done very recently.

Hopefully Ventoy will be able to overcome the problem.


EDIT: if you turn SECURE BOOT off, it all works. But I imagine that turning Secure Boot off in a workplace environment is not an option so hopefully Ventoy will be able to overcome this issue.

Hello! So i am trying to install Fedora OS with persistence on my USB for educating. I used a guide from this video https://www.youtube.com/watch?v=vJ8TMSZwo0I&t=1s and it worked really well with Linux Mint and Kali! So the main question is that the guide from https://www.ventoy.net/en/plugin_persistence.html says
"Need to add 

I want to use steamdeck recovery image in ventoy. When i look up the supported os 。I find that tje steam os is supported。But when I copied the recovery image to the ventoy disk,the svreen is black,I can't enter the steam os desktop successfully。So what is the reason?

As ventoy support fixed/dynamic size VHD for Windows,
If I have a 20GB dynamic size VHD, actually size is 10GB on disk.
After boot from this VHD, I see it's actual size will change to 20GB.
An additional 10GB of space has been allocated.
I want to know if this additional allocation takes up too much time？
If it's a 100GB VHD actually using 10GB, will it take more time to boot?

AQC113 shows "no more network devices" why?

Attached Files

Thumbnail(s)
   

I formatted a 32gb drive. I selected it and instructed VT to write to that drive, and Ventoy reported, "completed successfully", But the drive, now named Ventoy is blank.  A DVD drive with no disk in it shows that Ventoy is installed on it.  WTF?

Having issues with the Surface Laptop 6 for Business. I've had two come through, 13.5 and 15" models and they both don't seem to want to launch any images. They sit on Preparing for boot.. please wait. They never get any further. I'm wondering if/how to troubleshoot. Also the Surface Pro 9 does not boot, sits on Preparing.. it's something to do with the new Surface range of devices. Does it have something to do with the Unsupported Window Size 4 error in the log? I can PXE boot just happily on most everything else. These are using Surface Docks to pxe boot from.

2024/08/06 19:50:58.659 [HTTP] HTTP PXE service starting ...
2024/08/06 19:50:58.659 [TFTP] TFTP service starting ...
2024/08/06 19:50:58.659 [DHCP] DHCP service no need to start in external subnet mode ...
2024/08/06 19:50:58.659 [NBD]  NBD service starting ...
2024/08/06 19:50:58.659 [HTTP] HTTP PXE service is running on x.x.x.x:16000 ...
2024/08/06 19:50:58.659 [PXE]  Now save iventoy config data ...
2024/08/06 19:50:58.659 [HTTP] NBD service is running on x.x.x.x:10809 ...
2024/08/06 19:50:58.660 [PXE]  iventoy config data (data/config.dat) save OK
2024/08/06 19:50:58.660 [PXE]  ===========================================================
2024/08/06 19:50:58.660 [PXE]        iVentoy 1.0.20 [Linux 64] is running now ...
2024/08/06 19:50:58.660 [PXE]  ===========================================================
2024/08/06 19:50:58.660 [TFTP] TFTP service is running ...
2024/08/06 19:50:58.660 [TFTP] TFTP write thread is running 51 ...
2024/08/06 19:50:59.142 [HTTP] API request: <{"method":"query_status"}>
2024/08/06 19:50:59.152 [HTTP] API request: <{"method":"sys_ip_list"}>
2024/08/06 19:50:59.157 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2024/08/06 19:51:53.433 [TFTP] Parse tftp option(tsize,0)
2024/08/06 19:51:53.434 [TFTP] Parse tftp option(blksize,1468)
2024/08/06 19:51:53.434 [TFTP] Unsupported tftp option windowsize 4
2024/08/06 19:51:53.434 [TFTP] TFTP RRQ client x.x.x.x:1827 download <iventoy_loader_16000_uefi> start ...
2024/08/06 19:51:53.434 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snp.efi.0
2024/08/06 19:51:53.434 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1827 with blksize 1468, has oack 1
2024/08/06 19:51:53.434 [TFTP] Recv an ERROR opcode pkt from client x.x.x.x:1827.
2024/08/06 19:51:53.437 [TFTP] Parse tftp option(blksize,1468)
2024/08/06 19:51:53.437 [TFTP] Unsupported tftp option windowsize 4
2024/08/06 19:51:53.437 [TFTP] TFTP RRQ client x.x.x.x:1828 download <iventoy_loader_16000_uefi> start ...
2024/08/06 19:51:53.437 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snp.efi.0
2024/08/06 19:51:53.437 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1828 with blksize 1468, has oack 1
2024/08/06 19:51:53.507 [TFTP] Finished send file to x.x.x.x:1828 with blksize 1468 blks 206
2024/08/06 19:51:57.551 [HTTP] DHCP external subnet mode notify discovery client x.x.x.x ipxe/01-70-f8-ae-b2-75-68/uefi/mask:x.x.x.x/gw:x.x.x.x/dns:x.x.x.x
2024/08/06 19:51:57.551 [PXE]  Client 70-f8-ae-b2-75-68 start PXE install in UEFI X64 mode.
2024/08/06 19:51:59.410 [HTTP] 200 HEAD /viso/id/2/mac:x:x:x:x:x:x/busCI:01:80:86:46:1e size 1969795072
2024/08/06 19:52:13.789 [HTTP] API request: <{"method":"sysinfo"}>
2024/08/06 19:52:13.805 [HTTP] API request: <{"method":"sys_ip_list"}>
2024/08/06 19:52:13.809 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2024/08/06 19:52:57.593 [HTTP] Client x.x.x.x:29833 (70) read timeout (close), state=0
2024/08/06 19:52:59.538 [HTTP] Client x.x.x.x:25631 (71) read timeout (close), state=0
2024/08/06 19:53:15.086 [HTTP] Client x.x.x.x:60933 (72) read timeout (close), state=0