The Ventoy Linux version contains a file "CreatePersistentImg.sh" when the tar file is expanded into the Ventoy folder along with all the other Ventoy needs. In that folder, too, there is a README file.

Can someone steer me to any documentation on what this, "CreatePersistentImg.sh", is? 
And how to use it when creating a Ventoy bootable disk?

The README file give NO clue to what it is nor when it is to be used. The following is the README

https://techlibrary.hpe.com/us/en/enterp...index.aspx
能启动，但报错。

Curious.

I do understand the very good benefit the script and EXE file do for us as it creates the Ventoy device. 

But, the options when running these are NOT saved upon Ventoy device creation. And the user MUST REMEMBER those options whenever the user upgrades Ventoy from one release to the next.

Would the Ventoy developers consider saving a configuration/options file, either hidden or exposed, on Partition #2 of the Ventoy device?

If this is the case, on subsequent updates, there is no possibility that any user would get it wrong going from one release to another. Worst case in the Windows version, if Ventoy sees the 2nd partition, it could display the prior options that was used so a user would know what was done before...although I, personally, see little need for that. But, Ventoy could used the prior options as the default unless the user overrides some options from before.

If an implementation is forthcoming, all new upgrades would merely be:

Hello Guys,

I've actually got a question.
I read on the main site that 'USB Normal Use unaffected' as one of the features of Ventoy. So If I were to install Windows 10 onto the USB using ventoy, Can I copy other files like softwares onto it as well, so that I can have both Windows 10 and necessary softwares on one single USB? Can I use this USB and install the softwares from it? Would it cause any problems?
Also, is there any tutorials available for installing Windows 10 ISO onto the USB with ventoy? Any links would be highly appreciated.

Please Help.

Thanks in advance.

Would it be possible to support something like the following? (Note the * wildcard in the image names)

{
"injection": [
{
"image": "/ISO/MX-19.1_x64.iso",
"archive": "/driver/mx-driver.tar.gz"
},
{
"image": "/ubuntu-*-desktop-amd64.iso",
"archive": "/driver/ubuntu-driver.tar.bz2"
},
{
"image": "/windows_10_*.iso",
"archive": "/driver/win10-driver.zip"
}
]
}

That way, as we update the ISO files on the USB drive, the injection still works without having to modify ventoy.json each time and for every single iso

Please add support for GNOME Partition Editor (GParted)

https://gparted.org/download.php

ISO does not boot properly with Ventoy 1.0.19

I have a mypassport plug and play storage that appears as sdb. I could not install ventoy regularly to it with the exe even by running with the extra parameter letter, it still does not appear as an option, this only showed my internal drive extra. I first cloned a normal ventoy usb to it with easeus(I imagine copying would be the same but to be safe), then after tried to install on linux, this gave me an error mnt folder already existed but it says it installed successfully. I can boot in uefi on my true pc using either method but bios usb boot greets me with "GR.. then a no boot grub screen on both vb and real machine. 
    In virtualbox I am getting stuck at the uefi shell when booting with efi (have created usb.vmdk, ran as admin), it does not appear to find the fs0 or default efi mapping just blk device. Is there any trick for this, would secureboot or non-secure be recommended here? What is the maximum size drive for mbr support? The drive is empty now, is there anyway to make it appear as less space to allow dual legacy mbr bios & gpt boot, or just to ventoy boot the 5tb drive from uefi in virtualbox?All works ok with a 64gb usb. I would like to dedicate around 250gb to ventoy or maximum mbr allows if possible and collect iso and store them on it as time goes by. My apologies for so many questions, any help much appreciated.

Greetings!  I have noticed that on many "tested" ISOs that when they start up, the graphics display is way out of sync and unreadable.  On some ISOs it happens all the time, some are random and many never fail.  These ISOs run fine from USB preparation tools (Rufus, etc) and from CD/DVD creations.

Any idea on where I should head with this issue?  It only happens with VENTOY... thanx!

(Using i7 4th gen with internal graphics <Intel HD Graphics 4600> and VGA)

Hello,

I've tried to inject files into windows but they don't show up

I've made an archive like this with a single file in it : sources.zip\sources\$OEM$\$1\Users\Public\Desktop

My ventoy.json is like this 

Hi,

is there a way to boot legacy only iso on UEFI Bios using ventoy?
At this moment I get always the error: