Why does this VirtualBox error appear? Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED)

Question

When I attempt to start an Ubuntu guest OS in VirtualBox it gives me this error:

Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED)

I was getting more common errors (AMD-V) relating to virtualization beforehand. I am aware of issues with Windows 10, AMD, and virtualization. I had enabled SVM Support in the BIOS and it solved those issues, but this one is now appearing which it didn't before.

When I search this error I get information relating to "WHvSetupPartition" and not "VidMessageSlotMap". I tried the fixes for that (including the powershell command: bcdedit /set hypervisorlaunchtype off) with this one too, but they didn't work.

"Your question has been identified as a possible duplicate of another question." As mentioned, it's a different error and I've tried fixes for that error on this too.

I am using Windows 10 Pro N, a Ryzen 5 1600, and a Gigabyte B450M DS3H. As I said I enabled SVM in the BIOS and I am sure to have disabled the Windows 10 based virtualization features as they were apparently causing issues too. I attempted with them both enabled and disabled.

I've highlighted the ones I've heard are the ones that may conflict with it and as you can see they're all disabled.

What is causing this and how do I disable it or prevent it from doing so? Or what may I need to enable to get this working?

Solution 1

I was getting the same error. Leaving Virtual Machine Platform on made VM run.

Solution 2

My problem was started when i have enable WSl2 in windows 10 machine. But i am able to run WSL2 and Virtual Box by following steps:-

1. Open Virtualbox
2. Click on File Menu
3. Select Check for update
4. This will download a file in your downloads
5. Click on downloaded file and follow the steps

My error is gone after installing below version. Version 6.1.16 r140961 (Qt5.6.2)

Happy troubleshooting.

Solution 3

I had exactly the same error :

Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED).

I resolved this with a second reboot of the system. Hyper-V functionality and Windows containers were already disabled:

Disable-WindowsOptionalFeature -Online -FeatureName containers

I use French Windows 10 Pro. I have none of the following items: "Vitual Machine Platform", "Windows Hypervisor", "Windows Sandbox", "Windows Subsystem for Linux".

Comments

[Jezza]

Yeah I tried this and it worked, thank you. Also was able to enable Windows Subsystem for Linux and it still worked.

[quilkin]

No, didn't work for me, it just disabled my interet connection!

[Jake Levi]

What is "Virtual Machine Platform", and how do I leave it on?

[Shankara Narayana]

@jake, its a windows feature, in the windows search bar search "turn windows features"

[Admin]

Thank you this should be top comment