Virtualbox 6.1.16 - Guru Meditation - A critical error has occured ...

[Sanderif]

I've recently updated to Virtualbox 6.1.16 and got an error while trying to start up my newly made VM.

I tried to create a windows server 2019 64 bit virtual machine with the Windows Server 2019 ISO from the Microsoft Evaluation Center but when i start this VM it gave me the Guru Meditation error.
It is a simple 2048MB RAM with 50GB VHD dynamically allocated, nothing special...

I have a MSI P62M 7RDX Leopard laptop.

Does anybody have the same problem? Logs are uploaded as an attachment.

Tried Fixes
Vt-d is enabled. (BIOS)
Intel (VMX) Virtualization technology is enabled. (BIOS)
Re-install Virtualbox 6.1.16.

[mpack]

Your "logs.rar" attachment doesn't contain the log, and the screenshot only shows the Windows logo, no error message.

[Sanderif]

Excuse me. Here are the error logs.

Tried Fixes
Vt-d is enabled. (BIOS)
Intel (VMX) Virtualization technology is enabled. (BIOS)
Re-install Virtualbox 6.1.16.
Re-install Windows server 2019 ISO.

[mpack]

00:00:18.709376 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:18.727749 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Try to disable Hyper-v. See the related FAQ: I have a 64bit host, but can't install 64bit guests, especially posts #2 and #3.

FYI, VT-d is not a requirement. I'm surprised if an Intel focused motherboard mentions VMX, that's normally an AMD terminology AFAIK. The relevant Intel feature is VT-x (totally separate from VT-d), which the BIOS may refer to as "Virtualization technology".

[Sanderif]

I don't have Hyper-v on my laptop.

I double checked by running "dism.exe /Online /Disable-Feature:Microsoft-Hyper-V" in Ps but Hyper-V is unknown.

I can not find the VT-x option in my BIOS. Strange...

[mpack]

I don't have Hyper-v on my laptop.

Yes you do, otherwise the log wouldn't say so. Please read the FAQ I referenced.

[Sanderif]

You were right. Running "bcdedit /set hypervisorlaunchtype off" in cmd fixed the problem. I couldn't find hyper-v in OptionalFeatures.exe so i thought i didn't have it.

Thanks for saving me!