Ventoy icon indicating copy to clipboard operation
Ventoy copied to clipboard

[issue]: Booting Windows installed on SSD

Open 4iMh9CawHdyu opened this issue 2 years ago • 2 comments

Official FAQ

  • [X] I have checked the official FAQ.

Ventoy Version

1.0.71

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

UEFI Mode

Partition Style

MBR

Disk Capacity

128GB

Disk Manufacturer

No response

Image file checksum (if applicable)

None

Image file download link (if applicable)

No response

What happened?

I keep Windows on the SSD just in case i need it for software that I can't find an equivalent in Linux (not much!). In any case, on all Ventoy versions up to 1.0.71, Windows on my SSD boots fine after selecting it from the F4 options, a version higher than that qll the way up to the latest one and it doesn't, it just hangs. Thought i would mention it, obviously I'm using 1.0.71 at the moment.

4iMh9CawHdyu avatar Dec 30 '22 09:12 4iMh9CawHdyu

The F4 local boot feature corresponds to the following file: https://github.com/ventoy/Ventoy/blob/master/INSTALL/grub/localboot.cfg

This file was not modified at least on 1.0.71 and 1.0.72. So I don't know why 1.0.71 works OK but 1.0.72 fails.

ventoy avatar Jan 03 '23 06:01 ventoy

It is a Secure Boot issue; I hadn't mentioned it before because I just recently found out. If I disable Secure Boot the problem disappears.... I have before and do so now made sure that I check Secure Boot on the Ventoy Installer and it works ok with 1.0.71... so with a 1.0.86 installation, secure boot enabled in the installer and UEFI with Secure Boot for Microsoft and 3rd Party, I tried again about 5 times and it keeps booting me into the Bitlocker unlock screen.I know the password entered is correct, it works with 1.0.71; with 1.0.86 it restarts back onto Bitlocker password screen. About 2-3 months ago I tested many versions and if I remember correctly it was from 1.0.72 onwards that the problem appeared.

Many, many thanks for a great little program.

4iMh9CawHdyu avatar Jan 03 '23 21:01 4iMh9CawHdyu