5

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?

kesarling He-Him
  • 199
  • 2
    Does this answer your question? VirtualBox fails to start with VERR_NEM_VM_CREATE_FAILED – Ramhound Dec 24 '19 at 18:02
  • No it doesn't. Please look at the VidMessageSlotMap failed error. Others have a different error – kesarling He-Him Dec 26 '19 at 07:50
  • Possible duplicate of https://superuser.com/questions/1190456/virtualbox-0x80004005 – Ramhound Dec 26 '19 at 12:09
  • Possible duplicate of https://superuser.com/questions/785072/e-fail-0x80004005-when-running-linux-through-windows-8-virtualbox – Ramhound Dec 26 '19 at 12:10
  • 1
    Happening to me too. Tried every troubleshooting process found. Windows 10 build 19041. VirtualBox Version 6.1.0 r135406 (Qt5.6.2) – Jesus Iniesta Jan 04 '20 at 11:57
  • 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}" – Jesus Iniesta Jan 06 '20 at 15:44
  • 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? – kesarling He-Him Jan 06 '20 at 15:59
  • 1
    @d4rk4ng31 Before choosing to use an Insider Build, capture an image the C: partition using DISM (see the Imaging and Commands section), as going back to a non-Insidier's build will often require a clean install of Windows. . – JW0914 Jan 10 '20 at 14:23
  • 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) – kesarling He-Him Jan 11 '20 at 10:22

2 Answers2

1

I suspected, after reading OP's own answer, that my activation of Windows Hello PIN had hosed my VirtualBox install; even when attempting to set up brand new VMs, they all failed to start with the same error. I instead decided to try a different tack though: I reinstalled VirtualBox (over the top of my old install).

My old version was 6.1.18, and I reinstalled 6.1.30 over it -- as soon as the install had completed (I had to reinstall the VirtualBox Extension Pack as well because the old one was out of date) I tried to fire up a VM, and boom, it runs like a champ!

Doktor J
  • 2,383
  • 4
  • 20
  • 28
0

Finally, I myself found an answer. The solution is very simple (Do Take a backup of ye data before implementing). Go to the BIOS and reset the TPM settings(!!!!WARNING This clears your account credentials including your Windows Hello PIN if you have it set up!!!!). Then reboot and lo! bob's your uncle :). To all of you Geeks out there, what setting must have got changed when I reset TPM?? I mean, I don't remember changing TPM settings.

One more thing, the solution works for insider as well as non-insider builds

kesarling He-Him
  • 199