Enrolling the Secure Boot key with Super UEFIinSecureBoot Disk v3-3.
It works fine on a Dell Optiplex Micro PC.
Is there a tool or a good guide to remove the Secure Boot key again? For example before selling the PC.

• 2022/06/19 --- 1.0.77 发布
  

1. Support variables expansion in auto installation script. Notes
   
   
2. Fix the UEFI memory alloc failure in some computer. (#1671)
   
   
3. Fix the issue that install media not recognized when install Clear Linux. (#1674)
   
   
4. Fix a bug when booting daphile-21.01
   
   
5. languages.json update
   

I'm using vtoy_boot (Linux vdisk boot) plugin to boot to MX Linux from my drive. I wanted to ask where does the plugin mount the partition within the linux where the vdisk (vhd) file resides.

For ex. My vhd is in the first partition of the disk. When I boot to it I can access the rest of the partitions but the first one is never accessible. It cannot be mounted, but I reckon that it must be mounted somewhere to let ventoy boot from it.  I need to access the partition regardless. 

Same thing happens with booting Linux ISOs from a disk partition. When I do that I cannot access that partition anymore.

Ventoy 1.0.7.6 (today's release) has an interesting bug here ... 

My motherboard is an MSI B550 A-Pro with the latest Beta BIOS (AGESA 1.2.0.7). After upgrading my Ventoy USB stick and enabling Secure Boot, I rebooted my machine to enable Secure Boot in my BIOS and attempt to enroll the key. Upon entering the BIOS, the language settings becoming a hodgepodge of Chinese, Spanish, and English that navigation for me was impossible!   

https://i.imgur.com/D1PTyI7.jpg
https://i.imgur.com/FXXz4WA.jpg
https://i.imgur.com/oZ2Bi7S.jpg

Once the Ventoy USB is removed and the PC is rebooted back into BIOS, the issue is gone - everything is in English. 
However, if the Ventoy USB stick is re-inserted and I enter BIOS after another reboot, the corrupted language issue resurfaces. 

I'm positive that this issue can be recreated across all MSI B550 and X570 motherboards and isn't unique to my B550 A-Pro ... 

Furthermore, as long as my Boot Device Order was set to UEFI USB stick first followed by Windows Manager (i.e my M.2 drive), if I let my motherboard attempt to boot the Ventoy stick since it's first in the boot order, a blue OK box appears in the lower right corner. If I press ENTER, two "unable to boot file" errors appear in white text near the center of my screen and a 10 second boot countdown occurs, after which my M.2 drive is booted and I'm back into Windows. Since this is a continuous loop, the issue prevented me from enrolling the key. But I stumbled on a solution by accident. I set my Boot Device Order in my BIOS to M.2. drive first and UEFI USB stick last, and saved my BIOS settings. Once my system restarted, I pressed F11 to bring up the Boot Override BBS and manually chose the Ventoy stick. I was then able to follow the prompts to enroll the Secure Boot key and upon reboot, Ventoy launched without issue and even booted to a Linux Mint LIVE CD! 

• 2022/06/12 --- 1.0.76 release
  

1. Enable secure boot support option by default when install Ventoy. Notes
   
   
2. Fix the issue when enrolling key for secure boot with Super UEFIinSecureBoot Disk v3-3.
   
   
3. Auto use memdisk/grub2/wimboot mode if the ISO file name contains special identifier. Notes
   
   
4. Fix a bug when booting linux vdisk (.vtoy) file in Legacy BIOS mode with F2 or ventoy_grub.cfg.
   
   
5. Support EasyOS partition resize at the first boot time.
   
   
6. Support EasyOS 4.0
   
   
7. Support Stratodesk NoTouch OS. (#1652)
   
   
8. Update languages.json
   
   
9. New ISO support (total 900+)
   

Ventoy 1.0.75 + Easy OS 4.0

The first screen goes by too fast; the second screen is about mkmod -m mode
Finding drivers
can't read 'etc/fstab': No such file or directory
Error: BOOT_FS=' ' Boot filesystem is incorrect.

That Easy does boot successfully on a conventional live USB made w/ Rufus or other.

The same Ventoy does boot successfully such as a recent Puppy Linux on Slackware base + OpenBox & LXDE components LxPupSc64 22.02.

I also have posted a question about this in the EasyOS section of the Puppy forum, but no answer there so far.

Hi!
I'm trying to boot ventoy on a UEFI system but when on version 1.0.75 it doesn't work. 1.0.74 enrolls its key just fine but 1.0.75 doesn't. The menu asks for a valid key file extension, despite it showing the key in the directory.
Again, 1.0.74 enrolls its key just fine and dandy. I'm using a Dell Inspiron 5547 laptop with the latest bios update.

Ventoy & Grub2FM Multiboot With Original Files

Download Link

With this script you will be able to use both multiboot builds together using the original Grub2FM and Ventoy files.
Installing to USB or disks is enough for 1-2 clicks.

Hi,
I have a set of Windows ISO that don't boot properly in normal mode but boot fine in WIMBOOT mode.
Is there a way to "mark" an ISO file to automatically use the WIMBOOT mode without additional action?

Thanks

Hallo,
one way to make a copy/backup/clone of the ventoy-stick is to install ventoy onto the new stick and then to copy the files with robocopy or rsync, or to use dd, gparted, clonezilla, ... to copy the whole partition to the new stick.

It would be nice to have from within the ventoy-start-menu the function to clone and compare the stick in use, to a device that is at least as great as the source.