VM will not start - Error 0x80004005 - See Logs

[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}

[KelvinSmith]

Are you running any virus scanner on your system?

[mpack]

Well, according to the hardening log, your Windows kernel has been hacked.

[TBaFFz]

Well, according to the hardening log, your Windows kernel has been hacked.

Please explain more....

We run Avast Free for EDU.

[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.

[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.

[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.

[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.