E_FAIL (0x80004005) on Win10 Host

Discussions related to using VirtualBox on Windows hosts.

E_FAIL (0x80004005) on Win10 Host

Postby thuryanto » 4. Nov 2017, 16:27

After windows 10 update.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\HP\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Host = Windows 10
Guest = Windows XP
VB = 5.1.22

Please help me. Thanks!
Attachments
VBox.png
VBox.png (13.31 KiB) Viewed 51623 times
VBox.log
(121.57 KiB) Downloaded 369 times
VBoxHardening.log
(98.93 KiB) Downloaded 473 times
thuryanto
 
Posts: 2
Joined: 4. Nov 2017, 15:58

Re: E_FAIL (0x80004005) on Win10 Host

Postby luckyheather » 4. Nov 2017, 17:46

I also have this problem after a Windows 10 update yesterday. Here is what I have found and tried so far.

Although this has happened after a WIndows 10 update, this issue can occur on other OS'es too.

The VBoxHardening log file shows that a whole bunch of DLL files 'lack WinVerifyTrust'. Some sources suggest that this could be due to a conflict with AV software. I tried disabling the anti-virus and it did not help.

I have ran "sfc /scannow" in an administrator command prompt window to find out if any dll's needed fixing. No problems there.

Tried a VirtualBox Repair (accessed via Apps & features > Oracle VM VirtualBox > Modify) but no msi file in the Temp\VirtualBox folder. Downloaded the exe from the 'old builds' section of VirtualBox website. Restarted the PC after repair. No change to the current issue.

Need to think about this some more. My son is practically sitting on my shoulder!
Last edited by luckyheather on 4. Nov 2017, 19:11, edited 1 time in total.
luckyheather
 
Posts: 2
Joined: 4. Nov 2017, 16:51

Re: E_FAIL (0x80004005) on Win10 Host

Postby thuryanto » 4. Nov 2017, 19:03

I rolled back to the previous update and my VM's start as normal
thuryanto
 
Posts: 2
Joined: 4. Nov 2017, 15:58

Re: E_FAIL (0x80004005) on Win10 Host

Postby luckyheather » 4. Nov 2017, 19:46

I rolled back to the previous version of Windows 10 too. All working. Well done thuryanto. Yipee!
luckyheather
 
Posts: 2
Joined: 4. Nov 2017, 16:51

Re: E_FAIL (0x80004005) on Win10 Host

Postby rooby » 13. Nov 2017, 01:04

I had the same problem and workaround.

Uninstalling the "Security update for Microsoft Windows (KB4043961)" update in the control panel (Control Panel > Programs > Programs and Features > Installed Updates) let me start my VM again.
rooby
 
Posts: 1
Joined: 13. Nov 2017, 01:03

Re: E_FAIL (0x80004005) on Win10 Host

Postby Vaibhav Patil » 18. Dec 2017, 11:58

Don't uninstall windows updates, i have a perfect solution on it.
Uninstall virtual box and download new version 5.2.2-119230, and install it.
Your problem will get resolved.
Vaibhav Patil
 
Posts: 1
Joined: 18. Dec 2017, 11:55


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: socratis and 31 guests