6 Methods to Fix VirtualBox Result code: E_FAIL (0x80004005) Windows Error

6 Methods to Fix VirtualBox Result code: E_FAIL (0x80004005) Windows Error

VirtualBox When it cannot open a virtual machine, the error code “E_FAIL (0x80004005)” is displayed. This error can be caused by problems in the VirtualBox app or configuration files.

This article explains the possible causes of and solutions to the E_FAIL (0x80004005) VirtualBox error in Windows.

6 ways to fix virtualbox result code: e_fail (0x80004005) error in windows

1. VirtualBox updated

Windows Users This error was fixed by downloading the most recent version of VirtualBox 6. Go to developer’s website Download the Windows hosts VirtualBox installation file.

Update virtualbox

VirtualBox Manager app can be used to update VirtualBox. Select the VirtualBox Manager app and click “Update VirtualBox” File Select the option you want from the menu Check for Updates.

Update virtualbox

Click the link below to download VirtualBox’s latest executable file (.exe).

Update virtualbox

2. Start the Windows Hypervisor, (HyperV),

Hyper-V Windows features that allow you to use multiple operating systems in virtual machines. Hyper-V might be experiencing an error that makes it impossible to connect to virtual machines within VirtualBox.

You can restart Hyper-V under Windows (see the steps below), to fix problems that prevent VirtualBox sessions from being run.

  1. Click on the Start Menu and type cmd Use the search box to select Run as administrator Please see the below Command Prompt app.
Restart the windows hypervisor (hyper-v)
  1. Paste bcdedit /set hypervisorlaunchtype off In the Command Prompt console, press Enter.
Restart the windows hypervisor (hyper-v)

The following command disables Hyper-V in your computer. Run the following command to disengage Hyper-V from multiple operating systems on your computer.

Paste bcdedit /set {current} hypervisorlaunchtype off In the Command Prompt console, press Enter.

Restart the windows hypervisor (hyper-v)

If you receive a message indicating that “This operation was completed successfully”, restart your computer.

  1. To reactivate Hyper-V, open Command Prompt and grant administrative rights.

bcdedit /set hypervisorlaunchtype auto

Restart the windows hypervisor (hyper-v)

When Command Prompt shows a message indicating that the operation was successful, restart your computer. Start VirtualBox, and open the virtual machine.

3. Savings State should be discarded

VirtualBox might also show the E_FAIL (0x80004005) Error if it detects an error with the system Virtual session saved as a state . . If you are unable to restore a session of the virtual machine, then discard any saved states and restart it.

The same effects as turning off a computer’s save state are achieved by deleting it. Open VirtualBox. Right-click on the virtual machine and select Discard Saved State Or press Ctrl + JClick the button and then restart your session.

Discard saved state

You can use the below troubleshooting tips to determine if the “Discard Saving State” option is grayed out. This means the virtual machine doesn’t have any saved states.

4. VirtualBox Configuration Files – Rename

Force-quitting VirtualBox A virtual machine that is not closed can cause an E_FAIL (0x80004005) error. Let us explain why and how this occurs.

Assume you are using VirtualBox to create a virtual “Linux PC.” VirtualBox changes the file name of your virtual machine from “Linux PC.vbox” to “Linux PC.vbox–prev” and creates a temporary copy for the current session.

VirtualBox changes the name of the temporary file to Linux.vbox.vbox after you quit the virtual machine session. VirtualBox creates a “Linux PC.vbox.prev” file as a backup. VirtualBox then overwrites it every time you begin a new session.

Rename virtualbox configuration files

The file conversion process can be disrupted if VirtualBox is closed after you close it. This will prompt you to get the “Result code: E_FAIL (0x80004005) error when you attempt to launch VirtualBox again.

In the VirtualBox folder of your PC, open it and see if you can find a .vbox You can file to your virtual machine. You can only use temporary files (.vbox-tmpBackup (.vbox-prevIf you find () files in the directory, it is likely that VirtualBox was forced to close while using a virtual machine.

The backup file can be renamed to fix the problem. This will allow your virtual machine to start up again. To fix the problem, close VirtualBox Manager and then follow these steps.

  1. In File Explorer, open the VirtualBox’s file manger. Open your local disk (C:Double-click on the folder ‘( Users Folder, then select the computer or account you wish to use.
Rename virtualbox configuration files
  1. Open the VirtualBox VMs folder, select Machines, Double-click on the folder of your virtual machine.
Rename virtualbox configuration files
  1. Save both files (.vbox.tmp &.vbox.prev), and copy them to another location on your computer. The temporary file’s extension can be changed from .vbox-prev to .vbox.
Rename virtualbox configuration files
  1. Select OK Follow the prompts to open VirtualBox and close the message.
Rename virtualbox configuration files
  1. Change the VirtualBox settings and close VirtualBox .vbox Send it back .vbox-prev If the error continues, you can rename it. If the error persists, you can rename it .vbox-temp Send an email .vbox You can now check whether VirtualBox runs this virtual machine.
Rename virtualbox configuration files

Note: Virtual machine configuration files are stored in older VirtualBox versions (v3.2 or earlier) .xml format—not .vbox. .xml-prev or .xml-tmp Use this format .xml.

5. Allow Virtualization to be enabled in BIOS Settings

Virtual machines can only be run if your CPU or hardware virtualization is enabled. VirtualBox will indicate that hardware virtualization has been disabled if VirtualBox contains “AMD-v”, or “VTX” keywords within the error details.

You can verify your computer’s status with hardware virtualization by following the steps below.

  1. Go to Settings > System > Recovery > Advanced startup Choose and Restart now.
Enable virtualization in bios settings

Windows 10 has a new interface Settings > Updates & Security > Recovery Choose and Restart now You can find it in the “Advanced startups” section.

Enable virtualization in bios settings
  1. Head to Troubleshoot.> Advanced options.> UEFI Firmware Settings Choose and Restart To boot into the BIOS or UEFI settings of your computer.
Enable virtualization in bios settings
  1. Your PC model and manufacturer will determine how virtualization is enabled in BIOS settings. Head to this page for Lenovo products Configuration Section and set Intel Virtual Technology to Enabled.
Enable virtualization in bios settings

Visit the Configuration Section on HP computers and keeping Virtualization Technology enabled. This Microsoft Support document This document contains instructions on how to enable virtualization for all types of PCs and devices.

  1. Select the appropriate option from the section “Exit” Exit Saving Changes, Yes You can boot to Windows.
Enable virtualization in bios settings

After enabling virtualization on your computer’s BIOS/UEFI, VirtualBox will now be able to run the virtual machine.

6. Reinstall VirtualBox

If none of these troubleshooting techniques work, uninstall VirtualBox. Reboot your computer, then install VirtualBox. Some Windows users experienced the same problem after reinstalling VirtualBox Microsoft Community thread .

Type virtualbox Select the appropriate option from the Start menu Uninstall Below the Oracle VM VirtualBox application, follow the Uninstallation prompt.

Reinstall virtualbox

Get Oracle Support Contact your manufacturer of PC if you continue to get the “Result code: E_FAIL (0x80004005) error despite installing VirtualBox..

Leave a Reply

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