When starting a virtual machine in Oracle VirtualBox, you may encounter error VERR_NEM_VM_CREATE_FAILED and VirtualBox fails to start. In this post, we will discuss this issue in detail and see what you can do to resolve it.
Call to VidMessageSlotMap failed: Last=0x000000d/878 (VERR_NEM_VM_CREATE_FAILED)
Result Code: E_FAIL (0x80004005)
Call to NEMR0TnitVMPart2 failed VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)
Fix VERR_NEM_VM_CREATE_FAILED VirtualBox fails to start
If you see VERR_NEM_VM_CREATE_FAILED error and VirtualBox fails to start, follow the solutions mentioned below to resolve the issue.
- Reboot the host computer and retry
- Check for Virtualbox Updates
- Disable Hyper-V feature and stop it from running at startup
- Disable Container, Virtual Machine Platform, and Windows Subsystem for Linux
Let us discuss them in detail.
1] Reboot the host computer and retry
First, we recommend you try rebooting the host computer to resolve the issue. Rebooting will get rid of the glitches that could have caused it.
2] Check for VirtualBox Updates
Sometimes, the VERR_NEM_VM_CREATE_FAILED error appears once the user enables WSL2. However, this is a bug in Oracle VirtualBox that should have been resolved by the time you are reading this post. So, we recommend you check if there is any update available for the VirtualBox application and install it. Follow the steps mentioned below to do the same.
- Open Oracle VirtualBox.
- Click on File > Check for updates.
- If you see the “New version found” option, click on it, and then click on the given link.
- It will ask you to open it in a browser, and then the update will be downloaded momentarily.
- Once downloaded, go to the Download folder, and run the installer. But before that, close the VirtualBox application if it’s running.
- Finally, follow the on-screen instructions to complete the installation process.
After updating VirtualBox, check if the issue is resolved.
3] Disable Hyper-V features and stop it from running at startup
This issue mostly appears when Hyper-V is enabled and/or starts at startup. Hyper-V is Windows’ own hypervisor platform, and if it is enabled, it conflicts with Oracle’s hypervisor service. To resolve it, we need to first disable Hyper-V. Follow the steps mentioned below to do so.
- Open the Control Panel from the Start Menu.
- Then, go to Programs > Turn Windows features on or off.
- Look for Hyper-V, uncheck the box associated with it, and click on Ok.
After disabling Hyper-V, we need to ensure that it doesn’t start at startup. To do this, open the Command Prompt as an admin and run the following command.
bcdedit /set hypervisorlaunchtype off
Finally, reboot the host computer and check if the issue is resolved.
4] Disable Container, Virtual Machine Platform, and Windows Subsystem for Linux
The last and probably the least recommended solution is to disable the Container, Virtual Machine Platform, and Windows subsystem for the Linux option. You can do this just like you disabled Hyper-V from Control Panel > Programs > Turn Windows features on or off.
However, if you are using Docker, you will encounter an error. So, use this solution if none of the aforementioned solutions works.
What does VERR_NEM_NOT_AVAILABLE mean?
The VERR_NEM_NOT_AVAILABLE error message implies that virtualization is disabled at the BIOS level. In order to resolve it, you need to boot into BIOS and then enable the feature.
Read: VirtualBox failed to register and open Hard Disk image file
How to fix AMD V is disabled in the BIOS error on Oracle VM VirtualBox?
If Oracle VirtualBox says that “AMD-V is disabled”, you are supposed to enable Hardware Virtualization on your host computer. We recommend you check our guide to know what to do if you encounter AMD-V is disabled in the BIOS.
Also Read: VirtualBox Failed to open session for the virtual machine, E_FAIL (0x80004005) Error.
