How to Fix 0x80004005 Virtual Box VM on Windows

If you have experienced E_FAIL (0x80004005) error code while you are using Windows 10 or any other OS on VirtualBox then this guide will fix that issue. The error is not related to guest OS as it depends totally on the host.

Most of the users who experienced 0x80004005 on Virtual Box have fixed the issue by just disabling the Hyper-V. Once the Hyper-V is disabled then you can continue to use the VirtualBox.

virtual box 0x80004005 vm
virtual box 0x80004005 vm

Bonus: users have also experienced issues with BlueStacks and Hyper-V, once both of them are enabled. And this is how you fix BlueStacks and Hyper-V errors.

Fix Error Code 0x80004005 virtual machine

0x80004005 error
0x80004005 error

If you are experiencing the error code 0x8000400VM in VirtualBox then these methods can help you. The error that you are experiencing on VirtualBox should look something like this:

Failed to open a session for the virtual machine <VM_Name>.
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This can occur on running VirtualBox or while running VM. if you are one who is experienced at the start then follow these methods given. For users who experienced it on running VM, another separate section is given at the bottom.

Before you apply any of the methods given, let’s apply a few handy tricks. These are simple tricks that might fix the issue.

To update your VirtualBox to the latest version, you will need to open VirtualBox. Then you will click on File in the menu bar. Select the Check for Updates option and another popup will appear.

Click on the link and download the latest version. Perform the installation and you will have the latest version available.

If the tricks above haven’t fixed the 0x80004005 error then apply the methods below.

Disable Hyper-V

For using the virtual machine, you will need to enable the virtualization feature. While you enable it, sometimes Hyper-V is enabled too.

On one hand, Hyper-V is a great feature and needs to be enabled to use VirtualBox or VMware on Windows. On other hand, on rare occasions, it can also cause issues with VMware or VirtualBox. And to fix it, you will need to restart Hyper-V.

Here is how to restart Hyper-V. Open CMD (command prompt) from the Start menu and use the command below;

bcdedit /set hypervisorlaunchtype auto

Check if the error is fixed on VirtualBox. If restarting hasn’t fixed 0x80004005 then you are recommended to disable Hyper-V. For disabling, you can use the command below on CMD.  

bcdedit /set hypervisorlaunchtype off

This will fix users who are experiencing 0x80004005 on starting a virtual machine on Windows. Those who are having issues while running VM will use the methods given.

Fix Run Time error 0x80004005 VM on VirtualBox

Users who are having run-time errors will get something like this;

Runtime error opening 'C:\Users\COMPUTER_NAME\.VirtualBox\Machines\VM_NAME\VM_NAME.xml' for reading: -102 (File not found.).
D:\tinderbox\win-3.2\src\VBox\Main\MachineImpl.cpp[665] (Machine::registeredInit).
Result Code: E_FAIL (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

To fix run time errors, there are two simple and easy ways.

  • Discard Saved State
  • Replace prev and tmp files

Discard Saved State

For this method, you will run VirtualBox and right-click on the Virtual Machine that you want to run.

Now you will select the Discard Saved State option.

Give your VirtualBox a good restart and run VM. If you are still experiencing the error then you are recommended to use the next method below.

Change or Delete prev and tmp

Another way to fix the issue is by checking the VM files. There you will select XML files and make sure all the required files are there.

Navigate down and open the VM folder. You will probably find your VM folder path something like this “C:\Users\COMPUTER_NAME\.VirtualBox\Machines\VM_NAME\“.

Open the folder and inside you will find the following XML files;

1. VM_NAME.xml-prev

2. VM_NAME.xml-tmp

VM_Name.xml file
VM_Name.xml file

Now make sure there is a “VM_NAME.xml” file. If you can’t find this file then you are going to make a copy of the “VM_NAME.xml-prev” files and change its name to “VM_NAME.xml”. After the XML there won’t be any further extension.

Close the VM folder and give your VirtualBox a restart. Check your Virtual Box for 0x80004005 error code.

Alternative method

VM_Name.vbox file on VB
VM_Name.vbox file on VB

While some systems can fix the error code by changing XML files, others will require a change in “.vbox”. Here, you will select the “.Vbox-tmp” and change it to “.Vbox”.

Some will find “.Vbox-tmp” whereas others will find “.Vbox-prv” files. You are going to replace it too as we did with the “.Vbox-tmp” file. Change the name to “.Vbox” file.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: