writhziden Administrator, .NET/UWP Developer Staff member Joined May 23, 2012 Posts 2,923 Location Colorado May 29, 2019 #1 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} Click to expand... Since the steps are a bit obscure reading that thread: Go to Type here to search Type into the search textbox Turn Windows features on or off Make sure both Hyper-V and Windows Sandbox are unchecked/disabled If the system requires a restart, perform the restart. Restart a second time to ensure all Hyper-V features are disabled
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} Click to expand... Since the steps are a bit obscure reading that thread: Go to Type here to search Type into the search textbox Turn Windows features on or off Make sure both Hyper-V and Windows Sandbox are unchecked/disabled If the system requires a restart, perform the restart. Restart a second time to ensure all Hyper-V features are disabled
dharvell New member Joined Jun 11, 2019 Posts 1 Jun 11, 2019 #2 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.
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 Administrator, .NET/UWP Developer Staff member Joined May 23, 2012 Posts 2,923 Location Colorado Jun 11, 2019 #3 The only thing I can think of would be virtualization settings in the BIOS being incorrectly configured.
The only thing I can think of would be virtualization settings in the BIOS being incorrectly configured.
samuelcarreira New member Joined Jun 26, 2019 Posts 1 Jun 26, 2019 #4 Thank you writhziden, I can confirm that works on fixed my problem. details: VirtualBox-6.0.8-130520-Win (Windows 10 Pro 1903 x64)
Thank you writhziden, I can confirm that works on fixed my problem. details: VirtualBox-6.0.8-130520-Win (Windows 10 Pro 1903 x64)
Ezrav New member Joined Oct 30, 2019 Posts 1 Oct 30, 2019 #6 writhziden said: 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: Go to Type here to search Type into the search textbox Turn Windows features on or off Make sure both Hyper-V and Windows Sandbox are unchecked/disabled If the system requires a restart, perform the restart. Restart a second time to ensure all Hyper-V features are disabled Click to expand... 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...
writhziden said: 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: Go to Type here to search Type into the search textbox Turn Windows features on or off Make sure both Hyper-V and Windows Sandbox are unchecked/disabled If the system requires a restart, perform the restart. Restart a second time to ensure all Hyper-V features are disabled Click to expand... 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 New member Joined Sep 7, 2020 Posts 1 Sep 7, 2020 #7 its because virtual box sucks it always has something wrong with it