How to deal with error code 0x80004005? Here are the best decisions for your VM!
Here you will find out:
- 3 ways to fix 0x80004005 error
- when DiskInternals can help you
Are you ready? Let's read!
What is VirtualBox E_FAIL (0x80004005) Error
VirtualBox is a type-2 hypervisor for x86 virtualization that is free and open-source. Microsoft Windows, macOS, Linux, Solaris, and OpenSolaris are all supported. It allows you to create and manage guest virtual machines running Windows, Linux, BSD, OS/2, Solaris, Haiku, and OSx86, as well as virtualize macOS guests on Apple hardware.
VirtualBox is widely used to operate virtual machines. However, some users claim to have received the VirtualBox E FAIL (0x80004005) error while attempting to launch a VM.
The error message, component, and interface may vary, but the message "Failed to open a session for the virtual machine xx." and "Result Code: E FAIL (0x80004005)" will remain the same.
0x80004005 Fix 1: Discard the VM's Saved State
If you receive a message that the VM session was closed (0x80004005), you can retrieve the saved state of the virtual machine and then load your VM as normal.
Right-click your virtual machine and select the "Discard Saved State" option.
After that, try to start the virtual machine; no errors or interference should appear. If this is not the case, and all you can see is the message “the VM session was closed before any attempt to power it on” on the screen, then try the following fix of 0x80004005.
0x80004005 Fix 2: Uninstall and Reinstall VirtualBox
You can also uninstall VirtualBox and then reinstall it to deal with 0x80004005. This method is especially helpful if the problem appeared after a Windows update.
In the Control Panel, find and remove VirtualBox, the virtual machines will remain intact.
Next, restart your computer and load the latest version of VirtualBox. Once the download is complete, right-click the downloaded file and select "Run as administrator". Detailed instructions will appear on the screen to install VirtualBox, follow them and after installation restart your computer to fix 0x80004005.
Now reopen VirtualBox Manager and start the virtual machine.
Next, proceed to install the Guest Additions and Extension Pack if you wish. 0x80004005 must be gone!
0x80004005 Fix 3: Install VBoxDrv.inf Manually
The VBoxDrv.inf file is a VirtualBox driver. However, it's conceivable that the installation of this critical driver isn't finished during the initial installation owing to permission concerns. The VM then fails to start, resulting in the error E FAIL (0x80004005). In this scenario, manually installing VBoxDrv.inf would solve the problem. Here's how to do it:
Locate the VBoxDrv.inf file in the VirtualBox installation folder. The VBoxDrv.inf file path should be C:Program FilesOracleVirtualBoxdriversvboxdrv if you didn't change the installation location. Install this file by right-clicking it.
Protect your data in case of 0x80004005 error
When working with cloud platforms, you need to take care of the safety of virtual machine information. Use DiskInternals VMFS Recovery™ for this purpose. It is by far the most famous professional VMDK file recovery tool (both .vmdk files and -flat.vmdk files).
Here are the key features that differentiate VMFS Recovery™ from other software:
- Supports virtual machines including VMware, VirtualBox, Virtual PC and ProDiscover disk images, and also supports vSphere 6 and ESX / ESXi Server.
- Works with Windows 7 and above (however, it is still recommended to use Windows 10).
- The size of the software is 65 MB, which is not a lot, but you must have enough free space on your hard drive to recover data.
- The Recovery Wizard will help you to automatically recover data in a short period of time without any additional professional skills.
- You can mount virtual disks as local disks available in Windows Explorer for easy viewing of data.
- Support for file names and multi-level Unicode folders.
Use these detailed step-by-step instructions to recover a corrupted VMDK file with DiskInternals VMFS Recovery™.
Install VMFS Recovery™. Start recovery by activating the Recovery Wizard, or do everything manually.
First, if necessary, establish an SSH connection, and then you will be prompted to open your local drive (this could be SSH).
Then the scan of the selected disk will start, which may take some time; after completing this step, locate the required .vmdk files that you want to mount.
Then open the mounted .vmdk file by double-clicking the left mouse button and browse the available files to check their integrity.
At any time on the DiskInternals website, buy a license and complete the export of data to an alternative data source.