VirtualBox fails to start


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


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?

asked on Super User Dec 24, 2019 by kesarling • edited Jan 1, 2020 by kesarling

1 Answer


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

answered on Super User Jan 12, 2020 by kesarling • edited Jan 13, 2020 by kesarling

User contributions licensed under CC BY-SA 3.0