how to get Oracle vm VirtualBox 6.0 and wsl working at the same time

14
votes

when i Turn on Windows Subsystem for Linux option in Windows features on or off

VirtualBox out an error every time i run a vm

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

is there a way to fix the VirtualBox error without turn off wsl

2
windowsvirtual-machinevirtualboxwindows-subsystem-for-linux
I have this problem as well - I've tried all other fixes that I can find, and compared my system with a colleague's whose setup is the same apart from that he does not have WSL installed - he can run VMs in VirtualBox, I can't. It seems to be WSL that is preventing VMs from starting. Does anyone know if this is a known problem? – drkvogel

2 Answers

23
votes

I found it! After much research, and trial and error, here is what enabled me to run VMs in VirtualBox on Windows 10 with Windows Subsystem for Linux installed:

In an elevated (admin) cmd.exe or PowerShell, do:

bcdedit /set hypervisorlaunchtype off

and make sure Hyper-V and Windows Sandbox are disabled in Windows Features (which you can get to by entering OptionalFeatures.exe at a command prompt, or via the Control Panel).

Also, Virtualisation options should be enabled in the BIOS, and I think (I don't have time to test right now) that "Virtual Machine Platform" and "Windows Hypervisor Platform" should be enabled.

VirtualBox 6.0.14, Windows Version 10.0.18362.356.

0
votes

in november 2019, i upgraded my Windows 10 family to release 1909 (run winver to check). I wanted to use WSL2.

And then i was unable to run the VMs in Oracle Virtualbox :

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

I had to check the "Plateforme Hyper-V" in "Turn Windows features ON or OFF" And it went OK.