VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).
virom
Posts: 1
Joined: 28. May 2019, 01:32

Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

Post by virom »

I was using Ubuntu VirtualBox VM on 1903 without Hyper no problem at all until I enabled the Windows Sandbox feature. Then I get this error. I turned off the Sandbox feature, rebooted multiple times and still have the same problem. Why?
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

Post by Jacob Klein »

Maybe Windows Sandbox installs Hyper-V, and uninstalling Windows Sandbox does not uninstall Hyper-V.
See if you can uninstall Hyper-V, restart 2 times, then try again.
fieldar
Posts: 1
Joined: 27. Apr 2019, 11:38

Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

Post by fieldar »

I am running Virtual Box Version 6.0.8 r130520 (Qt5.6.2) on Windows 10 Pro version 1903 (OS Build 18362.116).

I have Windows 7 and a Windows 10 Insider (20H1) virtual machines. Both were running without problems until yesterday when I turned on WIndows Sandbox. After doing so both VM's gave the above error when I tried to power them up. Turning off Windows Sandbox didn't solve the problem.

My hunch was that turning on Sandox activated some part of Hyper-V which was not deactivated when Sandbox was turned off so I installed Hyper-V (no Sandbox), rebooted and then immediately uninstalled Hyper-V and rebooted twice. No more error message. Both VM's working as I expect them to.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)

Post by socratis »

fieldar wrote:on Windows 10 Pro version 1903 (OS Build 18362.116)
Windows 10 1903 is now officially released. This thread has fulfilled its purpose. No need for more posts in the "Windows prereleases" area. Locking this to avoid invalid "me too" posts.

If you have a similar problem, open a thread in the "Windows Hosts" area...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Locked