After Windows update KB5012170 (August 9, 2022), Ventoy can no longer be booted with Secure boot enabled.

Summary

This security update makes improvements to Secure Boot DBX for the supported Windows versions listed in the "Applies to" section. Key changes include the following:

Windows devices that has Unified Extensible Firmware Interface (UEFI) based firmware can run with Secure Boot enabled. The Secure Boot Forbidden Signature Database (DBX) prevents UEFI modules from loading. This update adds modules to the DBX.

A security feature bypass vulnerability exists in secure boot. An attacker who successfully exploited the vulnerability might bypass secure boot and load untrusted software.

This security update addresses the vulnerability by adding the signatures of the known vulnerable UEFI modules to the DBX.

KB5012170

Hello forum

tried to install Ventoy with "reserve disk space" .  

- after installing Ventoy with the -r option under Linux, I can't find this new partition and gparted does not report/see this partiton as well

- same thing under Windows (under Windows I dedicated 16GB as reserve disk space) and this is reflected in the
  Windows Filemanager (41,6GB free (of 64GB) )


Question:
Why I can't see the Reserve partiton?


Thank's a lot for any feedback!


Harry


$ sudo ./Ventoy2Disk.sh -r 8124 -i /dev/sdd

**********************************************
      Ventoy: 1.0.77  x86_64
      longpanda admin@ventoy.net
      https://www.ventoy.net
**********************************************

Disk : /dev/sdd
Model: Kingston DataTraveler 3.0 (scsi)
Size : 57 GB
Style: MBR

You will reserve 8124 MB disk space

Attention:
You will install Ventoy to /dev/sdd.
All the data on the disk /dev/sdd will be lost!!!

Continue? (y/n) y

All the data on the disk /dev/sdd will be lost!!!
Double-check. Continue? (y/n) y

Create partitions on /dev/sdd by parted in MBR style ...
Done
Wait for partitions ...
partition exist OK
create efi fat fs /dev/sdd2 ...
mkfs.fat 4.1 (2017-01-24)
success
Wait for partitions ...
Wait for /dev/sdd1//dev/sdd2 ...
/dev/sdd1 exist OK
/dev/sdd2 exist OK
partition exist OK
Format partition 1 /dev/sdd1 ...
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
mkexfatfs success
writing data to disk ...
sync data ...
esp partition processing ...

Install Ventoy to /dev/sdd successfully finished

If I used Ventoy to create the original UFD and reserved space then created a partition in this reserved space and put ISO's in it, in addition to the ISO's in the original Ventoy partition, would Ventoy find all of them/would this work?  In other words, will Ventoy search ALL partitions (exFAT, NTFS) for ISO's or only the first partition on the UFD?
--
Why: I want a fast way to keep my Ventoy CLONED UFD up to date.  Macrium supports RDC - Rapid Delta Clone - with it I can insert the original Ventoy UFD and the clone and tell it to copy over only the blocks on the UFD that have changed.  Problem is that this RDC only works with NTFS partitions.  If I reformatted the Ventoy partition from exFAT to NTFS, I guess that would work with RDC but I also have 2 FreeBSD ISO's and I don't think they would work booted from NTFS (or would they)?

So my idea is:

P1 - Ventoy (originally exFAT reformatted to NTFS + reserved space) - put all Windows ISO's here - use Macrium to keep it updated using RDC
P2 - Ventoy EFI - unchanged
P3 - User created partition from reserved space - exFAT - put ISO's that are incompatible with NTFS here

Thanks for such a great tool!!!

Ventoy 1.0.79 + Easy OS 4.3 or 4.3.3 same error.  During boot, the creating snapshot step fails w/ error: cannot find easy.sfs

This is not the same error experienced w/ 4.0 which needed more room and was achieved by using a truncate command on the .img file to expand its innards to 2G, which enables 4.0 to boot w/ Ventoy.

Even tho' the error was different, I attempted the same maneuver on 4.3, but it did not change the error problem.  Of course, I can boot the .img if I write it 'directly' w/ something like Rufus or Etcher.

我的PC上只有一个很大的硬盘，GPT，UEFI启动，已经安装了几个操作系统，还有很多空闲的分区，现在我想把Ventoy安装到这个硬盘上，就像一个普通的操作系统一样可以选择启动，这样就可以省下一笔买大容量U盘的钱了，那该多好？能办到吗？

