Windows 10 Version 1903 Hyper-V Is Currently Incompatible with Virtualbox 6.0.x

[writhziden]

VirtualBox 6.0 was redesigned to work with the Hyper-V feature for Windows 10 version 1809 and higher, but it seems that support is not currently working with version 1903. I found this out firsthand, and the information to get around it is available in VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

The error that is given is:

Failed to open a session for the virtual machine ********.

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}

Since the steps are a bit obscure reading that thread:

1. Go to Type here to search
2. Type into the search textbox Turn Windows features on or off
3. Make sure both Hyper-V and Windows Sandbox are unchecked/disabled
4. If the system requires a restart, perform the restart.
5. Restart a second time to ensure all Hyper-V features are disabled

 

[dharvell]

Out of curiosity... any idea why I would be getting this same error in Windows 10 May 2019 Update, even if Hyper-V and Sandbox are both disabled, already? I'm stumped.

 

[writhziden]

The only thing I can think of would be virtualization settings in the BIOS being incorrectly configured.

 

[samuelcarreira]

Thank you writhziden, I can confirm that works on fixed my problem.
details: VirtualBox-6.0.8-130520-Win (Windows 10 Pro 1903 x64)

 

[TU9000]

I had to also disable Containers.

 

[Ezrav]

VirtualBox 6.0 was redesigned to work with the Hyper-V feature for Windows 10 version 1809 and higher, but it seems that support is not currently working with version 1903. I found this out firsthand, and the information to get around it is available in VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

The error that is given is:


Since the steps are a bit obscure reading that thread:

1. Go to Type here to search
2. Type into the search textbox Turn Windows features on or off
3. Make sure both Hyper-V and Windows Sandbox are unchecked/disabled
4. If the system requires a restart, perform the restart.
5. Restart a second time to ensure all Hyper-V features are disabled

I had the problem like this... I enabled TPM in bios first then enable tpm in virtualization settings in bios.. I have dell bios , the first tpm setting is for OS and second is for virtualization which is in virtualization settings section . my problem was resolved...

 

[htrhtrrjhytryrw]

its because virtual box sucks it always has something wrong with it