VirtualBox 6.0.12 does not work anymore since Hyper-V was installed

[jmar83_the2nd]

..and so i know VirtualBox 6.0.x should run together with Hyper-V without any problems??

I used that command "DISM.exe /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V /NoRestart", then restarted Win10 host system and after the next start, the VMs won't start anymore.

Message:

Für die virtuelle Maschine windows server 2003 x32 konnte keine neue Sitzung eröffnet werden.

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

...and also the same problem when i select "Hyper-V" on paravirtualization settings. (Default value was: "predefined" (In my german GUI: "voreingestellt"))

Why it does not work together? On https://superuser.com/questions/1299022 ... ysical-nic and many other texts i read it works togther. But it works NOT.

How to solve that issue? (I wanna try using the virtual network adapters of Hyper-V in VirtualBox, because of that i need it!) Thank you for your feedbacks! :-)

[jmar83_the2nd]

"bcdedit /set hypervisorlaunchtype off" seems to work for bypassing the problem: https://github.com/kubernetes/minikube/issues/4587

[BillG]

Correct.Enabling Hyper-V blocks most VirtualBox guests because the hypervisor loads at boot time. Hyper-V can still use VT-x/AMD-V through the hypervisor but other programs like VirtualBox cannot. Preventing the hypervisor from loading allows VirtualBox to work (but prevents Hyper-V guests from running).

[jmar83_the2nd]

Thank you for your feedback.

[socratis]

i know VirtualBox 6.0.x should run together with Hyper-V without any problems??

Not true. It's an experimental feature, and we still don't know in which cases it works. I have yet to see a successful one.

That includes the article you linked to, I didn't see a successful co-existence...

[jmar83_the2nd]

Thank you for your feedback.