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


This question is SIMILAR to this post, but the solution presented there isn't applicable because I have Windows 10 Home and not Pro. The Hyper-V & Windows Sandbox deactivation solution that the accepted answer leans on isn't available for me.

OS: Windows 10 64bit, Version 1909, Build 18363.476 (19H2)

Before upgrading windows from version 1903 to 1909, everything I needed to do with VirtualBox was working well, but it seems I've encountered some post-upgrade issues. When trying to start my VirtualBox Ubuntu VM, I get the following error message:

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}

I've tracked down a resource on the forums which leads me to believe the problem could be related to the fact that I've been trying out the Windows Terminal Preview on my computer, but I can't figure out how to resolve the problem because the solution presented also relies on disabling Hyper-V in the Windows Features manager, which isn't an option for me.

enter image description here

Does anyone know how to fix this problem? All of the literature I've been able to find online relies on disabling Hyper-V either temporarily or permanently. Is there a way to do this safely from a PowerShell prompt?

asked on Super User Nov 16, 2019 by ifconfig

3 Answers


You need to go into Windows Features and uncheck BOTH Hyper-V as well as Containers. I had the same error message as you, but after removing the Containers option, everything worked like normal.

Let me know if this works for you. enter image description here

answered on Super User Jan 24, 2020 by gman

I'm using windows 10 home and I didn't have Containers and Hyper-V feature, but I disabled Virtual machine platform and Windows Hypervisor platform and that made the problem go away without having to re-install VirtualBox.

answered on Super User Jan 10, 2021 by Papaya-Automaton • edited Jan 10, 2021 by Papaya-Automaton

RUN > CMD > bcdedit /set hypervisorlaunchtype off then reboot host machine.

answered on Super User Jan 7, 2021 by FullStackDev

User contributions licensed under CC BY-SA 3.0