virtualbox.org

mpack,

You locked my thread "VBox 4.3.18 and 4.3.20 -- VMs will not start"

As I stated in my post, this issue is NOT related to the KB. We have users both with this KB installed and without it. All have logs showing the same errors as the one I attached.

Can you unlock this thread please?

Error appears to be related to the latest Symantec AV updates and the famous "hardening" baloney. Problem resolved by the usual method of uninstalling VBox and reinstalling 4.3.12 (a.k.a., "the last version that actually works"). >:-(

If you don't have the KBxxx issue then you have one of the standard hardening issues - and again we already have a thread to discuss it. See the "security" discussion sticked at the top of this forum.

But, in fact you clearly do have the KB3003493 issue, since there's no other way I know of that that Kernel32 can "lack WinVerifyTrust".

I suggest that you look at the last few days of messages in that security thread.

Reverting to 4.3.12 is fine, assuming you'll never need a new feature or bugfix from VirtualBox again.