Hello, I recently upgraded VirtualBox to version 4.3.26 which installed okay and opened okay. However, whenever I went to startup a VM I got this lovely error message.
E_FAIL (0x80004005)
I decided to then un-install virtualbox and install version 4.3.20, which I believe was my previous version as I remember updating VirtualBox but not this year. However downgrading I seem to get the same exact error message for all VM's I attempt to startup. My AntiVirus (Avira Free) does not pop-up any warnings or anything. I have attached the VBox Startup log.
Thanks!
Getting fatal error on startup on all VM's 0x80004005
-
GTAXL
- Posts: 2
- Joined: 25. Apr 2015, 17:15
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: CentOS 6.6 i386
- Location: Mount Vernon, Ohio
- Contact:
Getting fatal error on startup on all VM's 0x80004005
- Attachments
-
VBoxStartup.log- (102.32 KiB) Downloaded 4 times
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: just about all that run
Re: Getting fatal error on startup on all VM's 0x80004005
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
GTAXL
- Posts: 2
- Joined: 25. Apr 2015, 17:15
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: CentOS 6.6 i386
- Location: Mount Vernon, Ohio
- Contact:
Re: Getting fatal error on startup on all VM's 0x80004005
I've read all that, no help. I un-installed the windows update, re-installed virtualbox. Same issue
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: just about all that run
Re: Getting fatal error on startup on all VM's 0x80004005
this looks like your problem from the link you read of…
mpack wrote:This problem is on the host, not VirtualBox. VirtualBox merely reports it.
To explain: VirtualBox since 4.3.14 has introduced so called "hardening" features where it tries to prevent third party modules running as part of the VirtualBox program. The only exceptions are those which are covered by valid trust certificates. This topic discusses problems with this feature.
Your problem, or so it appears from the log, is that your host's certificates database has been corrupted, leading certification checks to fail for all modules, even those belonging to the host OS. The line "kernel32.dll [lacks WinVerifyTrust]" is a good example.
How to fix it? I have no idea. That's a Windows support question, so you'd have to ask Microsoft, or ask on a Windows forum.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.