12

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.

enter image description here

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?

Jezza
  • 123

6 Answers6

3

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

3

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.

1

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".

JPD
  • 11
0
  1. Try to update Windows to latest version and install latest version of VirtualBox (& if you used, you can update ExtensionsPack too)

  2. if above doesn't solve, try https://forums.virtualbox.org/viewtopic.php?f=6&t=95978

T.Todua
  • 4,053
0

I faced this issue after installing Docker Desktop and here is how I resolved this issue.

  • Open the "Turn Windows features on or off" settings (type optionalfeatures in the start menu or Win + R).
  • Uncheck "Windows Machine Platform" and "Windows Subsystem for Linux" .
  • Restart windows once or twice.

enter image description here

enter image description here

  • If you have Docker Desktop installed, then after restart you will see the following message.

enter image description here

I think the above message is telling that you have to check Windows subsystem for Linux and Virtual machine Platform for running Docker Desktop.

If you want to work on Docker Desktop again, you can check these options a see that are you able to use Docker Desktop or not. I haven't checked it myself so I can't tell you the result.

UPDATE - 2023

If above solution couldn't work, please try to update the VirtualBox. I installed the latest version of VirtualBox which is version-7 at the time of writing this update and it fixed my issue.

Hope this will help.

0

Win + R : optionalfeatures hit enter.

I disabled 5 items:

  • Windows Linux Subsystem
  • Hyper-V Windows
  • HyperVisor Platform
  • Container
  • Virtual Machine Platform

Then It worked on 6.1.2

Note: No problem on 7.02 but 6.1.2 is chosen in order to try to run copy and paste function on terminal.

Hakan
  • 181