VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

[Stanzilla]

Ah yeah, the website is not updated yet but the file is already live on the servers, software-download.microsoft. com/download/pr/MediaCreationTool1903.exe

But if the point of our argument is that I am using pre-release Software then okay, we could still treat it as that as long as MS does not update their websites, fine by me. Doesn't change the fact that this will ship to many users next month.

I installed VirtualBox-6.0.5-129923-Win.exe now and will report back if anything changes after I restart my system for the setup to complete.

Edit: Yeah still broken

[Stanzilla]

Uninstalling Windows Sandbox (https://techcommunity.microsoft.com/t5/ ... a-p/301849) got rid of the error, still not able to boot my old VM fully, working on providing more details.

[socratis]

Very interesting finding @Stanzilla! From the linked article:

Prerequisites for using the feature

• Windows 10 Pro or Enterprise Insider build 18305 or later
• AMD64 architecture
• Virtualization capabilities enabled in BIOS
• At least 4GB of RAM (8GB recommended)
• At least 1 GB of free disk space (SSD recommended)
• At least 2 CPU cores (4 cores with hyperthreading recommended)

Yet another thing to add to my "disable the following" list...

[Stanzilla]

Updated VirtualBox to 6.0.6 but still unable to boot. Logs attached. No idea why

[irak]

Build 1709 18362.53
Vbox 6.0.6 r130049 (Qt5.6.2)

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}

Still NG

[SchlauFuchs]

Hi,
I get this error after updating VirtualBox 6.0.6:

Failed to open a session for the virtual machine xxxx.

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}

This box was functional until the update.

[socratis]

This box was functional until the update.

Which update? VirtualBox or the Windows pre-release?

00:00:01.838067 OS Release: 10.0.18362

You're running a Windows pre-release, which is not supported until it becomes a release and the changelog/manual says "supported", that's why I merged your topic with the thread that deals/records suck reports.

PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...

[Pedro Roseiro]

Dear all,
I'm running Windows 10 Enterprise 64 bits version 1903 (build 18362.53) and VirtualBox 6.0.6.
Before the last windows update, I could run a VM running Opensuse 64 bits without problems.
Now, as soon as start the CM, it shows an error

Failed to create session (Call to WHvSetup Partition VERR_NEM_VM_CREATE_FAILED Oxc000000d/87

I was looking in the Web and some people were saying that I should install Hyper-V and Hyper-V Platform. I have already done it and Intel VT is enabled.

Nevertheless, it keeps not working. Can anyone help please?

[socratis]

@Pedro Roseiro

I got to admit; I was really impressed that at your 1st post, you managed to find your way through the forums, and actually find the "VirtualBox on Windows Hosts" » "VirtualBox on Windows pre-releases" area!

But then you missed the related thread, one thread down from the area start!

I merged your post with the thread that you missed...

[Stanzilla]

1903 ISOS are now on MSDN, might be time to move this thread

[Jacob Klein]

Still not avail to public yet . .
This release strategy, this time around, sure is strange!

[socratis]

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

[Jacob Klein]

Well, we can continue to document the problem And devs can probably pretty easily reproduce it, if they tried, by getting Insider builds. Nothing stopping them from being proactive.

We testers will be ready to test a fix, for sure!

[Stanzilla]

So what I don't quite understand is, do VirtualBox devs work/investigate this issue? Or are you guys waiting until the "final" version is out and only then start working on it? Because that would be pretty bad.

[socratis]

@Stanzilla,
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...

As far as knowing what the devs are doing? See https://www.virtualbox.org/timeline

As far as knowing what the devs are thinking?