I'm working on building some custom tools built around wiping data and installing Windows 10 on laptops. Thankfully Ventoy has made this totally possible in an "All on one USB stick" method, but I am hoping to make the operation of the tool a bit more user-proof.

For information, here is my order of events:
1. Boot the laptop to the Ventoy drive.
2. Select to boot to a Linux Mint iso (we are just using the live disk environment at the moment)
    Ventoy handily injects script files we need to record information about the device, collect serial numbers, wipe SATA drives etc etc.
3. Reboot the computer to the Ventoy drive
4. Select to boot Windows 10 with an automated install.

I'm hoping there is a way that I can automate the movement between steps 2 and 4 above.

As in, I want to tell Ventoy to only boot to a certain option after I perform a task inside of the Linux Live Disk.

Initially, I was thinking I could edit the ventoy.json file from inside the live disk to adjust the available boot options and auto selection/timeout options (i.e. making Windows.iso select automatically after 1 second) however, trying to mount the Ventoy partition while inside the live disk has proven problematic.

Is there any recommendations about how I might be able to accomplish telling Ventoy to boot to certain .iso files based on various conditions?

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.

Ventoy simulates booting images (iso,wim,vdisk,img...) like the hardware system boots those images, so it cannot boot images (iso,wim,vdisk,img...) from vdisk For example, when you boot medicat.vhd.vtoy or medicat.img from ventoy, it will boot into ventoy on medicat.img or medicat.vhd.vtoy and give the same headings as in ventoy, then if you choose to boot another item from the images (iso,wim,vdisk,img...) then the system will stop or restart

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)