NOTE 12th Dec: if you have a Windows 7 host that started failing in the last few days then this is most like due to buggy Windows update KB3004394. Microsoft have released a fix here. Do not post about your problem until you have tried their fix. While this Windows bug does trip over the VirtualBox hardening feature, it is not caused by it, and therefore is not a problem that should be discussed in this topic.
This topic is specifically for Windows users that may still have issues seen in version 4.3.20 caused by security being strengthened.
If you want to be taken seriously you need to post a few items as attachments (compressed is preferred)
- 1) Host OS and version
2) VBoxStartup.log (zipped)
3) Mention any host anti-virus, firewalls, protection software, and debugging programs etc which might be relevant.
As in the previous (4.3.14, 4.3.16, 4.3.18) discussions, the purpose of this topic is to gather diagnostic data needed to solve the hardening issues, and nothing else. Wibble posts, opinion posts, and posts that don't include necessary diagnostics will most likely be deleted. If a test build is created then you'll be expected to have tried it before you post.
Please be explicit about errors. Don't say "same as xxxxx". See list above for what's required.
Test builds can be found here: https://www.virtualbox.org/wiki/Testbuilds
---- Original message by MikeDiack.
I thought we'd best create this, as people are posting 4.3.20 problems at the end of the 4.3.18 thread...
Please post entries here
Early signs are that:
Comodo has problems with the 4.3.20 build 96996 build.
Symantec Endpoint Protection has problems with the 4.3.20 build 96996 build.
It sounds like Avast is working.