Windows 11 host VERR_NEM_VM_CREATE_FAILED
Windows 11 host VERR_NEM_VM_CREATE_FAILED
Failed to open a session for the virtual machine COMP2401-F21.
Failed to get device handle and/or partition ID for 000000000120c7b0 (hPartitionDevice=0000000000000bc9, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Failed to get device handle and/or partition ID for 000000000120c7b0 (hPartitionDevice=0000000000000bc9, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Last edited by scottgus1 on 18. Oct 2021, 17:12, edited 1 time in total.
Reason: changed title to reflect problem
Reason: changed title to reflect problem
Re: Virtual box
I am trying to use the virtual box and I am getting this error. I am using windows11, I have tried everything possible online. Nothing works
Re: Virtual box
Yh I did that already but it didn't work I think it's because I am using windows11. At least that was what Microsoft told me. They said there currently isnt a virtualbox that's compatible with windows11
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual box
Jacob seems to disagree: viewtopic.php?f=38&p=506895#p506895stephen00 wrote:Microsoft told me ... there currently isnt a virtualbox that's compatible with windows11
I haven't run 11, so I cannot say for certain. But,
Honestly, most folks who don't get the tutorial to work either are under IT overlords who won't let the tutorial work, or they didn't do it right:stephen00 wrote:Yh I did that already but it didn't work
VERR_NEM_VM_CREATE_FAILED: What do I do? wrote:If you still get the error, post back exactly what you did and we'll try to help some more.
Re: Virtual box
Failed to get device handle and/or partition ID for 0000000001b80040 (hPartitionDevice=0000000000000c25, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I just followed the steps exactly again and I still have the same error
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I just followed the steps exactly again and I still have the same error
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual box
stephen00 wrote:I just followed the steps exactly again
You should report what you typed, what you clicked, what you did. That's what "post back exactly what you did" means. So far, failure to follow this simple instruction does not leave good feelings about your having truly followed the tutorial.scottgus1 wrote:post back exactly what you did
Also consider tying the 6.1.27 test builds. Save the test build installer until you update again later.
Re: Virtual box
1. I rebooted my host
2. Ran my command prompt as administrator
3. Entered the command
bcdedit /set hypervisorlaunchtype off
4. Enter this command:
shutdown -s -t 2
5. Did a cold reboot
2. Ran my command prompt as administrator
3. Entered the command
bcdedit /set hypervisorlaunchtype off
4. Enter this command:
shutdown -s -t 2
5. Did a cold reboot
Re: Virtual box
I just installed build 6.1.27 and I am still getting the same error
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual box
OK, thanks for the list.
Just to clarify:
Just to clarify:
stephen00 wrote:5. Did a cold reboot
Is that what "cold reboot" means?the tutorial wrote:6. When the computer turns off, unplug it for 20 seconds.
Re: Virtual box
I am not charging my laptop. When doing this so I just shutdown then wait for a while before I turn it back on. What do you suggest I do?
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 11 host VERR_NEM_VM_CREATE_FAILED
"Unplug it" means to remove power. So if I unplug a computer that has its own built-in power source, it remains powered. Therefore, what do you think would be the next step to truly unplug your laptop?
Note that Windows 11, or some corporate IT restriction from your workplace, or some other pebcak error not known by us, may be limiting you on your laptop to disable Hyper-V. So even removing the battery (a hint there, just in case) may not succeed in disabling Hyper-V. But it would at least demonstrate complete following of the tutorial.
BTW, the list of steps taken in your post here: viewtopic.php?f=6&t=104085#p507219. There are items to investigate in step 2 of the tutorial which you did not indicate you completed. These items may prevent the steps you posted from working.
Note that Windows 11, or some corporate IT restriction from your workplace, or some other pebcak error not known by us, may be limiting you on your laptop to disable Hyper-V. So even removing the battery (a hint there, just in case) may not succeed in disabling Hyper-V. But it would at least demonstrate complete following of the tutorial.
BTW, the list of steps taken in your post here: viewtopic.php?f=6&t=104085#p507219. There are items to investigate in step 2 of the tutorial which you did not indicate you completed. These items may prevent the steps you posted from working.
Re: Windows 11 host VERR_NEM_VM_CREATE_FAILED
I spoke with miscrosoft and I disabled my hyper-V manually (from the windows feature) and I also used the command prompt again to disable. My laptop is using a built in battery so the only proper way to do this will be to let it go off completely. Also I did all that I have virtualization enaled already.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 11 host VERR_NEM_VM_CREATE_FAILED
So does that mean you got things running?
BTW the newest 6.1.28 has a Hyper-V-cooperation bug that kills Windows 10 / Virtualbox coexistence with Hyper-V. Windows 11 as a host is not technically supported yet. The 6.1.97 test builds may be more compatible.
BTW the newest 6.1.28 has a Hyper-V-cooperation bug that kills Windows 10 / Virtualbox coexistence with Hyper-V. Windows 11 as a host is not technically supported yet. The 6.1.97 test builds may be more compatible.