Hello, I am currently getting an issue booting 32 bit UEFI WinPE which has been created using the Windows 10 AIK from microsoft.

I can boot to UEFI using a 64 bit Win PE ISO created from the Windows 10 AIK but 32 bit UEFI doesn't boot, I get the message No boot file found for bootx64.efi

I checked the EFI boot folder for the 32 bit ISO and it has a file called bootia32.efi.

Please advise on this issue. Thank you.

I created my first Ventoy USB stick the other day, and while everything worked perfectly in UEFI, it just wouldn't boot in Legacy BIOS. I tested in VMware, VirtualBox, and my actual system and i got the same result with all of 'em... a blinking cursor on the top left of the screen.

I couldn't figure out what the issue was.. tried everything but still won't boot. In the end i decided to reformat the main ventoy partition with NTFS instead of exFAT, and hoped i got lucky... lo and behold it now boots successfuly with legacy BIOS!

Anyone know why it doesn't boot with exFAT? Btw i have a 2GB reserve partition formatted as FAT32, not sure if that made a difference.

It is a wonderful way that Ventoy  is installed U disk .But it is not proper in all conditions.
I want to load ventoy with grub2 as grub2 can load grubfm .

How to write color after echo -e in Ventoy ( echo -e '\e0x05 <-- back to main menu ...)

您好，龙大。。

我有一台T410，过于古老。。您见谅

没有UEFI，Ventory通过Legacy BIOS可以启动，可以看到ISO列表

但是选择ISO进入后，只剩黑屏加左上角的一个闪动光标

关于Legacy的容量限制，做了多次尝试，1G，2G，4G，8G，16G都尝试了。。

无法解决问题

特来论坛请教

Hi,

I'm testing Windows 11 iso with Ventoy 1.0.53 but when the installer wants to copy the files it gives an error that the source could not be found.
Anyone else seen this issue?

Hi!
I have 2 computers, both with the Manjaro Linux KDE.
One has a 4K desktop and the other is Full-HD.
The GUI looks really bad on the 4K desktop.
I have attached a sample.
What can I do to solve this?
Thanks in advance!
I'm sorry if my English is not good enough.

Attached Files

Thumbnail(s)
   

Hi, 
Anyone can help me with this error?

Attached Files

Thumbnail(s)
   

I am running Ventoy 1.0.53.

I just got my Ventoy USB drive working with Secure Boot. It was painful to get the MOK keys registered, but I finally figured out a work-around (Not Ventoy's issue, I know).

Now that I have my Ventoy USB working with Secure Boot, I started trying out all my ISO images to see how they ran.

I ran into a problem with my Ubuntu 20.04 ISO with a persistent image enabled.

When booting Ubuntu 20.04, I saw the following MOKManager failure:

Verification failed: (0x1A) Security Violation

Is this a known issue with Ubuntu and Secure Boot?

Thanks,

AzJazz

Hi!

First, thanks a lot for developing this innovative USB boot tool.

My goal is to create a bootable USB drive with a customized Ubuntu Linux 20.04 based on VirtualBox images. It shall work on a (quite recent) Notebook
model called Tongfang GM7NG0R (https://noteb.com/?model/model.php?conf=...299&ex=USD). It is the first notebook I have which has no legacy boot support (so UEFI only, but secure boot is disabled).

What I did: I downloaded the Ubuntu ISO (ubuntu-20.04.3-desktop-amd64.iso) and installed it into a fixed-size VDI image as described on the "Linux vDisk Boot Plugin" page. EFI mode has been activated before installation, and the most recent vtoyboot script run. When I boot the USB and select the *.vdi.vtoy image, I see a short black screen and then the system immediately restarts. However, booting the exact same image (on the same USB drive) works fine on other Legacy Boot notebooks, and also on one other UEFI boot machine. Interestingly, on the "problematic" Tonfgang notebook, it is possible to boot the original Ubuntu ISO file using Ventoy.

What could I do to "debug" or resolve the issue? Any help to boot a vDisk on this notebook would be appreciated.