VirtualBox VM fails to load after windows update - E_FAIL (0x80004005)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
chrisxa
Posts: 3
Joined: 22. Feb 2018, 22:39

VirtualBox VM fails to load after windows update - E_FAIL (0x80004005)

Post by chrisxa »

I'm having a lot of trouble with VirtualBox after the latest Windows update (possibly post hoc ergo propter hoc).
I've searched the forums here, on stackoverflow, and general google searches for a few hours without finding a solution that worked for my situation.

Recent changes:
* windows update
* virtualbox upgrade
* docker-machine upgrade
* vagrant upgrade

Environment:
* Windows 10 Version 10.0.19042 Build 19042
* VirtualBox Version 6.1.26 r145957 (Qt5.6.2)
* Vagrant 2.2.18 (I know this is 3rd party - including for completeness since one of the VMs was built with vagrant long ago)
* docker-machine 0.16.1

VMs:
1. buildbox - used by docker-machine
2. devenv - ubuntu guest that was built through vagrant long ago

The VM used by docker-machine was failing because the host-only adapter #2 didn't exist.
To troubleshoot this I:
* deleted the old buildbox vm
* uninstalled BitDefender in case it had interfered
* uninstalled VirtualBox
* rebooted
* installed VirtualBox as admin
* rebooted

The adapters still didn't exist.
Running `vboxmanage list hostonlyifs` created the interfaces, though their names were "Ethernet 4" and such, with the description set to "VirtualBox Host-Only Ethernet Adapter #2".
I created the new VM for docker with:

Code: Select all

docker-machine --debug create -d virtualbox --virtualbox-disk-size "150000" buildbox
This partially worked, but networking still failed.
Disabling and re-enabling the interface worked, so as a workaround I'll run:

Code: Select all

disable-netadapter -InterfaceDescription "VirtualBox*" -confirm:$false
enable-netadapter -InterfaceDescription "VirtualBox*" -confirm:$false
docker-machine restart buildbox
docker-machine env buildbox | Invoke-Expression
This fixed the issue with the docker-machine buildbox VM.

The other VM is still broken, regardless of whether I start it with vagrant (I know, 3rd party), or directly within the VirtualBox Manager.
The error when launching with vagrant (including in case others search by that error):

Code: Select all

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "7f996d6a-b179-43dc-902d-c9b159997196", "--type", "headless"]

Stderr: VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
Starting from the VirtualBox Manager:

Code: Select all

The VM session was closed before any attempt to power it on.

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
The logs are very verbose and I'm not sure what to look for.
Attachments
VBoxHardening.zip
(235.86 KiB) Downloaded 6 times
Last edited by chrisxa on 21. Sep 2021, 16:55, edited 1 time in total.
chrisxa
Posts: 3
Joined: 22. Feb 2018, 22:39

Re: VirtualBox VM fails to load after windows update

Post by chrisxa »

Adding vbox.log
Attachments
VBox.log
(124.68 KiB) Downloaded 25 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VirtualBox VM fails to load after windows update

Post by mpack »

The usual problem is Win10 enabling Hyper-v. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you need to continue the discussion then a VM log will be required (not the hardening log you already provided - that ends with an error code of zero hence you have no hardening problem).

Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VirtualBox VM fails to load after windows update - E_FAIL (0x80004005)

Post by mpack »

Thanks for the VM log. My guess was correct.
00:00:01.101364 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:01.162527 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
chrisxa
Posts: 3
Joined: 22. Feb 2018, 22:39

Re: VirtualBox VM fails to load after windows update - E_FAIL (0x80004005)

Post by chrisxa »

That fixed my issue - thank you.
Docker Desktop was a bit annoyed, but uninstalled then reinstalled and it seems happier with WSL2 now.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VirtualBox VM fails to load after windows update - E_FAIL (0x80004005)

Post by scottgus1 »

Docker and WSL2 will both enable Hyper-V, which may continue to interfere with Virtualbox. For the time being you'll have to use Virtualbox or Docker/WSL2, but not both in one boot of the host.
Post Reply