mpack wrote:@donteatthebug:
Blame the spammers and hackers for the need for hardening, not the devs. The commercial reality is that VirtualBox can't be seen as a credible vector for malware, because the competition will not.
As to your problem - a glance at your log reveals it.
This seems to be a generic DLL loaded by some .NET apps, so the actual faulting app is harder to identify.1244.968: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -5667 (0xffffe9dd)) on \Device\HarddiskVolume3\Users\Fox\AppData\Local\Temp\ammemb64.dll [lacks WinVerifyTrust]
1244.968: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -5667 (0xffffe9dd)) on \Device\HarddiskVolume3\Users\Fox\AppData\Local\Temp\ammemb64.dll [lacks WinVerifyTrust]
1244.968: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -5667 (0xffffe9dd)) on \Device\HarddiskVolume3\Users\Fox\AppData\Local\Temp\ammemb64.dll [lacks WinVerifyTrust]
<and many more like it>
I'm curious to know why a legit DLL is being loaded from a temp folder and injected into the VirtualBox execution space, and why so many attempts? Until these questions are answered I suggest that you really shouldn't want to "turn off hardening at your own risk".
Thank you for the reply, I can sympathize.
I can answer that the "ammemb64.dll" is part of software called "Actual Multiple Monitors", used to make the Windows TaskBar act in a useful manner across multiple monitors. I've tried several alternative multi-monitor TaskBar utilities, but they lack functionality.