Page 1 of 1

VM Error - WHvSetupPartition failed: (VERR_NEM_VM_CREATE_FAILED)

Posted: 1. Jul 2019, 10:21
by Zen1
Win 10 Test-2019-07-01-17-09-50.zip
(7.81 KiB) Downloaded 73 times
Win 10 Test-2019-07-01-17-09-50.zip
(7.81 KiB) Downloaded 73 times
Hi, I am receiving the below message when attempting to open VM - the same error for both Windows 10 and Ubuntu.

IT student assessment - new computer bought for VM purpose. Attempted everything prior to posting.

Failed to open a session for the virtual machine Win 10 Test.
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}
Thank you

Re: VM Error - WHvSetupPartition failed: (VERR_NEM_VM_CREATE_FAILED)

Posted: 1. Jul 2019, 14:08
by scottgus1
To help you get to your solutions faster in the future, you can try searching for the error text (the CAPITALIZED_UNDERSCORE_SPACED words) in a web browser with the text "site:forums.virtualbox.org" added to restrict searching to this forum.

So use your favorite search engine to search this:
VERR_NEM_VM_CREATE_FAILED site:forums.virtualbox.org
This is a new but common problem, has been discussed many times on the forum.

Re: VM Error - WHvSetupPartition failed: (VERR_NEM_VM_CREATE_FAILED)

Posted: 2. Jul 2019, 06:42
by Zen1
Hi, thank you for the reply.
As mentioned I have tried everything suggested in the google searches.

I have been able to eliminate some of the problems but still cant get Virtual box to open in either Windows 10 or Ubuntu.

So I uploaded to the forum with the error messages.

Is there anything else you would recommend?

Re: VM Error - WHvSetupPartition failed: (VERR_NEM_VM_CREATE_FAILED)

Posted: 2. Jul 2019, 15:39
by scottgus1
Hopefully, what you might have come across in your searches is this:
socratis wrote:Look in the "Control Panel" » "Programs and Features" » "Turn Windows features on or off", and make sure that the none of the following are active (the list keeps getting bigger by the day):
  • Application Guard
  • Credential Guard
  • Device Guard
  • <any> * Guard
  • Containers
  • Hyper-V
  • Virtual Machine Platform
  • Windows Hypervisor Platform
  • Windows Sandbox
  • Windows Subsystem for Linux (WSL)
If that doesn't work, enter the following command:
  • 
    bcdedit /set hypervisorlaunchtype off
followed by a cold boot, i.e. shut down the computer, pull the power plug for 10 seconds, reboot.
I might add that the 'bcdedit' command may have to be run in a Run-As-Admin command window.

Try all of this, it's supposed to clear up the error you're getting.