Hello.

I have recently started using Ventoy with succes.

However there is one very nuisance. A Ventoy prepared USB-stick (under Windows 10), if a extra ISO is to be added, takes maybe 4 minutes before recognized by the PC (with Windows 10). Before recognizing, all USB-related programs (and Windows Explorer), fail to start. After recognizing, all functions well and normal. Even unplugging and replugging the USB-stick gives then no problem (untill replugging in a new started PC).
The are many reports from different peaple about the same problem.

I found that the Ventoy-stick has a FAT16 Ventoy-system partition. 
I have earlier found, on my PC with Windows 10, that memory-cards which are FAT16 formatted (so 2GB or 4GB cards) give serious confusing recognizing problems. Probably because there are several different recognizing ID-'s for FAT16. When I applied FAT32 for those cards all problems were over.

So I suggest to the developer of Ventoy to change the Ventoy-system partition to FAT32, in my expectation that then the long recognizing problem under Windows10 is over.

I feel I have looked everywhere, obviously not ! I just find this to download - even on the page devoted to it.

Anyway, if anyone can enlighten me as to where I will find it I would be most obliged.

Thanks

Hello,

I captured the image of a Windows machine through WDS.
But when I add it to iVentoy, iVentoy shuts down.

Does iVentoy accept personal Windows iso ?

Thank you for your answers.

As a new member and user, I am very pleased with Ventoy. It is absolutely magnificent.

I have found this issue when using Ventoy on my Toshiba 500GB SSD. As per the title, the VENTOYEFI partition is not visible on this SSD in Windows File Managers - but it is there!. The SSD boots and works just fine and the VENTOYEFI partition IS visible in WinPE applications.

When I use Ventoy to set up various other Flash Drives, I see the VENTOYEFI partition on those flash drives in Windows file managers - but not on this SSD?

Any thoughts?

1st test > iventoy 1.0.19
Asus router as DHCP server ( no advance setting for nextserver and bootfile )
All settings are default except > DHCP server : External / Externalnet ( I tried both)
Gives error : No boot device found ( both Bios and UEFI mode)

Only way to get it work is to change DHCP server setting to " Internal"

I am using AIOboot PXEboot from more then 5yrs
Same network setup. Pc boots without any problem.
( All Pc I clone or repair with this PXE setup)

Please check image for detail.

I think something is missing in iventoy to work with external DHCP without any advance settings.

Attached Files

Thumbnail(s)
           

Hi @ventoy
A user asked how to install iVentoy on a Synology NAS drive.
I couldn't find an answer because I don't have any knowledge on this subject. Can iventoy be used on this device?
if it is possible How can we do it?

(sorry, translate with google)

Start the ISO on a USB stick with Ventoy.
In the next menu only 'Boot in memdisk mode' works for Truecrypt (TS).
Truecrypt-Rescue starts.
If the Truecrypt|Windows-Loader is then restored with F8, the query comes from TS:  Disk 0?  y/n
After y(es) the loader is written to the disk 0, but it's the USB-stick! Of course, after that the stick no longer boots and the TS-drive was not updated.
For CDs, TS does not mix up hard drives, the first real hard drive is used. 
In the BIOS I can define the USB stick as a CD, but Ventoy no longer boots as a CD.

The Ventoy stick should somehow be recognized in the system as a CD (or as a Not-Harddisk-Thing) not as a hard drive. 

Then TS would do everything right.

Greetings,
I'm trying to add ventoy to my Ubuntu grub menu.
My ventoy is installed on a 2nd ssd drive on my laptop as sdb.
My /etc/grub.d/40_custom file is:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Ventoy Boot USB' {
insmod part_gpt
insmod ext2
insmod fat
insmod exfat
insmod ntfs
insmod chain
search --no-floppy --set=root --fs-uuid 8CC4-D433
set search_efi_path=(hd1,2)/ventoy
# chainloader /dev/sdb2/ventoy/ventoy_x64.efi
chainloader (hd1,2)/ventoy/ventoy_x64.efi
}

I've run update-grub and when I boot I see ventoy on the grub list:
But when I run it I get"
"Invalid signature"

What am I doing wrong?

Hello,

I have a problem. I cannot get my icons visible for my ISO files. I use a 128 GB Philips USB 3.1-3.2 formatted in exfat. The icons are in the folder Ventoy - Theme - Vimix - Icons. I don't see what is wrong. Everything seems to be correct.


can anyone help me thank you

Paul

I seem to be having a strange issue when booting iVentoy using UEFI mode. I'm unsure if it a bug or if I'm missing something but for example when booting a stock Windows image using iVentoy in UEFI, I end up with a garbled image.

I have tested this on multiple physical machines and also using Virtual box. Unsure if it's related or not but when booting the same image in UEFI mode using Ventoy (USB version) everything works fine. When testing on Virutalbox in UEFI mode it hangs at the message "Preparing for boot, please wait..." and then eventually restarts.

My iVentoy server is running as a Proxmox virtual machine (Debian 12) in a different VLAN than my PXE clients. I am using iVentoy in the "ExternalNet" mode with OPNSense being my DHCP server (I have network booting enabled & allowed through Firewall), but I have also tried changing this to "External" and even using the built in DHCP server on the same subnet. I also tried the Windows version of iVentoy but all yield the same garbled image.

Interestingly booting a Linux based ISO in UEFI mode seems to work ok (I tried GParted).

I can reach the iVentoy menu fine, but when I select an image I get the garbled image.

I have attached some images to help explain things, although I can only attach 5...

• Image 1 - UEFI Windows boot using Ventoy USB version (Works)
  
• Image 2 - UEFI iVentoy boot (Can access menu fine)
  
• Image 3 - UEFI Windows boot using iVentoy (Garbled image)
  
• Image 4 - UEFI Windows boot using iVentoy with Virtualbox (Hangs at message screen, then restarts)
  
• Image 5 - UEFI Linux boot using iVentoy (Seems to work fine)
  
• BIOS Windows boot using iVentoy (Works)
  
• OPNSense DHCP network booting options (Next server = iVentoy IP address, BIOS image name = iventoy_loader_16000_bios, UEFI image name = iventoy_loader_16000_uefi)
  

Attached Files

Thumbnail(s)