Ticket #18536 (new defect)

Opened 3 years ago

Last modified 2 years ago

VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362

Reported by: supra Owned by:
Component: other Version: VirtualBox 6.0.4
Keywords: Cc:
Guest type: all Host type: all


dear oracle team,

no matter which bios settings or windows settings (hyper-v on off, virtualization on off, sandbox on off, all windows additional functions on (normal) or off) I think I get this error: VERR_NEM_VM_CREATE_FAILED

I do not know any more and hope for your support. here is an inserted log to my normal settings.

Yours sincerely roman prosek

sehr geehrtes oracle team,

egal welche bios einstellungen oder windows einstellungen (hyper-v an aus, virtualisation an aus, sandbox an aus, alle windows zusatz funktionen an (normal) oder aus) ich vornehme ich bekomme diesen fehler: VERR_NEM_VM_CREATE_FAILED

ich weis nicht mehr weiter und hoffe auf ihre unterstützung. hier noch ein eingefügter log zu meinen normalen einstellungen.

mit freundlichen grüßen roman prosek


windows 7 roman-2019-04-02-22-22-59.log Download (36.5 KB) - added by supra 3 years ago.
error log of my virtual system

Change History

Changed 3 years ago by supra

error log of my virtual system

comment:1 Changed 3 years ago by Jacob Klein

Have you tried to uninstall Hyper-V, by going to:

Control Panel > Programs > Programs and Features > Turn Windows features on or off > Unselect Hyper-V > OK

... making sure to restart Windows TWICE, as my testing indicates that it actually takes 2 restarts to fully uninstall Hyper-V.

Any luck after those 2 restarts?

Note: We are tracking possibly the same issue, here in this thread:

Last edited 3 years ago by Jacob Klein (previous) (diff)

comment:2 Changed 3 years ago by socratis

I was commenting on this while Jacob was actually... posting :)
I'll include my original comment in any event, if nothing else just to CC: myself...

00:00:01.895780 OS Release: 10.0.18362 

That's a Win10 insider build. And there has been another, double-confirmed thread about this in the  "VirtualBox on Windows pre-releases" area.

Related discussion in the forums:

Please visit the forums, let's continue the discussion there. I'll simply point to my last post in the forums that summarizes the situation so far:

  • 10.0.18362 seems that it's going to be the 1903 (April 2019) Win10 official update.
  • That's around the time (2019-04-16) that I suspect that 6.0.6 and 5.2.28 are going to become available, based on Oracle's security update schedules. See
  • I think it would be wisest for the problem to have been addressed by the time that both of the releases happen...

Which means that you will have to keep a closer eye in the next couple of weeks on the Testbuilds. A really close eye...

PS. If someone of the people-with-the-right-power sees this ticket, I had to change the forums' thread title to something more appropriate compared to "trying to run virtralbox", I renamed it to "VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362", you could consider doing something similar, changing the ticket's title to something more... appropriate ;)

comment:3 Changed 3 years ago by socratis

Look in the "Control Panel" » "Programs and Features" » "Turn Windows features on or off", and make sure that the none of the following are active:

  • Application Guard
  • Credential Guard
  • Device Guard
  • <any> Guard
  • Containers
  • Hyper-V
  • Virtual Machine Platform
  • Windows Hypervisor Platform
  • Windows Sandbox
  • Windows Subsystem for Linux (WSL)

If that doesn't work, enter the following command:

bcdedit /set hypervisorlaunchtype off

followed by a cold boot, i.e. shut down the computer, pull the power plug for 10", reboot.

comment:4 Changed 3 years ago by socratis

And can someone change the title to something more meaningful, like:

"VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362"


comment:5 Changed 2 years ago by janitor

  • Summary changed from error however i try to change my system to VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use