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

[SrvSum]

Can anyone help in resolving this issue??

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}

Have tried almost every solution available ?? I am not able to fix this.

Logs Msg:

00:00:03.670706 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1463) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED
00:00:03.671101 VMSetError: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87)
00:00:03.671178 NEM: Destroying partition 000000000131bc70 with its 0 VCpus...
00:00:03.675176 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805
00:00:03.675595 Console: Machine state changed to 'PoweredOff'
00:00:03.681546 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005))
00:00:04.181940 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:04.181987 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:04.182232 GUI: Aborting startup due to power up progress issue detected...

[scottgus1]

Logs should be posted full, zipped, using the forum's Upload Attachment tab.

However, this is a common error message posted regularly on this forum. A very easy way to get help is to do a search in a web browser, using the CAPITALIZED_UNDERSCORE_SPACED_WORDS, with the text "site:forums.virtualbox.org" added to restrict searching to this forum, like this:

VERR_NEM_VM_CREATE_FAILED site:forums.virtualbox.org

You'll probably end up here:
I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts. Based on my perusal of successful fixes for this problem, the silver bullet appears to be the "bcdedit" command & complete power-down in post 2 point 1.

[SrvSum]

Thanks scottgus1 for your revert, I have tried everything but all in vain, still same error persists.

[socratis]

What have you tried, exactly?
Did you pull the power plug after running the "bcedit" command for example?

[cybermario]

hi there... first time in the forum...

i got this msg when i ran a vm...

Code: Select all

Fallo al abrir una sesión para la máquina virtual issabel.

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

Código resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

any ideas? thanks in advance

[scottgus1]

To help you get underway getting a solution quick 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, like this:

VERR_NEM_VM_CREATE_FAILED site:forums.virtualbox.org

This has been common and a decent web-search will definitely get you a solid solution to this problem. You will probably end up here:
I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts. Based on my perusal of successful fixes for this problem, the silver bullet appears to be the "bcdedit" command & complete power-down in post 2 point 1.

[fogfire]

Like many people this has been driving me nuts for hours:

Start with these changes: (Just to keep all the known info in one place)

In Windows Features Turn Off:
Hyper-V
Sandbox
Containers
Virtual Machine Platform
Hypervisor Platform

Reboot:
(if you machine supports getting into BIOS here go for it
Make sure Virtualization Technology is ON
{Not something I have seen here yet]
ALSO make sure SECURE BOOT is Off. On my HP I had to remove my BIOS Supervisor PW to see these features

After you reboot
In admin PowerShell
enter: bcdedit /set hypervisorlaunchtype off

Restart Windows.

At this point, many people are going to be fine, but I think since 1903 more of us will still be pulling our hair out!!

In Admin PowerShell type:
Systeminfo

If you on the last line still see:
A hypervisor has been detected ....UGGGG!!

The final piece that some have gotten close to has to do with Windows Defender Credential Guard
It requires virtualization. It is buried in Windows and all the GPEDIT articles about turning it off.. DON'T seem to really disable, it's still there just dormant

It is the feature that is enabling a Hypervisor in the system and blocking VirtualBox and VMWARE.

This is the only way i have seen to actually turn this all the way off so that there is not a hidden hypervisor running.

This REAL way to make this go away is the LAST item on the page. I'n new so can't post URLS so you will have to edit these.
https://docs.microsoft.com/en-us/window ... iness-tool

Download the readiness tool as mentioned.
https://docs.microsoft.com/en-us/window ... iness_tool
Run the command.
.\DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot

Answer yes to the scary boot message by pressing the Windows Key

BOOM My VMs Run just fine

[scottgus1]

In admin PowerShell
enter: bcdedit /set hypervisorlaunchtype off
save and close work: a shutdown is required.
in a command prompt, run: shutdown -s -t 2 (or hold Shift down while clicking Shut Down in the Start menu)
When the computer is shut down, unplug it and go get a sandwich/coffee/restroom break,etc. Then plug in and reboot.

Added a couple things that make this whole get-rid-of-Hyper-V thing work. A complete power-down (and possibly a complete not hybrid shutdown) is sometimes necessary to ensure full acceptance of the bcdedit command. Regrettably we can't figure out if it is always necessary or whether some factors require it and some don't. But it doesn't hurt and sometimes helps.

See this:
https://www.tenforums.com/tutorials/139 ... puter.html for more info and a boot-menu method to turn Hyper-V on or off, depending on whether you need it or not.

[PenJax]

It is the feature that is enabling a Hypervisor in the system and blocking VirtualBox and VMWARE.

This is the only way i have seen to actually turn this all the way off so that there is not a hidden hypervisor running.

This REAL way to make this go away is the LAST item on the page. I'n new so can't post URLS so you will have to edit these.
https://docs.microsoft.com/en-us/window ... iness-tool

Download the readiness tool as mentioned.
https://docs.microsoft.com/en-us/window ... iness_tool
Run the command.
.\DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot

Answer yes to the scary boot message by pressing the Windows Key

BOOM My VMs Run just fine

Thanks a ton. This was the final step I needed to disable the Windows Hypervisor. I still can't figure out how Credential Guard was enabled, it must have enabled automatically from one of the Windows updates. I had been running Virtualbox no problem about 2 months ago and then this issue popped up when I tried to create a new virtual machine.

The only thing I would add is that I needed to run the Readiness Tool as an administrator in PowerShell for it to execute properly.

Thanks again for the fix!!!