I was running VB on the previous build of Windows but since I updated the build to 20257, I get this error when trying to start an Ubuntu 20.10 VM:
Failed to get device handle and/or partition ID for 000000000224c610 (hPartitionDevice=00000000000009a8, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I have Windows Hyper-V turned off and none of my Ubuntu settings have changed.
Windows Build 20257 Broke VB
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows Build 20257 Broke VB
If you had Hyper-v turned off then you wouldn't be getting VERR_NEM_VM_CREATE_FAILED.TomL12953 wrote: Failed to get device handle and/or partition ID for 000000000224c610 (hPartitionDevice=00000000000009a8, Last=0xc0000002/1) (VERR_NEM_VM_CREATE_FAILED).
...
I have Windows Hyper-V turned off and none of my Ubuntu settings have changed.
See related FAQ, carefully check all the items in post #3: FAQ: I have a 64bit host, but can't install 64bit guests.
-
- Volunteer
- Posts: 870
- 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: Windows Build 20257 Broke VB
TomL12953,
If that Insider Build Update was one of those that completely replaces the OS in the same way the the now annual Feature Updates do, then IME it will have reactivated any comatose installation of Hyper-V, i.e. Microsoft might well say it sought to repair a broken feature that wasn't working.
If that Insider Build Update was one of those that completely replaces the OS in the same way the the now annual Feature Updates do, then IME it will have reactivated any comatose installation of Hyper-V, i.e. Microsoft might well say it sought to repair a broken feature that wasn't working.