virtualbox.org

Always prompted:

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

I've tried various settings. Still cannot figour out what's wrong. This is my current setting (attached). I also uninstall Windows Terminal Preview.

Is there any official documents about how to work around the failure on 1909? Thanks.

Thanks.

See 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.

Why do I have the feeling that "Windows Projected File System" may be the culprit here? Microsoft's documentation on this feature mentions:
[quote=""Windows Projected File System (ProjFS)""]The part of the file system that the provider owns, where its data is projected, is rooted in a directory called the “virtualization root”. When the provider wants to start projecting its data it starts a "virtualization instance", which is an object that manages communication between the provider and ProjFS for the set of files and directories located under a particular virtualization root.[/quote]
Can somebody with a Hyper-V capable PC, and a Windows 10 ≥ 1809 Host, confirm/refute that enabling this feature results in Hyper-V getting activated?

socratis wrote:Can somebody with a Hyper-V capable PC, and a Windows 10 ≥ 1809 Host, confirm/refute that enabling this feature results in Hyper-V getting activated?

It does not. When I enabled WPFS, it did not require a restart. And the other VM settings (VMP, VHP, Hyper-V) remained unset. When I disabled WPFS, I did get a restart prompt. After restarting, the other VM settings remained unset.

However, from my experience of installing the Windows 10 Pro 1909 update on several PCs, that process does re-activate Hyper-V support functions if Hyper-V is already already installed, but deactivated, which results in the error reported by the OP. Only the already known 'bcdedit command solution' appears to return VirtualBox functionality if a User wants to retain a dormant Hyper-V installation rather than completely obliterating all traces of it.

Thank you 'Tim Wood' for testing this, much appreciated!

'multiOS', thanks for your insight as well, it looks like the 'bcedit' command will become the "silver bullet" that 'scottgus1' is referring to in viewtopic.php?f=6&t=95759&p=463958#p464013...

This is my current setting. Still not working (same error).

Any other suggestions? Seems virtualbox 6 is not working on win10 1909, either an OS bug or a software bug.

KGG wrote:Any other suggestions?

Nope, that's it. Just go again and again through the list. You must have missed something. There's no point in making the same question again and again, because the answer is going to be the same again and again...

I am experiencing a similar problem. I run Windows 10 1909, 64 bit. I have Hyper-V enabled, because the latest version of Android Studio allows to use it for avd emulation on AMD CPUs like the one I'm using.
I've read that virtualbox 6-6.1 supports Hyper-V, and I tried it. As a matter of fact one the 64 bit guests I've configured says 'Hyper-V paravirtualization enabled'. But everytime I tried to start the vm I get this error:

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

Exit od E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I also get the same error with 32 bit guests. Apparently Virtualbox recognizes Hyper-V, but it still doesn't work. Tried 6.1 and the latest 6.1.5 developement build, same results.

That is correct. At present, VirtualBox (and also VMWare) cannot operate normally if Hyper-V is enabled because the Windows hypervisor loads before the OS, locking hardware virtualization use by other programs. See the discussion at the top of this forum.

viewtopic.php?f=6&t=90853

The only way to get this working on the same machine is to have a multiboot setup, with the Windows hypervisor launch enabled in one and disabled in the other.

For those that have tried the 64-bit tutorial but have been unable to figure out what to do, here's the core details to get rid of Hyper-V, as well as a link to how to set up the dual-boot BillG suggested, if you need Hyper-V sometimes and Virtualbox others:

The "VERR_NEM_VM_CREATE_FAILED" error means that some service in Windows 10 that uses Microsoft Hyper-V is active in your host PC OS. In most cases Hyper-V blocks Virtualbox.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Find the Command Prompt icon, right click it and choose Run As Administrator.

3. Enter this command:

bcdedit /set hypervisorlaunchtype off

4. Enter this command:

shutdown -s -t 2

5. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

Your Virtualbox should be running now. If Virtualbox still complains of the "VERR_NEM_VM_CREATE_FAILED" error, try all the steps again. If you still have the error, post back exactly what you did and we'll try to help some more.

For further info, see I have a 64bit host, but can't install 64bit guests and https://www.tenforums.com/tutorials/139 ... puter.html

In the future, 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

So, on top of all the steps listed in this thread (and the 64-bit thread everyone refers to), in order to get VBox to work on my 1909 install I had to boot into BIOS, disable secure boot, and then run the command bcdedit /set hypervisordebug off. After that, vbox FINALLY started up my vm's.