6 Ways to Fix VirtualBox Result Code: E_FAIL (0x80004005) Error in Windows

Before calling up Oracle Customer Support

VirtualBoxdisplays the “E_FAIL (0x80004005)” error code when it can’t open a virtual machine session. The error could be due to problems with the VirtualBox app, configuration files, or hardware-related issues.

This tutorial highlights probable causes and troubleshooting solutions for the E_FAIL (0x80004005) VirtualBox error on Windows devices.

1. Update VirtualBox

Some Windows usersresolved this error by installing the latest build of VirtualBox 6. Head to thedeveloper’s websiteand download the Windows hosts VirtualBox setup file.

You can also update VirtualBox directly within the app. Open the VirtualBox Manager app, selectFileon the menu bar, and selectCheck for Updates.

Select the provided link to download the executable (.exe) file of the latest version of VirtualBox.

2. Restart the Windows Hypervisor (Hyper-V)

Hyper-Vis a Windows feature that lets your computer run multiple operating systems as virtual machines. You may be unable to access virtual machines in VirtualBox if Hyper-V is experiencing a glitch.

Restarting Hyper-V in Windows (see steps below) can fix issues preventing VirtualBox from running virtual machine sessions.

Running this command turns off Hyper-V on your computer. If you have multiple operating systems installed on your computer, run the command below to disable Hyper-V for the active/current OS.

Pastebcdedit /set {current} hypervisorlaunchtype offin the Command Prompt console and pressEnter.

Restart your computer when you get a “This operation completed successfully” message.

bcdedit /set hypervisorlaunchtype auto

Restart your computer again when Command Prompt displays a “The operation completed successfully” message. Launch VirtualBox and try opening the virtual machine.

3. Discard Saved State

VirtualBox may also display the E_FAIL (0x80004005) error if there’s a problem with thevirtual session’s saved state. So, if you cannot restore a session, discard the saved state and reopen the virtual machine.

Discarding a machine’s saved state has the same effect as shutting it down. Open VirtualBox, right-click the virtual machine, selectDiscard Saved State(or pressCtrl+J), and restart the session.

Try the troubleshooting solutions below if “Discard Saved State” is greyed out—i.e., the virtual machine has no saved state.

4. Rename VirtualBox Configuration Files

Force-quitting VirtualBoxwithout first closing a virtual machine can trigger the E_FAIL (0x80004005) error. We’ll explain how and why this happens.

Let’s assume you have a “Linux PC” virtual machine in VirtualBox. When you launch the virtual machine, VirtualBox renames the machine’s file from “Linux PC.vbox” to “Linux PC.vbox-prev.” VirtualBox then creates and uses a new/temporary copy of the virtual machine file—”Linux PC.vbox-tmp”—for the active session.

When you end the virtual machine session, VirtualBox renames the temporary file (i.e., Linux PC.vbox-tmp) to Linux PC.vbox. The “Linux PC.vbox-prev” file serves as a backup—VirtualBox overwrites the file every time you start a new session.

Terminating VirtualBox without closing your virtual machine can disrupt the file conversion process. That’ll prompt the “Result Code: E_FAIL (0x80004005)” error the next time you try to launch the virtual machine.

Open your PC’s VirtualBox folder and check if there’s a.vboxfile for your virtual machine. If you only find temporary (.vbox-tmp) and backup (.vbox-prev) files in the folder, you probably force-closed VirtualBox while running a virtual machine.

Renaming the backup file can fix the problem and get your virtual machine running again. Close the VirtualBox Manager application and follow the steps below to get it done.

Note:Older VirtualBox versions (v3.2 and older) store virtual machines configuration files in.xmlformat—not.vbox. If you find files with this extension in your virtual machine folder, rename them following the steps above. That means you’ll change files in.xml-prevor.xml-tmpformat to.xml.

5. Enable Virtualization in BIOS Settings

You must have hardware or CPU virtualization enabled on your computer to run virtual machines. If VirtualBox includes the “AMD-v” or “VT-x” keywords in the error details, your PC’s hardware virtualization is likely disabled.

Follow the step below to verify your computer’s hardware virtualization status.

In Windows 10, head toSettings>Updates & Security>Recoveryand selectRestart nowin the “Advanced startup” section.

Head to theConfigurationsection on HP computers and keepVirtualization Technologyenabled. ThisMicrosoft Support documenthas instructions for enabling virtualization for all PC manufacturers and devices.

VirtualBox should now run the virtual machine after enabling virtualization in your PC’s BIOS/UEFI settings.

6. Reinstall VirtualBox

Uninstall VirtualBox if none of the troubleshooting tricks resolve the problem. Afterward, reboot your computer and install the latest VirtualBox version. Reinstalling VirtualBox fixed the problem for some Windows users in thisMicrosoft Community thread.

Typevirtualboxin the Start menu search, selectUninstallbelow the Oracle VM VirtualBox app and follow the uninstallation prompt.

Contact Oracle Supportor your PC manufacturer if the “Result Code: E_FAIL (0x80004005)” error persists despite reinstalling VirtualBox.

Sodiq has written thousands of tutorials, guides, and explainers over the past 4 years to help people solve problems with Android, iOS, Mac, and Windows devices. He also enjoys reviewing consumer tech products (smartphones, smart home devices, accessories, etc.) and binge-watching comedy series in his spare time.Read Sodiq’s Full Bio

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

Comment*

Name*

Email*

Website

Welcome to Help Desk Geek- a blog full of tech tips from trusted tech experts. We have thousands of articles and guides to help you troubleshoot any issue. Our articles have been read over 150 million times since we launched in 2008.

HomeAbout UsEditorial StandardsContact UsTerms of Use

6 Ways to Fix VirtualBox Result Code: E_FAIL (0x80004005) Error in Windows#

1. Update VirtualBox#

2. Restart the Windows Hypervisor (Hyper-V)#

3. Discard Saved State#

4. Rename VirtualBox Configuration Files#

5. Enable Virtualization in BIOS Settings#

6. Reinstall VirtualBox#

Leave a Reply#