a.h.8 wrote:[...] it should at least be possible to [...] allow {the user] to authenticate the offending function manually and on his own risk. Yes, that is a risky thing to do, but probably still a lot better then going back to an outdated software version with no hardening at all.
OMG Yes Please ! ! !

I've been unable to run anything newer than VirtualBox v4.3.12 due to these frustrating "hardening" errors. Really wish VirtualBox would at least provide some kind of way to allow bypassing these hardening obstacles at own risk
(other than tweaking the source code and compiling our own build with signed drivers & all etc), just like most other software out there.

I used to love VirtualBox and recommended it to everyone... until the
post v4.3.12 apocalyptic hardening was forced upon us on that terrifying Tuesday July 15th 2014.
Will the nightmare ever end?
Still no-go on the latest test build (VirtualBox-5.0.11-104456-Win.exe)
Host OS: Windows 7 Ultimate SP1 64bit
Antivirus\Firewall: ESET Smart Security v8.0.319.0