VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).
Locked
TomL12953
Posts: 38
Joined: 16. Mar 2012, 03:15
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Commodore OS, Win 8

VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by TomL12953 »

As the title says, I get this error when starting a virtual machine:

Failed to get device handle and/or partition
ID for 000000000174d500 (hPartitionDevice=0000000000000be4,
Last=0xc0000002/1)
(VERR_NEM_VM_CREATE_FAILED).

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

I've attached the log file
Attachments
VBox.log
(41.39 KiB) Downloaded 189 times
ViGe
Posts: 2
Joined: 17. Apr 2020, 13:27

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by ViGe »

We run into this as well. Running latest VirtualBox (6.1.16) on a Windows 10 machine running the Insider Preview builds, Hyper-V enabled. None of the virtual machines start.
mregulski
Posts: 3
Joined: 25. Oct 2020, 02:45

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by mregulski »

I've met same issue
olmerg
Posts: 1
Joined: 30. Oct 2020, 21:25

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by olmerg »

I have the same issue,
Failed to get device handle and/or partition ID for 0000000001b3d860 (hPartitionDevice=0000000000000ce0, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).


Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
multiOS
Volunteer
Posts: 800
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: WIN11,10, 7, Linux (various)
Location: United Kingdom

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by multiOS »

Start with this Guide: viewtopic.php?f=25&t=97412 and see if you can track down the problem

Please note that if you previously disabled Hyper-V to allow VirtualBox to work effectively then the Insider 'Upgrades' very probably reactivate it.
mregulski
Posts: 3
Joined: 25. Oct 2020, 02:45

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by mregulski »

I think it's not true anymore because I would like to use Hyper-V as a backend, and it was working on a previous build of Windows Insider. It stopped working exactly in this build.
multiOS
Volunteer
Posts: 800
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: WIN11,10, 7, Linux (various)
Location: United Kingdom

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by multiOS »

Dream on!

Current VirtualBox User Guide (6.1.16):
9.32 Using Hyper-V with Oracle VM VirtualBox
Oracle VM VirtualBox can be used on a Windows host where Hyper-V is running. This is an experimental feature.
No configuration is required. Oracle VM VirtualBox detects Hyper-V automatically and uses Hyper-V as the virtualization engine for the host system. The CPU icon in the VM window status bar indicates that Hyper-V is being used.
Note: When using this feature, some host systems might experience significant Oracle VM VirtualBox performance degradation.
mregulski
Posts: 3
Joined: 25. Oct 2020, 02:45

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by mregulski »

What does it change? This experimental feature was working and now it's not. We are just reporting that it stopped working. I don't care about performance, I care about the possibility of using VirtualBox in parallel with Hyper-V because I also use Docker.
multiOS
Volunteer
Posts: 800
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: WIN11,10, 7, Linux (various)
Location: United Kingdom

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by multiOS »

It doesn't change anything, that's the whole point. If someone wants to use VirtualBox and hits this problem then they simply have to completely disable Hyper-V to use VirtualBox effectively. If access to Hyper-V is really necessary, then they can't use VirtualBox effectively at the same time. That's the current reality; and the choice for the vast majority who report these issues here.

At present, the realistically available options for dealing with this "Warning Message" are to either to dispense with mixing these conflicting virtualisation solutions completely; or to learn how to toggle the use of Hyper-V/VirtualBox (or any other conflicting 3rd-party virtualisation software), which is relatively easy, while waiting/testing for improvements over time. Any significant change in capability will, no doubt, be important enough to be announced in the accompanying changelogs for future VirtualBox Updates. Endless reports which simply state "I also get this message" add very little to any conversation and do not lead anyone anywhere, because it's already a well known issue, and even when logs are added they don't increase the existing knowledge base.

From me, that's it and I have no intention of commenting further.
brandonp357
Posts: 5
Joined: 4. Nov 2020, 12:45
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Ubuntu

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by brandonp357 »

not working for me as well
Attachments
VBox.log
(31.81 KiB) Downloaded 121 times
tute87
Posts: 1
Joined: 7. Nov 2020, 05:39

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by tute87 »

thx for all!!! 1 week with this problem!
AceHack
Posts: 2
Joined: 23. May 2019, 06:37

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by AceHack »

Same problem any update?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VERR_NEM_VM_CREATE_FAILED on Win 10 Build 20241

Post by scottgus1 »

Locking this one, especially as we are gathering me-too glom-on's. Future would-be posters, please refer to MultiOS's posts above, especially the post with the quote from the manual about possible degraded Virtualbox performance under Hyper-V.

Long story short: Virtualbox (a type-2 hypervisor that requires a solid host OS accessing the hardware) is not fully capable yet running on top of Hyper-V (a type-1 hypervisor that accesses the hardware before the host OS does). The devs are working on it.

There is no time-frame available for when this situation might be cleared up. A lot depends on Microsoft's developments, and it is probably correct to say that Microsoft does not care a rat's patootie if Virtualbox gets broken at the next 6-month Windows update. :lol:
Locked