Page 2 of 2
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 15. Mar 2022, 16:35
by fth0
For a test, uninstall Malwarebytes Chameleon. If the error persists, post a new (zipped) VBoxHardening.log file.
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 17. Mar 2022, 14:25
by martin123
Hi All,
When I start the VM in "Deatachable Start" mode, it does not work properly. The VM works very slowly. There is some heaviness.
How to make the VM work normally, by starting it in "Normal Start" ?
Thanks in advance,
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 17. Mar 2022, 21:21
by scottgus1
Did you try uninstalling Malwarebytes, per fth0's suggestion?
Also, per the recommended "Diagnosing" tutorial posted early on, the ability to start Detachable but not Normal is discussed and a possible solution presented.
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 18. Mar 2022, 11:22
by martin123
Hi fth0 & scottgus1,
Hi All,
I had not installed the MalwareBytes Chameleon program, maybe it is a leftover from an old installation.
I renamed the file mbamchameleon.sys in C:\Windows\System32\drivers\mbamchameleon.sys, but the problem with the normal VM startup remains the same.
The same error message keeps appearing.
When I renamed mbamchameleon.sys, VirtualBox updated the VBoxHardening.log file that I provide here.
Note that I have completely uninstalled VirtualBox and deleted all log files. I reinstalled it again, I added the VM vbox, but the issue persists : the VMs don't start normally anymore !
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 18. Mar 2022, 22:49
by fth0
The VirtualBox hardening code couldn't verify the Authenticode signature of one of the major Windows DLLs named user32.dll, which probably means that this file has been modified. This will prevent VirtualBox from starting any VM. You could try sfc /scannow from within a Command Prompt with administrator rights.
Re: VM start failed [E_FAIL (0x80004005)]
Posted: 20. Mar 2022, 01:33
by martin123
I ran the "sfc /scannow" command, and apparently the system repair was done. After the reboot, the normal VM launch seems to work again.
Thanks, fth0, for your support.