That E_FAIL 0x80004005 error when you try to start a VirtualBox VM is annoying. I've seen it hundreds of times in my help desk. The fix is usually simple.
Main Fix: Reinstall VirtualBox and Disable Hyper-V
This error pops up most often on Windows 10 or Windows 11 machines. The cause? VirtualBox doesn't get along with Microsoft's Hyper-V hypervisor. They both want to run virtual machines, and they fight.
- Uninstall VirtualBox completely. Go to Control Panel > Programs and Features. Find Oracle VM VirtualBox. Right-click and select Uninstall. Wait for it to finish. Don't click anything else during uninstall.
- Restart your computer. After restart, don't open VirtualBox yet.
- Disable Hyper-V. Open Command Prompt as Administrator. To do this, right-click the Start button and select Command Prompt (Admin) or Terminal (Admin).
- Type this and press Enter:
dism /online /disable-feature /featurename:Microsoft-Hyper-V-All
You should see progress bars and a message saying "The operation completed successfully." - Restart again. This is critical. The Hyper-V changes need a reboot to take effect.
- Download the latest VirtualBox from the official Oracle website. At the time of writing, the latest stable version is 7.0.x. Don't use an old version.
- Install VirtualBox. Run the installer. Use all default options. When it asks if you want to install network drivers, say Yes.
- Restart one more time. I know, it's a lot of restarts. But this clears up any leftover conflicts.
- Open VirtualBox. Try to start your VM. It should boot now without the E_FAIL error.
If you still see the error after these steps, you probably have Windows Sandbox or Device Guard enabled. Turn those off too — they also use Hyper-V under the hood.
Why This Works
VirtualBox uses its own hypervisor (the thing that manages virtual machines). Hyper-V is Microsoft's built-in hypervisor. When both are active on the same machine, VirtualBox can't get exclusive access to CPU virtualization features. This causes the VM to fail with E_FAIL 0x80004005.
Reinstalling VirtualBox resets the driver stack and removes any corrupted files. Disabling Hyper-V removes the conflict. The combination fixes the issue for about 95% of users.
Less Common Variations of the Same Issue
VM Was Working, Then Suddenly Got E_FAIL
This usually happens after a Windows Update that enables Hyper-V features. Check if Windows Sandbox, Windows Subsystem for Linux (WSL 2), or Device Guard got turned on. Disable them using the same dism command above, but also run this:bcdedit /set hypervisorlaunchtype off
Then restart.
Error Only on One Specific VM
If other VMs work fine but one gives E_FAIL, the VM's configuration might be corrupted. Back up the VM folder (usually in C:\Users\You\VirtualBox VMs). Then delete the VM from VirtualBox Manager (right-click > Remove > Remove only). Re-add it by choosing Machine > Add, then pick the .vbox file. This rebuilds the config without re-creating the whole VM.
Guest Additions Crash After Update
Sometimes after updating VirtualBox, old Guest Additions cause E_FAIL. Uninstall Guest Additions from inside the VM (if it boots) or start the VM with the ISO mounted for Guest Additions. Reinstall them fresh.
Prevention Tips
- Don't install Windows Hyper-V features unless you really need them. That includes Windows Sandbox, WSL 2, and Device Guard. They all conflict with VirtualBox.
- Keep VirtualBox updated. Old versions have bugs that get fixed. Check for updates every couple months.
- Back up your VM folders regularly. If corruption happens, you waste time rebuilding the VM. Copy the whole folder to another drive once a month.
- Before a major Windows update, snapshot your VM. If the update breaks VirtualBox, you can roll back easily.
That's it. The error is annoying but fixable. If none of this works, you might have a deeper hardware issue — like virtualization disabled in BIOS. But 9 times out of 10, the steps above solve it.