I tested live linux BEE free 20.04 2020-08-01 (based on Ubuntu) with ventoy-1.0.18.
ISO: BEE-free-20.04-2020-08-01.iso (3.4 GB)
Download: download
DistroWatch info: info
Site: site
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

Hi,

I love ventoy.
But there's a problem I have.

I made an Multiboot-USB Stick. With ventoy so easy.
But if I edit an ISO the error: "No bootfile found for UEFI! Maybe the image does not support X64 UEFI!" occured.

In this case it's Acronis 2019.
Inside iso is a file for Mac: AcronisTrueImage2019-17000.dmg
I delete this one to safe space. Now I bood end get the error.

Kaspersky rescue disc the same.

But I did the same thing with Acronis 2017 ago... this worked fine.

I use PowerISO or UltraIso to edit the isos.

Can someone help me with this?

Best regards

I've installed Ventoy onto two different USB drives and both fail to boot on an i386.  I get "GR" in the upper left corner, then an error message about an invalid file system, and then it dumps me into a GRUB recovery command prompt.  The USB drives were 16 GB and 2 GB.  Both written successfully with the Windows version of the installer.

I was able to get the drives to boot on a newer x64 system and everything appeared to work properly there.  I was building the USB drive to stick some utilities on, like Clonezilla and DBAN, so it's not super-critical for it to work on "antique" hardware.  It didn't work and I'm trying to understand why.  I read the documentation pretty carefully and didn't see anything that indicated it wouldn't work on x32.

Thanks for any clarification...

I tested live Linux Kodachi 7.2 (2020-08-03) with ventoy-1.0.17/1.0.18.
ISO: kodachi-7.2-64.iso  (2.9GB)
Download: Download
Info site: info
Distrowatch info: info
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
       

I tested live BunsenLabs Linux 6 Lithium amd64 (2020-08-02) with ventoy-1.0.17/1.0.18.
ISO: lithium-1-amd.hybrid.iso  (1.2GB)
Download: 
Distrowatch info: info
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

I've tested pmagic_2020_05_20.iso and noticed a strange behavior with CloneZilla under a particular condition.  If you use the first option to launch (running from RAM), remove the flash drive after the timezone screen comes up, run Clone Disk (Clonezilla), then just after the "Shutting down the Logical Volume Manager" message, a series of these appear:

/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...

This seems to happen only if I remove the flash drive after Parted Magic launches.

This does not happen in Memdisk mode, but of course takes much longer to load.  Tested with both Ventoy 1.0.17 and 1.0.18.

I've tested also with Rufus and YUMI and something similar doesn't happen with either of those.

100 G3 64GB

Hi,
How may I have Ventoy-boot loads the keyboard and touchpad drivers of my Surface Laptop 3 ? So that ISO without boot.wim may be used?
Regards,
-Valp

I tested GeckoLinux Cinnamon x86_64-999.200729.0 (based o OpenSUSE) with ventoy-1.0.17.
ISO: GeckoLinux_ROLLING_Cinnamon.x86_64-999.200729.0.iso  (1.4GB)
Download: download
Info GeckoLinux site: info
Info DistroWatch: distrowatch info
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
           

“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/