I agree. CD or DUI are must have if someone is willing to use WD nowadays (at least on Windows 10). The built-in GUI of WD is a chaos.
Funny, one wants people to use Defender but then objects to a more friendly means to use it. I welcome something like this. For me, H_C has been a god-send, even if one uses only certain module/s. Whether you take the direct route or scenic, I mean, it's ultimately the same end--maybe even safer.
It makes me very concerned that a 3rd party program could have that much control over Defender. It surely can't be too difficult for something malicious to disable features or exclude itself without anyone knowing the difference.
Correct and there is a hidden premise here that this 3rd party program described is efficacious and to me, that is far from a given (and as you suggest) it may actually be harmful.
It won't be that easy because CD or DUI will be whitelisted by MS, so WD will not detect them as malicious. But if unknown applications tries to modify WD settings, I bet that WD will treat them as malicious (with defs or with it Tamper protection).
I wonder that this kind of software use is still very rare and therefore not profitable to hack. H_C was white-listed by Microsoft last time I installed the updated build. You can do some damage yourself simply by disabling or side-stepping SmartScreen. Aren't the potential benefits worth more than the risks? You would be bolstering Defender, not undermining it. But I def. see the points made on each side. Spoiler: hcuac
I don't feel that goes far enough. If they approve of this or any other thing that modifies security they should have a program where it is digitally signed by them or something similar. I'm sure CCleaner was whitelisted too before the incident. What if that had been allowed to change these settings?
I am sure that Andy or Dan could answer you better than me. Did you read their discussion about that here?
https://malwaretips.com/threads/defenderui.109495/page-6#post-956509 On my system DefenderUI crashed because of a comma vs period placeholder, that was a regional issue and is now fixed with this latest version 0.60 beta
Good news and progress. Thanks all especially Dan the man. Generous of him to put this together. EDIT-UPDATE: I installed it today onto the Windows 10 new lappy. My Word! This is IMPRESSIVE! Per Dan-
I forgot to mention that DefenderUI requires Tamper Protection to be turned off, so this is a problem. But I assume he will get this tool whitelisted by M$. On the other hand, malware often uses PowerShell to disable WD and I'm not sure if Tamper Protection protects against this. Good to know, will soon install the new version.
This would be HUGE. Thanks for the new updated notice @Gandalf_The_Grey and keeping us abreast in such a timely fashion as always.
You're welcome Another bug fix release: https://malwaretips.com/threads/defenderui.109495/page-7#post-957533 https://malwaretips.com/threads/defenderui.109495/page-7#post-957535
To each their own I reckon. No one MUST add what they don't prefer to the status quo. It's not a requirement. But there is an option!