Page 1 of 1
VM will not start - Error 0x80004005 - See Logs
Posted: 11. Jan 2016, 23:02
by TBaFFz
I just tried to fire up my VM and I am getting error messages. Anyone know a solution to this issue?
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 11:18
by KelvinSmith
Are you running any virus scanner on your system?
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 11:23
by mpack
Well, according to the hardening log, your Windows kernel has been hacked.
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 15:16
by TBaFFz
mpack wrote:Well, according to the hardening log, your Windows kernel has been hacked.
Please explain more....
We run Avast Free for EDU.
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 15:20
by mpack
I'm not in a position to explain more, my previous sentence was a complete translation of what the log tells me. I.e. I have no information on the nature of the hack.
You can try to disable the AV to see if that is responsible.
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 15:35
by TBaFFz
I just ran windows updates and my VM is working now. Not sure what is going on. As far as the "hack" goes. Not exactly sure what to look for. I scanned system with MalwareBytes, Avast, SpyBot, and Adware. Nothing has come up. Maybe you are thinking the "hack" is Classic Shell which adds the "Start Menu" back?
Thanks for you help.
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 16:15
by scottgus1
Classic Shell which adds the "Start Menu" back?
That could be it. Theme changers & such do change core Windows files and don't allow security checks to pass.
Re: VM will not start - Error 0x80004005 - See Logs
Posted: 12. Jan 2016, 16:16
by mpack
That would be enough, but no: the log said that kernel32.dll failed a signature check, meaning the kernel has been hacked, not a theme DLL. I would expect a theme patcher to mess with the shell, I don't know why it would touch the kernel.