None of my VM Machines works E_FAIL (0x80004005)

[ijaguirre]

Dear all

I always use virtual box with any problem, but a couple days ago I have i received this screen message:

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

Código resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

I try everything, I re-install Virtul Box twice (simply way, i don't touche the registry), I delete all my virtual box machines and use an old file from an external disk

Please, I need a solution

[scottgus1]

Take a look at: Diagnosing VirtualBox Hardening Issues Hardining problems happen because another program on your computer is interfering with Virtualbox. This tutorial is a list of suggestions. We will not be able to tell you exactly what to do, only offer ideas.

Your hardening log shows an exit code of 1.

Also, the log says you have Avast installed. As a troubleshooting step, completely uninstall anything related to Avast. Check their website to see if they offer a cleaning tool to completely remove Avast, and use it. Then reboot your PC, reinstall Virtualbox by right-clicking the installer and choosing Run As Administrator. Then reboot your PC again.

If Virtualbox still does not run, zip and post a new Hardening log.

If Virtualbox does run a guest, then try reinstalling Avast.

[goldempo]

Screenshot Chinese Blog page

Prnt Scrn_11zon.jpg (87.88 KiB) Viewed 1018 times

{SOLVED}
One has to use the other start methods from the falling menu next to the green . These are the "Headless Start" and "Detachable Start", which appear on the falling menu and not to use "Normal Start".

P.S I have to admit, that I browsed the internet and found this information in a Chinese blog and used the google translator to translate it:

[scottgus1]

goldempo, thanks for posting what you found!

Actually, getting around a hardening error by starting the VM headless or detachable is a known workaround and troubleshooting step, and is mentioned in the "Diagnosing" link above, post 5. However, the exit code that calls for this workaround is 0xC0000005, instead of the OP's exit code 1.

If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.

The problem caused by the graphics drivers comes from a graphics driver file being unsigned or failing security signing, which trips up Virtualbox hardening. Sometimes the graphics card companies forget to completely sign new driver releases. Please see the tutorial for why Virtualbox should care.