Guys, there are going to be blocks, that is the whole point of the beta test… at least we know the mechanism is working
. These new features are only a couple of weeks old, so it is going to take some time to finish writing the rules.
Several people have asked about how DefenderUI Pro is different from SWH and OSArmor. I have said for a very long time now that I am not a huge fan of globally and blindly blocking anything. It simply breaks way too much stuff and the user is left wondering why his computer is not working properly. SWH is quite limited in scope and only blocks certain attacks, for example there is no anti-exploit or vulnerable process mechanism that I have found. OSArmor includes most or all of the potential attacks, but a lot of the options are disabled because enabling these options would interfere with normal operation.
The whole point of DefenderUI Pro is to include all possible attacks and to block what actually needs to be blocked and allow what actually needs to be allowed, in other words, smart windows hardening. Quite simply, the best of both worlds, but it is going to take a little bit of time.
I actually might change the name of the “Anti-Malware and Anti-Exploit Contextual Engine” option to Smart Window Hardening
. BTW, there are a handful of other contextual engines on the market, but DefenderUI Pro has a few unique ideas that I am pretty sure have not been implemented by anyone, and I just thought of another extremely cool one today that I will implement soon.
Sure, there have been a couple of crazy block incidences, but overall it is looking great. Within a week or so we should have all of the rules figured out, so we are much closer than you think we are.
After you install the new version, please reset the whitelist in the DefenderGuard tab. There was a small bug that created a lot of blocks.
I will catch up on the rest of the posts I missed asap, but for now, here is the latest version…
DefenderUIPro 0.92 beta
SHA-256: 27157d2db0bece25d981f8671f7ce01b80788a7cc9345475f0a6ab0bb1d52ca8