hi

i need last windows 10 64 bit last update 2021 iso image (that iso image must work with ventoy)

thanks alot

Hello,

Thank you for sharing Ventoy! And for writing such nice documentation! It is really appreciated! I have become very excited about using this tool!

Unfortunately, my first attempts recently did not go well. I have a ThinkPad T60, updated to latest BIOS (v2.27) but it does not seem to recognize the USB stick as bootable.

Ventoy is not the only software I have had trouble with, in fact I made a lengthy post at ThinkPad Forums about Booting T60 from USB. The only thing that seems to work for me is Debian Live CD, which apparently use ISOLINUX (more specifically Isohybrid).

I am very willing to test, help diagnose, etc. on my hardware, as this is something that has been bothering me for a long time now.

Alternatively, any hints where else I could research some solution would be greatly appreciated.

I hope you are enjoying your Spring Festival!

EDIT: I think this hardware is old enough that is does not support EFI whatsoever (at least there are no options in BIOS that I can see). Just old school BIOS/GPT boot. Maybe this is the problem?

I did play with some partition boot flags, of course that did not work. Not sure what else to try.

Hi everyone, I like Ventoy, it's beautiful and works great, until I decided to add the "mac os extended ed journaled" section to the Big Sur image, after that the flash drive stopped loading
I got two partitions, the first 40 GB exFAT that creates Ventoy and the second 15 GB mac os extended ed journaled, perhaps this is not done so, I'm sorry I'm not experienced in these matters, is it possible to add the ability to break a flash drive not only in exFAT in one piece?

Hello,

how can i setup ventoy to boot a image only if a partition is not found?

With grub?

Thx.

I tested live Devuan 3.1.0 „Beowulf” (based on Debian GNU/Linux) on Ventoy-1.0.35.
ISO: devuan_beowulf_3.1.0_amd64_desktop-live.iso (1.2GB)
Download and read:
download
download
Boot: Legacy/MBR, UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U

Attached Files

Thumbnail(s)
       

I tested live Siduction 21.1.0 KDE (based on Debian GNU/Linux) with Ventoy-1.0.35.
ISO: siduction-21.1.0-cblues-kde-amd64-202102141913.iso (2.8GB)
Download: download
Boot: Legacy/MBR, UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U

Attached Files

Thumbnail(s)
       

Is there a way to change the default highlighted selection for the auto installation plugin from the 1st auto install script to "boot without auto installation template"? Some times I need to use Windows installer for WinRE environment, and am always worried someday I might accidentally use wrong selection and accidentally lose someone's data.

Hi, I'm no expert in Ventoy or Linux, but I've been getting acquainted with them since a couple of years ago. One way of accomplishing that is by setting a Ventoy multiboot USB flash drive.

Most often I've been playing with MX-Linux 19.3 KDE x64 with 16 GB Persistence dat file, and so far so good saving lots of data files in the dat virtual storage for a couple of months until, I guess, I made a terrible mistake and started getting stuck at the message of the Subject above...

I have already posted in a MX Linux forum, but I was advised rather to post in a Ventoy forum.

This is how it all started:

A few days ago the system was left on for a day or two, with an extra empty flash drive attached to another USB port, when I set the system to Suspend mode in order to save a little in the electric bill, and get the system back quicker and right where it was before going to Suspend mode. Prior to turning the system back on in the day after, I decided first to replace the extra flash drive by another one, as it was not yet being used by me after all...

As a matter of fact, my guess is the system does save all current status information in regards the hardware, software, RAM and so on when going to Suspend mode, quite different from when going to shut down, of course.

Besides, now I can not either boot any other Linux in the Ventoy flash drive, neither using or not using the Persistence dat file for the MX Linux, or for any other flavor for that matter. Even the boot order in the BIOS settings has being changed intermittently for some reason beyond my reasoning.

The screen where the message is displayed is a blank one. Hitting Enter takes the cursor down like a new line (wrap). Alt-F2/F3... does not work either. Nothing can be done.

I'm writing this topic on a dual boot W7/Debian Buster, and using Dolphin I can browse the ISO and dat files in the Ventoy USB multi boot flash drive, but no any other files seen there.

I deeply appreciate if anybody knows how to address this and get the Ventoy flash drive usable again without losing any information stored in it. And, of course, without starting fresh from scratch again.

Not to mention it is a good challenge and opportunity to learn something else out of it.

Let me know of any other additional detail you might need to resolve this issue.

I can use an hex editor to do changes in the right spot if someone tells me how.

See dropbox link of the screenshots here.

First of all, thank you for Ventoy!
I have an obscure windows 10 tablet which appears to be 32 bit.
It only supports OTG USB connection and the boot manager does not recognise any USB drives.
I've managed to get into the Intel EFI shell.
My Ventoy USB is available here.

I type...

mount fs1 usb
usb:
cd efi/boot
grubx64.efi

...and I get...

"Image type X64 is not supported by this IA32 shell"

...which I presume is because the tablet is 32 bit.

How do I use Ventoy on here?

I tested (live) OpenMandriva Lx 4.2 Plasma (2021) (based on Russian linux ROSA) with Ventoy-1.0.35.
ISO: OpenMandrivaLx.4.2-plasma.x86_64.iso  (2.2GB)
Download: https://www.openmandriva.org/en/download
Boot: Legacy/MBR, UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U, AMD Radeon R9 graphic

Note:
I also tested OpenMandriva Lx 4.2 Plasma znver1 and not work (boot: Legacy MBR/UEFI), when iso start I see info "(...) microcode: no support for this CPU vendor" (see picture 3 above) and after this I see only OpenMandriva logo (see picture 4 above) and laptop restart.
ISO for test: OpenMandrivaLx.4.2-plasma.znver1.iso > download

Attached Files

Thumbnail(s)