VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

[azimut]

the same problem on 1903 - 18862.86

[Stanzilla]

the same problem on 1903 - 18862.86

Does it work if you disable Windows Defender and Control Flow Guard?

[azimut]

in 1809 every works fine.
in bcdedit there is hypervisorlaunchtype Auto
I dont have Windows Defender enabled.
also, from new features in 1903 I set Windows Sandbox feature.
how I know, the Sandbox is also like a VM. Maybe is this a problem?

[socratis]

in 1809 every works fine.

Seriously? Did you notice that we are in the Windows pre-releases area? Which at this point in means 1903 and not 1809?

how I know, the Sandbox is also like a VM. Maybe is this a problem?

Start by reading this thread from the beginning!!! Seriously...

[azimut]

don't panic, sir)
the 1903 is official released for MSDN subscribers, you can google it like 1903 msdn and will find out more interesting)

[socratis]

I urge you once more... instead of wasting time replying, please take 5' to read the thread from the beginning:

Unless you hear from a poster that has an "Oracle Corp." on the right side of the post in their Profile, the rest can only be an educated guess... And since I've been "educating" myself for quite some time, I can "guesstimate" that there will be nothing official (as far as VirtualBox goes) until there's a final 1903. Doesn't make sense otherwise...

The thread is going nowhere, until we all have our hands on the final, *and* there's a new version of VirtualBox that specifically and explicitly declares 1903 as supported.

And I don't mean a test or a development build...

You're running a Windows pre-release, which is not supported until it becomes a release and the changelog/manual says "supported"

I wonder how many times I have to repeat this, honestly...

[azimut]

ok

[Djnjd9]

HELP! My PC Has Hyper V And I Tried Everything! It Broke After The Update With This Update (And every update) !!! I've Also Tried Every Other Good Software But Most Of Them Worked For A Week Like This One When I Installed It! I've made a little video that i cant show you because im new if you want to see what happens.

[Jacob Klein]

If you don't require Hyper-V, then...
Did you try going to Control Panel > Programs > Programs and Features > "Turn Windows features on or off"
... to uninstall Hyper-V, and restart twice?

[mojicajosef]

Using VirtualBox 6.08_r130520(Qt5.62) on a Windows 10 laptop running Windows 10 Insider Preview Evaluation Copy. Build 18898.rs_prerelease.190510-1634. A couple of days the Virtualbox was working with the new Windows 10 Insider Preview now I get errors on both of my VDI Linux (Ubuntu 18.04) and my Windows Server (2019) the error: Failed to open a session for the virtual machine Linux.

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}

Failed to open a session for the virtual machine Server 2019.

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}

[socratis]

@mojicajosef
Please search before opening a new thread. I merged your thread with the existing 70-posts one...

[mojicajosef]

I do apologize, the reason I posted this is because I did a research and did not find anyone with the same error: Failed to open a session for the virtual machine Server 2019.

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}

[socratis]

I'm sorry, but what in the seven kingdoms are you talking about? Did you read the thread? From the beginning? And you didn't see the same error? In the very first post of the thread? Seriously now???

[Arevi]

It looks like as of today 1903 is the general release build, so this would no longer be considered a pre-release OS build. Is there any news of a fix coming down the pipeline?

[azimut]

It looks like as of today 1903 is the general release build, so this would no longer be considered a pre-release OS build. Is there any news of a fix coming down the pipeline?

Have you tried to disable Windows Defender and Control Flow Guard?
I decided to restore to my 1809, so I cannot try this now.
To disable "Windows Defender and Control Flow Guard" is a very complicated procedure, with some modifications of BCDedit records.
https://docs.microsoft.com/en-us/window ... ard-manage

Another solution, must be tried:
To disable Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of Windows 10 is necessary. After the reboot I was able to boot the Windows 10 VM.

To enable the Hyper-V role again use the following command:

bcdedit /set hypervisorlaunchtype auto

A reboot of of the Windows 10 is necessary.