{
    "auto_install": [
            {
            "image": "/sources/Windows_Install/Windows10 Pro x64 20H2(19042.782) GSCD 2in1.iso",
            "template": "/ventoy/script/Windows10_unattended-Mow-in.xml"
            },
            {
            "image": "/sources/Windows_Install/Windows10 Pro x64 20H2(19042.804) Lite Util.iso",
            "template": [
                    "/ventoy/script/Windows10_unattended1.xml",
                    "/ventoy/script/Windows10_unattended2.xml",
                    "/ventoy/script/Windows10_unattended3.xml",
                    "/ventoy/script/Windows10_unattended4.xml"
                    ],
            "autosel": 2
            },




"auto_install"
It doesn't seem to work.

I've reported a sample, but it doesn't work.

How do I get it to work?

I can't get the "error" on my first USB boot with Ventoy. My system is a Lenovo L580 with OS Windows 10 Pro Ver. 21H1 Comp. 19043.985. With UEFI Bios. Just start Windows 10.Iso installed on USB. I cannot access the USB priority boot option without disabling Secure Boot.
Does this mean that it is necessary to keep Secure Boot disabled in order to use Ventoy?

{ "VTOY_DEFAULT_IMAGE": "/sources/WinPE/Z-Win10PE_x64_UEFI.ISO"}

"theme": {

          "gfxmode": "1024x768",

          "display_mode": "GUI",

          "serial_param": "--unit=0 --speed=9600",

          "ventoy_left": "75%",

          "ventoy_top": "6%-7",
          "ventoy_color": "#65CBFF",




If you specify the "/sources/WinPE/Z-Win10PE_x64_UEFI.ISO" file location, the ventoy version information is output to the location set by the user.

But...


The "F6 > List Viewer Mode" hotkey option changes the ventoy version information to its original position, the lower left corner.



I don't want the ventoy version information to change in the location set by the user.

How do I fix it?

Will this issue be reflected in the next version?

Downloaded Lakka-Generic.x86_64-3.1.img.gz , extracted to ventoy partition and tried to boot but it fails with kernel mod errors related to device mapper and mounting problems.

I see that 2.3.2 is shown in the supported list of ventoy, does the new version need tweaking at ventoy end?

Tried in legacy as well as uefi ventoy boot mode, same issue.

Please suggest.

I am encountering a UEFI boot issue with a 32 GB Ventoy USB drive that I prepared. The menu with the list of ISO images appears, but when I select one I get a black screen with a white cursor, unless I boot in BIOS mode. I am using supported ISOs (Clonezilla and Manjaro Linux). Here is a screenshot of the vtdebug output:







The motherboard is an ASUS P8H67V and UEFI boot works ok with another tool called AIO Boot. What could be the problem here?

{ "VTOY_DEFAULT_IMAGE": "/sources/WinPE/Z-Win10PE_x64_UEFI.ISO"}

The ventoy version is output as a setting value in the ventoy.json file.
Default lower left version output



{ "VTOY_DEFAULT_IMAGE": "F6> Windows 10 HDD 부팅 메뉴"}

The ventoy version is not output as the value set in the ventoy.json file.
at the coordinates I set
The version is not printed.[/size]


coordinates i set I want to print the version from

I asked the following on the MX-Linux forum:
I can now successfully create a bootable Ventoy customized MX-Linux iso.
However, when I add the Ventoy "backend" persistence configuration, it
boots into an UN-customized instance!
Is there some option to boot skipping the persistence (until shutdown,
that is) ??
Thanks..

MX-Linux user 'fehlix' replied...
Justed booted up a couple of month older ventoy stick. ISTM, they
somehow have "hardcoded" the persistence option, without a way for the
user to choose whether persistence to use or not, when choosing ventoy's
persistence "backend". So I tend to agree with JayM that's rather a
ventoy issue, b/c they tweaked internal MX LiveUSB options, which was
always meant to allow the user to choose. In the way they done it (as I
see it), you can use the ventoy persistence "backend" but have not an
option to finetune. That might also be the reason why you see the
"vanilla" Live System without your data, b/c the missed to offer to the
user to copy over the saved persistence data (under/home) from the
compressed linuxfs file into the new persistence file.

Does this make sense?
Is there any way around this?

Thanks.

PaulJayD

Suggestion for ventoy installer (script and webui, app for windows):

Option to choose filesystem type for the ventoy data partition: (eg- ExFAT/NTFS/EXT/etc.)

Along with a warning for obvious limitations/pros-cons in a small message shown while installing if its an unconventional selection.

Comments from @longpanda and others appreciated.

Hello,

I would like to use TinyCore with Ventoy but when I download the ISO from the website :
http://tinycorelinux.net/12.x/x86/releas...urrent.iso

I have the following Error :
No bootfile found for UEFI!
Maybe the image does not support X64 UEFI!

Do you know how to do to use it ?
Kind regards

Hi there!



Can Ventoy be configured on an architecture not listed in the /INSTALL/tools folder? (i386, x86_64, arm, aarch64)