My laptop Secure-Boot menus contain a few places that allow me to load the ventoy .cer file, which I did (it shows up with the name "grub").  I was a bit confused during the add process though, since it prompts me for a UUID number before allowing the add.

Anyhow - I still get the red "bad sig" error and it won't boot ventoy.

Does anyone have suggestions for how to get this to work?

If you need me to help get this working, I'm happy to do screenshots and experiments etc.

Hello forum,

is he Ventoy-stick strictly read-only (r/o), or could it happen, that a booted Linux-ISO does user the stick as Swap-device, or that it does write other things to the stick?


Thank's in advance!

Harry

朋友新配一台机器，主板是：ROG STRIX Z690-A GAMING WIFI D4吹雪，用最新的引导启动机器安装时，开机后黑屏状态，无菜单出现。
改用win iso做的引导U盘启动，正常
不知何故？如何解决？

如题，做好的u盘启动后，选择老毛桃或者微pe工具箱的iso，直接就进了对应的pe系统，我想先进界面，怎么办？

I have Dozens of Iso's on my External ventoy SSD.
And the Menu looks crap and is hard to sort through and therefore takes time.
So i need help in creating a Decent Menu.
I am a Die Hard Windows User.
I have used linux a bit but I get lost very easy.
Can someone help me with info about building a menu using windows 10.
And then Transferring it over to the Ventoy SSD

all,
I'm attempting to install a distribution of linux. I have previously use Ventoy to install Alma linux, but I need to intsall another distribution, so thats that. My issue is that when I boot into the Ventoy Menu, which looks like it installed correctly, the bootable .iso isn't available. Currently the flash drive I'm using is a 32gig onn. and has two partitions listed as sda1 and 2. 1 is 28.9 GiB and 2 is 32 Mib, and this is where the ventoy tool seems to live. I hope you can help me with my dilema, its a bit strange to me.

使用ventoy引导wepe，进入wepe后无法弹出usb驱动器，仅使用wepe的情况下是可以做到弹出usb驱动器的
倒并不影响正常使用，只是有些情况下需要提前移除USB驱动器避免重启时再次进入u盘引导，不然只能点完重启拼手速再拔U盘了
请问这个问题是正常现像吗？希望可以解下困惑，谢谢

long panda you should read this 

------------------------------------------------------


Some signed third-party bootloaders for the Unified Extensible Firmware Interface (UEFI) could allow attackers to execute unauthorized code in an early stage of the boot process, before the operating system loads.
Vendor-specific bootloaders used by Windows were found to be vulnerable while the status of almost a dozen others is currently unknown.
Threat actors could exploit the security issue to establish persistence on a target system that cannot be removed by reinstalling the operating system (OS).
Elysium security researchers Mickey Shkatov and Jesse Michael discovered vulnerabilities affecting UEFI bootloaders from third-party vendors that could be exploited to bypass the Secure Boot feature on Windows machines.
Secure Boot is part of the UEFI specification designed to ensure that only trusted code - signed with a specific, vendor-supplied certificate - is executed to start the OS booting process.
The firmware bootloader runs immediately after turning on the system to initialize the hardware and to boot the UEFI environment responsible for launching the Windows Boot Manager.

[b]Overview of the boot process on UEFI systems[/b]
source: Microsoft

• New Horizon Datasys Inc: CVE-2022-34302 (bypass Secure Boot via custom installer)
  
  
• CryptoPro Secure Disk: CVE-2022-34301 (bypass Secure Boot via UEFI Shell execution)
  
  
• Eurosoft (UK) Ltd: CVE-2022-34303 (bypass Secure Boot via UEFI Shell execution) 
  

I properly installed (from Windows 10) Ventoy on a USB stick a couple of days ago and copied a Linux Mint iso and a Puppy Linux iso to the proper partition (reformatted as FAT32), but my computer refuses to acknowledge Ventoy.

I first tried it by accessing the boot menu from BIOS (UEFI, secure boot disabled). Selecting the proper boot option does nothing and I return to the BIOS screen. When I select Windows, it boots up normally. I tried switching the correct boot option to the top of the boot priority, saved and exited, but it still booted to Windows as if the option didn't exist. I also tried to boot again directly from the boot menu this time (instead of accessing the boot menu from BIOS), it still didn't work. 

I have live-booted Linux Mint on this machine from this same USB stick previously (I used Etcher then) so I don't think it's a hardware problem either. Can anyone help me? This is my first time posting to a forum like this, so I hope I have provided all the information needed.

1) During install, if MBR is chosen, does Ventoy write to the "hidden track 0" some boot code
2) Technically curious - how does Ventoy boot in BIOS mode?  Does the MBR pass control to a program in the VToyEFI partition and if so, is it the same program that Bootx64.efi passes control to in UEFI mode?