Failed to get device handle and/or partition ID for 000000000196a390

[hwalker]

Hi there,

I'm kinda new to VirtualBox. and I have just started getting this error. Another forum post led me to believe it was Hyper-V, so I turned it off and rebooted, but I still keep getting the error.

I'm running Windows 10 2004 (insider build). The error I get:

Code: Select all

Failed to open a session for the virtual machine Server 2019.

Failed to get device handle and/or partition ID for 000000000196a390 (hPartitionDevice=0000000000000b1c, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).

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

Is there any way to fix this?

[scottgus1]

VERR_NEM_VM_CREATE_FAILED: What do I do?

[hwalker]

VERR_NEM_VM_CREATE_FAILED: What do I do?

This worked! I just ran bcdedit /set hypervisorlaunchtype off, did a cold boot, and now it works!

[scottgus1]

Great! Glad you're up and running.

[blueBear]

:: setting hypervisorautolaunch off from bcdedit >>>
this will work...but the only problem with this fix is the wsl2 gonna stop working completely unless u turn it to 'auto' again

[scottgus1]

wsl2 gonna stop working completely

This is true, blueBear. However, there has been more development in the last year and a half, since the final date on this topic before you woke it up.

Continued effort by the devs has resulted in the 6.1.35 test build, which is letting some folks use Virtualbox while Hyper-V is enabled.

If you try 6.1.35 or other future test builds, save the test build installer until you update again later. You'll need it if your host's MSI installation database goes south (they do) and the installer will not be available for download after the next even-number version gets released.

[Tirus]

I faced the same issue. I guess this happened because I recently downloaded Docker which uses some common technical stuff as VM does or changes some settings that VM also uses. So enter these commands in order:

>> bcdedit /set hypervisorlaunchtype off

>> DISM /Online /Disable-Feature:Microsoft-Hyper-V (May not do anything in some cases)

>> shutdown -s -t 2

With the last command, your PC will be shut down.

When you start it again, START YOUR VM BEFORE YOU START DOCKER!!!

I believe there should be better solutions but this is one solved mine.