Script install menu bug.

If I go to the script install menu and then go back to the previous step, nothing happens.
All F1 to F6 keys do not work.

It doesn't work only in the script install menu.

How to make kon-boot bootable from uefi and/or legacy 
how to add files from folder efi>boot "bootia32.efi" "bootx64.efi"......? 
and usbfiles "konboot.img" "grldr"....... ?

I will use plugins but i dont understand how to install this. I have read the help but i dont understand this. In the FAQ i read this: ventoy.json should be placed at the 1st partition
But i see only one partiton where is my iso. I use Windows 10.

Dear Concern,

            At first I say Very very thank you for making such a great software. Recently i Purchased 256 GB Sandisk Pen drive for all ISO Boot, But some ISO's not booting in this i listed the names of the ISO please Make a Support of it and release a update of ventoy.

all_windows_dvd_1 (Contains Win95,98)
all_windows_dvd_2 (Contains Windows 2003)
android-x86_64-9.0-r2
android-x86-9.0-r2
Remix_OS_for_PC_Android_M_32bit_B2016112201
Remix_OS_for_PC_Android_M_64bit_B2016112101
Windows 10 Pro X64 21H1 Compact & SuperSlim [19043.1023]
Windows Me
Xtreme.LiteOS.7.x64
en_windows_vista_sp2_x64_dvd_342267
en_windows_vista_sp2_x86_dvd_342266 


If you please give me a reply then i will be highly obliged to you

1.0.46 version bug

Hidden Shortcuts
F1/Ctrl+IWRU

After applying the theme
Shortcut keys on first boot
"s?" is expressed.

If I use the hotkey again after switching to another mode in this state, it works fine.

{
    "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?