Opened 4 years ago
Closed 4 years ago
#19832 closed defect (invalid)
Virtual Box + Hyper-V - VERR_NEM_VM_CREATE_FAILED
| Reported by: | mfr | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.10 |
| Keywords: | Hyper-V | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
We are running Win10 1909 Build 18363.959 with Hyper-V (CredentialGuard) enabled. We like to run VirtualBox (version 6.1.12) with VMs on the system. When we fresh install virtualbox, everything is working fine. The VM can be started. After a reboot of the system the VMs are not able to start anymore, with the following error: ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805
After we completely uninstall virtualbox and do a new fresh installation of virtualbox, we are again able to start the vms. But again after a reboot the same error occurs again.
CPU - Intel Core i5-8365U
I looked up google, but any solution states to disable Hyper-V. But as we like to use Credential Guard this is no option for us. And why is it working after a reinstallation.
Attachments (2)
Change History (3)
by , 4 years ago
| Attachment: | failed_Tsdte-2020-08-25-11-25-14.log added |
|---|
comment:1 by , 4 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Your failure log is from VBox 6.0 (which is also EOL), the successful one from 6.1. Does it really fail with the latest 6.1 release? We'd need a VBox.log from that version. Just be aware of #19695, it is probably best if you use the latest 6.1 testbuild to have the latest Hyper-V fixes. Closing as invalid, for now. Please reopen if this really is an issue with 6.1 still.
VM Fails to start