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?

  • 3
    Does this answer your question? VirtualBox fails to start with VERR_NEM_VM_CREATE_FAILED – Ramhound Jan 6 at 23:57
  • This error only happens if the software installed on the system is using the hardware virtualization x86 extension (AMD-V/VT-x). So the fix is pretty much universal, making sure Windows itself is not using through one of its optional features, and making sure any third-party security software is not using it. Specific errors would be required to provide any additional help. Additional, screenshots uploaded using the image upload functionality, is always recommended instead of using external image hosts. – Ramhound Jan 7 at 0:12
  • 1
    @Ramhound - It doesn't help because it talks about a different error: "Call to WHvSetupPartition failed", whereas this one is "Call to VidMessageSlotMap failed", and I've mentioned this and how I still tried the same fixes to no avail in the OP. As the screenshot shows I have disabled all the Windows 10 virtualization, along with restarting multiple times. I don't get any other errors than what VB shows, however what other software may be (somehow) still using it as I haven't used virtualization on this machine before? Thanks. – Ryszmarine Jan 7 at 17:27
  • What security software do you have installed? Do you have Core Isolation enabled? Do you have Application, Credential, and Device Guard disabled? Even though you have disabled Hyper-V, have you actually ran the command, bcdedit /set hypervisorlaunchtype off? Your question does not explicitly specify if that is the case or not. The error you received is a virtualization extension issue, only cause by software using the extension, and preventing VirtualBox from using it. – Ramhound Jan 7 at 17:31
  • You should also verify you are NOT using an Insider Preview build of 20H1 or 20H2. – Ramhound Jan 7 at 17:38

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

  • Yeah I tried this and it worked, thank you. Also was able to enable Windows Subsystem for Linux and it still worked. – Ryszmarine Jan 18 at 21:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.