Resolving issue: Oracle Virtual Box and Windows 10 – Call to WHvSetupPartition failed VERR_NEM_VM_CREATE_FAILED

Lucas Jellema 10
0 0
Read Time:2 Minute, 10 Second

Like so many colleagues and fellow developers around the world, the latest Windows Update also messed up my machine’s ability to successfully run Oracle Virtual Box. When running vagrant to provision a VM, I ran into messages such as:

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: ConsoleWrapInterface: IConsole

When I tried to open a VM in the Oracle Virtual Box GUI that used to run fine before the Windows Update (to Windows 1903), I got a similar error.

Following the instructions in the Forum Thread (and to disable absolutely everything in Windows that has any connection with Hyper-V, I was not able to solve the issue – although I guess these steps are required too – and they seem to be enough for many users:

Make sure none of these Windows Programs or Features are running:


Application Guard
Credential Guard
Device Guard
<any> * Guard
Virtual Machine Platform
Windows Hypervisor Platform
Windows Sandbox
Windows Subsystem for Linux (WSL)

And to disable Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of Windows 10 is necessary. And sometimes to be sure a cold reboot and even more than one.

Thanks to my colleague, André van Winssen, I learned about these steps that finally resolved my situation:

  1. go to and download the ” Device Guard and Credential Guard hardware readiness tool “
  2. unzip it.
  3. start powershell as admin in the directory that contains the unzipped archive contents.
  4. run script with parameter -disable (see image below)
  5. reboot the machine; in the boot-sequence, press F3 when prompted to really disable the Device Guard


    press F3. Then press any key to continue.


    Press F3. Then


    Press any key. The reboot continues
  6. after Windows comes back again, I can now run and provision VMs again with Virtual Box

Edit: After update to Windows : December 10, 2019—KB4530684 (OS Builds 18362.535 and 18363.535), my VirtualBox again would not start. Again, my colleague André van Winssen figured out the solution: (basically reiterating through this article):

  1. ensure all Windows Features are turned off that bear any relationship to hypervisor
  2. run the DG_Readiness_Tool_v3.6.ps1 tool in PowerShell as admin
  3. reboot and confirm disabling Virtualization Based Security Opt Out Tool and Credential Guard Opt Out tool

About Post Author

Lucas Jellema

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
0 %
0 %
0 %
0 %
0 %
0 %

Average Rating

5 Star
4 Star
3 Star
2 Star
1 Star

10 thoughts on “Resolving issue: Oracle Virtual Box and Windows 10 – Call to WHvSetupPartition failed VERR_NEM_VM_CREATE_FAILED

  1. I get the same error message when I am running out of memory. In my case I stopped the VM and 30 minutes later wanted to start it which resulted in the same error message (Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005)))
    After several tries (and knowing that hyper-v was not change in the meantime) I killed Firefox after noticing it was consuming 4 GB of RAM) and afterwards I was able to start the VM again.
    So this seems to be a quite general error message for ressources not being available to VirtualBox which can be caused by a number of reasons.
    Thanks still for the article because I think it is a good summary of what you need to do to use VirtualBox under Windows 10 considering Hyper-V.

  2. Copy-Item : Não é possível localizar a unidade. Não existe uma unidade com o nome ‘V’.
    No C:\Users\Intel\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:1246 caractere:22
    + … CmdOutput = Copy-Item “$env:windir\System32\SecConfig.efi” $FreeDrive …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (V:String) [Copy-Item], DriveNotFoundException
    + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

    Lucas, I have this problem, do you know how i can fix this?
    ps: the first two sentences are in Portuguese, I’m from Brazil hahahaha.
    ps.2: the translation is “The drive cannot be located. There is no unit with the name ‘V’.”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Next Post

Java Microservices: What do you need to tweak to optimize throughput and response times?

Performance tuning usually goes something like followed: a performance problem occurs an experienced person knows what is probably the cause and suggests a specific change baseline performance is determined, the change is applied, and performance is measured again if the performance has improved compared to the baseline, keep the change, […]
%d bloggers like this: