[Solved] E_FAIL (0x80004005)

[mogli73]

I’ve also downgraded to V 4.3.12 and it works with avira.
Can anybody report or post en link if there is a fix (new version of avira or virtualbox)?

[mogli73]

any news here???

[mpack]

What news are you expecting? This isn't the Avira support forum.

[mogli73]

I'd like to know if the actual version of virtualbox is working with the avira antivirus.

[mpack]

"The actual version"? Anyway, you need to ask Avira about their bugfix schedule.

[moudy001]

Just wish to confirm, that AVIRA! ist the culprit.
VB on my DELL Latitude E6430, Intel Core i5-3320M, 8G RAM, stopped startet VMs after an Avira Professional Update in Dez.
Uninstalled Avira, VB worked ok again.
Re-Installed Avira, VB could't start VMs.
Uninstalled Avira again, VB worked ok again.

Installed AVG AV Free = no problems with VB 5.0.12 r104815

[mpack]

To be fair, all you can conclude from that procedure is that there is a conflict between VirtualBox and Avira. However Avira have already acknowledged that the fault is theirs and that a fix is planned (however don't expect them to post Avira release notices here). The "hardening" sticky at the top of this forum gives a workaround (other than the obvious one of dumping Avira).

[moudy001]

AVIRA Productversion 15.0.15.141 from 17.02.2016 is out.

Virtual Box working ok again since this update by Avira

Hans

[ZZ]

Avira is not the problem...

I never use Avira. I use Eset Smart Security.

I disabled everything, All features of ESS but same error...

Only installing Vbox 4.3.12 version, solves the problem.


Conclusion: Problem is in VirtualBox's new versions.

[scottgus1]

Conclusion: Problem is in VirtualBox's new versions.

More like:

Jump to Conclusion: Problem is in VirtualBox's new versions.

Versions after 4.3.12 check for malware that can use Virtualbox to do more damage to your PC. So your host PC is more vulnerable to drive-by downloads, etc. with 4.3.12, and you can't run later OSs.

And of course with this being your first post and no Minimal information needed to be able to help or exact error messages or logs to help us help you....

[ZZ]

scottgus1

Thank you for your quick response


Well, I agree with you about security and also prefer newer versions...

I'm a long time Vbox user and right now Vbox 5.X is installed and running smoothly on my linux machines (Fedora 22 and 23)

But windows versions I tested VirtualBox-4.3.36-105129-Win, VirtualBox-5.0.14-105127-Win and VirtualBox-5.0.16-105871-Win have some problems. I tried to find solutions but without success...

And this thread talks about Avira... I never used Avira...

I just installed the latest VirtualBox-5.0.16-105871-Win on my test pc in order to reproduce the error.

Here it is

Host: Windows 8 Pro 64-Bit
Processor: Intel(R) Core(TM) i7 -2600 CPU @ 3.40GHz 3.40GHz
Ram 8.00 GB

Guest (I'm trying to install): Win8 Pro X86. Same problem with XP and linux guests...

Virtualbox version installed: 5.0.16-105871

Installing the guest from iso file fails on start.

Error Code:

Code: Select all

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


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Log: Attached.

[scottgus1]

Thanks for the log! Some observations:

Linux hosts don't have the security glitch that Windows hosts have, so there's no hardening checks on Linux. Failed hardening checks on Windows will prevent the guest from starting, even to boot from an ISO.

Searching for the word "error" in the log shows errors involving shell32.dll, a Windows file.

A Google search on "shell.dll hardening site:forums.virtualbox.org" shows a few links that may be pertinent:

viewtopic.php?f=6&t=75027
viewtopic.php?f=6&t=69830

Do you have a theme patcher on your host? Something to change how the OS looks? These might be the cause.

It would be interesting, if you have the capability, to temporarily put another disk in your host, install a fresh Windows 8 on it, no updates, no antivirus, no anything else, then put the latest Virtualbox 5 on and see if a guest can boot (even a bootable ISO running means Virtualbox is happy).
Then let the updates happen, and after each batch, try Virtualbox again. If you can get all the updates (seems only Windows 7 hosts were thusly affected, but it doesn't hurt to be sure) and Virtualbox remains responsive then put on the Eset. Gradually rebuild the system on the new disk until Virtualbox doesn't run. The last thing you put on is the culprit.

[michaln]

Linux hosts don't have the security glitch that Windows hosts have, so there's no hardening checks on Linux.

I have to correct that. The Linux (and OS X and Solaris) versions of VirtualBox are hardened and have been for a long time. That means for example that the (unprivileged) user starting a VirtualBox VM can't attach a debugger to it.

The big difference is that Unix has had a clearly defined security model for well over 30 years, and Windows-style craziness (like random DLLs injecting themselves into any process, or any user being able to overwrite system libraries) does not exist. So when hardening was enabled in those VirtualBox versions, 99.9% of users didn't even notice.

Windows on the other hand is... interesting. In the carefree days of Windows 3.1, people learned to do things like dynamically install hook DLLs that run in the context of every GUI process, which from a security perspective is total insanity. To be clear, Microsoft has made major improvements in every Windows version released in the last 10+ years, but this is basically Microsoft of today trying to undo the near-infinite damage that the Microsoft of 1990s made.

[Firedragon]

I have the same problem,but i don't have avira. I was just trying to make a test of 2008, but i never reached a point where i could start the installation, is trials blocked in some way?

[mpack]

I'm going to close this 3 year old topic, as the title is far too broad. If you have a question to ask then start your own topic, ask your question, and provide minimum diagnostic information for an affected VM, including a zipped VM log (VBox.log). If you have a hardening problem (VBoxHardening.log ends with exit code other than 0) then include that in the zip too. Don't include it otherwise.

Providing a log :-
With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (and/or VBoxHardening.log) to a zip file. Attach the zip to your description, in a topic with a well chosen name.