3
1
I know that multiple questions have been asked related to this topic; but my error is entirely different This is the exact error I get:
Failed to open a session for the virtual machine Arch.
Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
It should be noted that I have a windows 10 home edition. It doesn't come with a Hyper-V feature. Even to use Hyper-V, I will have to buy a professional edition
Edit:
I installed vmware. It isn't working, but at least giving a nice error message saying device guard and credential guard should be turned off. As I said, I've Windows 10 Home edition and it doesn't have either of the two. Will anyone explain the reason?
d4rk4ng31
Posted 2019-12-24T17:09:41.233
Reputation: 169
2
Does this answer your question? VirtualBox fails to start with VERR_NEM_VM_CREATE_FAILED
– Ramhound – 2019-12-24T18:02:46.073No it doesn't. Please look at the
VidMessageSlotMap failederror. Others have a different error – d4rk4ng31 – 2019-12-26T07:50:34.550Possible duplicate of https://superuser.com/questions/1190456/virtualbox-0x80004005
– Ramhound – 2019-12-26T12:09:07.427Possible duplicate of https://superuser.com/questions/785072/e-fail-0x80004005-when-running-linux-through-windows-8-virtualbox
– Ramhound – 2019-12-26T12:10:03.6471Happening to me too. Tried every troubleshooting process found. Windows 10 build 19041. VirtualBox Version 6.1.0 r135406 (Qt5.6.2) – JesusIniesta – 2020-01-04T11:57:02.937
1@d4rk4ng31 "Failed to open a session for the virtual machine Ubuntu 18.04. Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}" – JesusIniesta – 2020-01-06T15:44:24.423
1@JesusIniesta, my issue got resolved when I switched from a Windows insider build to a normal build. Just for the sake of verifying, I again (stupidly) upgraded to an insider build, and there was again an issue. Are you running an insider build? – d4rk4ng31 – 2020-01-06T15:59:06.510
1
@d4rk4ng31 Before choosing to use an Insider Build, capture an image the
– JW0914 – 2020-01-10T14:23:47.583C:partition usingDISM(see the Imaging and Commands section), as going back to a non-Insidier's build will often require a clean install of Windows. .Any info on How to disable Device/Credential Guard would really be helpful. The fact that I know the issue but can't resolve it is really annoying me. I searched all over on Google, but all they show is for Pro versions. As far as I know, Windows Home doesn't come with these features (at least mine didn't) – d4rk4ng31 – 2020-01-11T10:22:38.573