“BootHole” vulnerability in the GRUB2 bootloader opens up Windows and Linux devices using Secure Boot to attack. All operating systems using GRUB2 with Secure Boot must release new installers and bootloaders.

The vulnerability affects systems using Secure Boot, even if they are not using GRUB2. Almost all signed versions of GRUB2 are vulnerable, meaning virtually every Linux distribution is affected. In addition, GRUB2 supports other operating systems, kernels and hypervisors such as Xen. The problem also extends to any Windows device that uses Secure Boot with the standard Microsoft Third Party UEFI Certificate Authority. Thus the majority of laptops, desktops, servers and workstations are affected, as well as network appliances and other special purpose equipment used in industrial, healthcare, financial and other industries. This vulnerability makes these devices susceptible to attackers such as the threat actors recently discovered using malicious UEFI bootloaders.

https://eclypsium.com/2020/07/29/theres-...-the-boot/

How to write json syntax to add icons for shutdown and MemdIsk, Instead of the current caption (see attached screenshot),

I saw here that it is possible to do this .. I would be happy if you could expand a bit

Attached Files

Thumbnail(s)
   

AOMEI.Backupper.Technician.Plus.5.6.0_UEFI.iso Refuses to boot with both version v5.6.0 and v5.8.0 (In UEFI)
If my memory does not mislead me VENTOY V1.0.16 was correct,

Attaches a screenshot of the error received

Attached Files

Thumbnail(s)
   

测试发现，列表模式下 VTOY_DEFAULT_IMAGE 默认选择无效；
如下配置中，不管怎么修改 VTOY_DEFAULT_IMAGE，被选择的始终是排在第一位的ISO
测试版本：ventoy-1.0.17

{
    "control": [
        { "VTOY_DEFAULT_MENU_MODE": "1" },
        { "VTOY_FILT_DOT_UNDERSCORE_FILE": "1" },
        { "VTOY_DEFAULT_SEARCH_ROOT": "/ventoy" },
        { "VTOY_MENU_TIMEOUT": "10" },
        { "VTOY_DEFAULT_IMAGE": "WePE_V2.1.iso" }
    ],
    "menu_alias": [
        {
            "image": "/ventoy/WePE_64_V2.1.iso",
            "alias": "微PE工具箱V2.1 64位"
        },
        {
            "image": "/ventoy/WePE_V2.1.iso",
            "alias": "微PE工具箱V2.1 32及64位"
        }
    ]
}

Good evening,

I would like to know if it would be possible today or in the future to plan the launch of a VHD via Ventoy.

Thank you in advance for your answers.

In version 1.0.16 and 1.0.17 and 1.0.18 Win10XPE starts loading but fails about a quarter of he way .
error says disk was removed.
Version 1.0.14 and 1.0.15 work fine

here is the error

Attached Files

Thumbnail(s)
   

如果有多余的精力的话有时间的话希望可以
先谢过大佬
这是官网链接
https://fydeos.com/download

Can't remember if the 8GB USB was created using Ventroy for Windows OR Ventoy for Linux.

BUT, I got the following when running Ventoy for Linux v1017. 

1. Curious: Does Ventoy maintain a config file or a logfile in the USB signaling the how/options used to create the USB?
   
2. Edit: A subsequent run was done to insure continuing "Secure Boot" was included in USB boot needs: Same bug outcome.
   

Can VENTOY boot to UEFI32 and UEFI64 ?   If so, does it do it automatically? Or, do I have to do something to get it to boot in UEFI 32-bit bootloader? 

Thanks
Michael

Inspired by an user @aaronpriest from this forum:
===============================

Today I've tested successfully booting WIN-10_LITE.VHD from VENTOY.

Here's what I did:
1.Install Windows-10 (I tried with Lite Version) using Virtual Box on VHD (Dynamic Disk).
2.Put grubfm_multiarch.iso in VENTOY.
Optional : If you have enough space in your VENTOY Disk, then Copy VHD file else you can locate from VENTOY to your Internal HDD
3.Boot Ventoy.
4.Run grubfm_multiarch.iso
5.Locate the VHD & Boot from it.

P.S. As off now VHD Boot is possible only through grubfm_multiarch.iso, if the Developer of VENTOY could implement this feature then it would be another BANG for us...