Please Ms can you employ people who understand Virtual Machines.

Hi there
It;s bonkers that if on new W11 installs they are going to insist secure boot is enabled but if you create a brand new Virtual machine with boot options "Secure boot enabled" then your wretched iso's don't boot on some older machines !!!!!!!!!! --- If you just select UEFI then it's all kosher -- but c'mon you need to get your act together here. VM's are no longer "Eseoteric" these days but very much part of even home users testing.

"A rant at Ms a day -- keeps happiness at Maximum today" !!!!

Cheers
jimbo

jimbo45 said:

Hi there
It;s bonkers that if on new W11 installs they are going to insist secure boot is enabled but if you create a brand new Virtual machine with boot options "Secure boot enabled" then your wretched iso's don't boot on some older machines !!!!!!!!!! --- If you just select UEFI then it's all kosher -- but c'mon you need to get your act together here. VM's are no longer "Eseoteric" these days but very much part of even home users testing.

"A rant at Ms a day -- keeps happiness at Maximum today" !!!!

Cheers
jimbo

Click to expand...

I do not get your point.

On Hyper-V, you can always set secure boot even if host pc is 100% legacy bios. My old lenovo can be set to boot in legacy bios only (it can also be set to boot from uefi or legacy depending on what is on drive). None of this affects having a uefi vm in hyper-V with secure boot.

Maybe your issue is with you vm software actually using host secure boot status?

In the end, what is point of using W11 on really old devices anyway. This is a bit like saying you want your car to use a carburettor as well as fuel injection. I have no idea if that is even possible, but it would be a waste of space.

Not to mention this is nowhere near a new problem. Older boot discs have come with a caveat to disable secure boot when installing, and this includes OSs of all flavors. Secure boot isn't something new.

FWIW, I'm working my way through a Gentoo install in both a gen 1 and a gen 2 VM, and simply not enabling Secure boot when installing works perfectly fine in the gen 2 VM. You can always enable it later - just like you could always disable it in the BIOS / UEFI firmware settings on bare metal, install, then go back and enable it.

So, yeah, agreed, not seeing what the issue is here.