Can't enable secure boot for Windows 10 guest on VB Version 7.0

[Shmu26]

My Windows 10 guest has EFI boot set up and working.
And I can enable TPM v.2.
But when I try to enable Secure Boot, it says

Code: Select all

Failed to save the settings.

I want to enable secure boot so I can upgrade the guest to Windows 11 without using hacks.

Not sure if this is connected at all, but when I start the guest I get

Code: Select all

Can't enumerate USB devices

I didn't get that error message on VB version 6.1, which I was running before.
I installed the extension pack and guest additions for 7.0 but still get the error.

Host: Kubuntu 22.10
Guest: Windows 10
VB: Version 7.0.6 r155176 (Qt5.15.6)

Screenshot_20230324_131309.png (99.51 KiB) Viewed 3200 times

[Shmu26]

Maybe I need to enable secure boot in the firmware settings of the guest?
If so please provide instructions.
I spam the ESC key during startup, and then....?

[scottgus1]

Just to let you know, we're not ignoring this, we just need to wait for someone who knows the answer.

[Shmu26]

Just to let you know, we're not ignoring this, we just need to wait for someone who knows the answer.

[fth0]

I don't know the answer either, but perhaps you're interested in reading Enable secure boot by command line.

[thorsten_cgn]

Old thread, I know. But I can not find an answer and I am running into the very same problem with 7.0.14. Did this got solved by chance?
Thank you!

[Byroniac]

WARNING: what I am about to tell you is potentially unsafe for your VM, so backup the entire VM first as a precaution if you choose to proceed with this advice.

I have had this same issue, and I do not currently use Windows 10/11 guests (but plan to resume doing so in the future). As an aside, though I love VirtualBox, Windows Sandbox is available as an option for Windows 11 Pro (and 10 Pro also, I think) systems, and is a wonderful quick way to test temporary software configurations, but has no permanence (cannot save VM state, and once you shut down it returns to an immutable base image state). Now with that out of the way, continue...

When I have encountered your scenario in the past, I have proceeded to delete the .nvram file in the VM folder, then somewhere in the process of enabling Secure Boot I chose the reset security keys option. I remember times when I got it working, and times when I didn't. I cannot remember exactly what worked, only it involved deleting the .nvram file (but I remember a few times when I had to do a complete reinstall).