Here is a screen shot of my ventoy directory on a usb memory stick:
   
And here is a screen shot of the ventoy.json file:
   
All of the .dat files were generated by CreatePersistentImg.sh and then copied to the ventoy directory and the names change as you see them. When booting from the usb memory stick, all of the ventoy menus look and function as they should. The Kbuntu iso starts and runs as expected and configuration changes are stored and remembered at the next startup, as expected.
The Ubuntu iso will not start up using the persistence file. It will start and run without persistence. All of the others start up and run with their persistence files, but no configuration changes are remembered on the next boot.
What am I doing wrong?

Is there a setting so that the sufixe (extension) of the ISO or WIM name does not appear in the menu list?
Thank you

Greetings!  GRUB newbie here.  I've been using VENTOY successfully on lots of machines, mostly Legacy-MBR types.  I just tried to use it on an HP 8510p Core2Duo (Legacy-MBR) and GRUB flashes an error (too fast to see) and winds up at the GRUB prompt.

I used the "ls (hd0,1)" and "ls (hd0,2)" GRUB commands to give a quick look at the partitions on the VENTOY build (which is a 1tB USB HDD).  Partition 1 looks normal seeing an exFAT FileSystem with the proper label and size.  Partition 2 says "No known FileSystem detected" with the proper 32mB size.  All my partition tools say that the 32mB partition is of the FAT16 type.

Any idea what might be happening here...???  Thanks in advance for any offered help.

Hi @all.

There are scant reports of anyone updating -- specifically from v1.0.21 to v1.0.22 -- with Ventoy installed to computer internal HDD/SSD.

I just tried to upgrade my setup (see https://forums.ventoy.net/showthread.php...46#pid1746 and https://forums.ventoy.net/showthread.php...88#pid1488) by booting a Linux Mint 20 livecd ISO image and issuing the following command in a terminal:

Hello everyone,
i tried today to install Windows 7 in several ways into a VHD and start it with Ventoy.
I always tried to boot in BIOS mode, but no matter how I created the VHD I got a Bluescreen 07b at boot time.
I also tried to patch the registry to AHCI, but without success.
Did Windows 7 already run one of you ???
I would like to have it on the Ventoy Stick, then I don't need a local installation anymore. :-)

i have many files in USB. 
there are Some PE files in /PE
and iso files in /Source
and etc.. 1st folders, sub folders, sub sub folders...  many..in usb.

So, take many times to scan and display files, folders in root without below option.

{ "VTOY_DEFAULT_SEARCH_ROOT": "/PE" }

But, with option "VTOY_DEFAULT_SEARCH_ROOT", just display files in /PE. no shows files wim or iso in root. To solve this problem, I Have to collect ISO, WIM in One Folders.

so I sugesstion, 
Without "VTOY_DEFAULT_SEARCH_ROOT", Do not scan All folder and files USB. Just scan root folder and 1st folders.

Hello, longpanda!
Please tell me which Ubuntu distributions are supported by the Auto Installation Plugin, in particular whether it is possible to use this plugin with the distribution ubuntu-20.04.1-desktop-amd64.iso?

Since the latest version of Ventoy also supports booting from VHD, I have been working on this for the last few days.
Windows (different versions) I get all of them running.
Windows XP I unfortunately can't get to run. :-(
Maybe someone of you has a VHD with XP and the integrated drivers for Vboot to test.
Did anyone of you already manage that ???

Since the latest version of Ventoy also supports booting from VHD, I have been working on this for the last few days.
Windows (different versions) I get all of them running.
Linux however does not. I tried everything I could think of, but without success.
Did anyone of you already manage that ???

after the 1st stage of installing windows 7, after copying the files after the first restart of the computer, it will boot from the USB flash drive and press f4 to search and boot windows to continue the installation, then the installation will not complete successfully and will give an error later windows setup could not configure windows to run on this hardware. But if you manage to immediately remove the USB flash drive after the first reboot, so that Windows itself goes to the second stage of installation, then everything is installed well. The bug is only Windows 7 different images, on 8.1 and 10 Windows the bug does not appear.