How to fix E FAIL 0x80004005 when starting a VirtualBox VM

The ill-fated error E FAIL 0x80004005 can be seen when starting a virtual machine through VirtualBox. Starting from XP and ending with the latest versions of the “dozens” – all versions of Windows operating on the 6.1 kernel and newer are affected by a similar problem. As a rule, the error is caused by the configuration files of the virtual machine, a specific version of VirtualBox, HyperV enabled, and more.

Solution for error E FAIL 0x80004005

1. Deactivate HyperV

For the virtual machine (hereinafter referred to as VM) to work normally in VirtualBox on the PC, the HyperV function must be deactivated. Disabling the latter can be achieved by various methods, but we suggest doing it through PowerShell as follows:

  • press WIN+S to call the system search bar;
  • type in the query “Windows PowerShell”, click on the result found with
  • RMB and select “Run as administrator”;
  • run the following command in the console:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

  • close PowerShell and restart your PC.

2. Enable virtualization

Of course, you will not be able to start the VM if virtualization is not enabled on your computer. Similar functionality is activated in the BIOS / UEFI settings of the motherboard. Restart your PC, press the desired button, for example, F2, F9 or DEL, and go in search of the virtualization item in the advanced settings (it is often located there).

What to do if there is no virtualization in the BIOS or it is not available for? There are several reasons for this:

  • your CPU does not support the technology;
  • activated HyperV (↑);
  • outdated BIOS.

Regarding the latter, in rare cases, motherboard manufacturers add / open virtualization in new firmware versions.

3. Reset saved state

In some cases, E FAIL 0x80004005 occurs due to certain problems with its last saved state. To get rid of the latter, you need to do the following:

  • open Oracle VM VirtualBox Manager;
  • right-click on the problematic virtual machine;
  • select “Reset saved state” in the context menu;
  • restart Virtualbox.

4. Restore the VM Location Path

Pay attention to what other information VirtualBox gives you when you try to start a virtual machine (hereinafter simply VM) and it throws an error. See the “STOP” icon next to the machine’s name and its location on the PC in bold? Then, probably, your VM is no longer available at the specified path. Remember if you changed its location?

In simple words: return the VM to its original location. If you changed any characters in folder names, return everything as it was. Alternatively, you can re-add the VM with its new VitualBox location.

5. Installing another version of VirtualBox

In certain situations, a complete reinstallation of VirtualBox is required, and to a different version of it. We recommend trying the most current version of the program, and if the situation repeats, old builds. The main thing is not to get rid of user data when you remove the problematic version of VirtualBox. Just click “No” when prompted to do so. Thus, you will switch to another version of the program and save your important data.

Leave a Reply