Is it possible installing Ventoy into local disk along with other OS's? If the answer is yes that would be great! Could any one tell me how to achieve that?

Hello

In Ventoy 1.0.79 I cant´t load:

- Darik's Boot and Nuke 2.3.0
- MiniTool Partition Wizard Enterprise 12.6
- MiniTool Partition Wizard Technician12.6
- Ultimate Boot CD 5.3.9
- Hiren's BootCD 15.2

Anybody knows how to fix it?

Many thanks

Windows 10.0.19044.1288
Windows 11.0.22000.318

用 Lenovo XClarity Essentials Bootable Media Creator 生成的ISO镜像启动时无法正常进入界面，Lenovo 服务器指南的ISO镜像可以正常启动，但无法加载Windows系统镜像进行安装，不知能否做兼容处理，谢谢！
Lenovo XClarity Essentials 可启动媒体创建器下载链接：https://datacentersupport.lenovo.com/us/zc/solutions/lnvo-bomc
Lenovo XClarity Essentials UpdateXpress 下载链接：https://datacentersupport.lenovo.com/us/zc/solutions/lnvo-xpress
Lenovo 服务器指南：https://support.lenovo.com/us/zc/solutions/lnvo-guide

Hi,
I'm having a hard time getting Ventoy to work when the data partition uses nffs.
There isn't much use having a terabyte utility drive if a person can pick the damn thing up and readily access everything on it!

Also, if a person wants to experiment with MS tools on a Util partition, not using nffs is problematic!

When the 1st data partition is exfat the f'ing thing works.
When I try doing a hard boot on a machine with ntfs, there's an error that the uefi partition can't be accessed & Ventoy goes to a grub prompt.

The boot partition is 32 MB fat.

This is so ridiculous. Once a person changes the first data partition to exfat, then they have a nightmare booting vhdx images. The images work in VM Ware, VBox, and during a hard boot on a physical notebook.

I don't know what edits are necessary to fix data partition ntfs issue or getting Ventoy to boot a vhdx image without generating a stop error.

Any help would be greatly appreciated.

Phill

(07-31-2022, 05:34 AM)Digi-O Wrote: Hi,
I'm having a hard time getting Ventoy to work when the data partition uses nffs.
There isn't much use having a terabyte utility drive if a person can pick the damn thing up and readily access everything on it!

Also, if a person wants to experiment with MS tools on a Util partition, not using nffs is problematic!

When the 1st data partition is exfat the f'ing thing works.
When I try doing a hard boot on a machine with ntfs, there's an error that the uefi partition can't be accessed & Ventoy goes to a grub prompt.

The boot partition is 32 MB fat.

This is so ridiculous. Once a person changes the first data partition to exfat, then they have a nightmare booting vhdx images. The images work in VM Ware, VBox, and during a hard boot on a physical notebook.

I don't know what edits are necessary to fix data partition ntfs issue or getting Ventoy to boot a vhdx image without generating a stop error.

Any help would be greatly appreciated.

Phill

I saw there is a plugin for DUD for Linux, but was wondering if there is a way to do something similar for Windows ISOs. When doing a normal install I can load the driver from my Ventoy thumb drive at the drive selection/partition screen, but in order for my unattended installs to work I have to add new drivers with dism and resave the ISO each time a new build comes out.

• 2022/07/28 --- 1.0.79 release
  

1. Rollback Super-UEFIinSecureBoot-Disk to v3.3
   
   
2. Support Fedora CoreOS (#1727)
   
   
3. Fix a bug when rhel based distribution has an external kickstart file. (#1717)
   
   
4. Fix a bug that VTOY_LINUX_REMOUNT option doesn't take effect in openSUSE. (#1729)
   
   
5. Fix a bug that autosel option doesn't work (#1716)
   
   
6. Fix a bug for Ventoy2Disk.gtk that reserved space can not contains digit 9. (#1753)
   
   
7. Fix a bug that can not find repo when install Kylin V10SP2 Server.
   
   
8. vtoyboot-1.0.24 release. Notes
   
   
9. languages.json update
   
   
10. New ISO support (total 940+)