Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
VoodooShield
DefenderUI by VoodooShield - Turn on Hidden Security Features of Microsoft Defender
Message
<blockquote data-quote="Andy Ful" data-source="post: 954764" data-attributes="member: 32260"><p>Your suggestions make sense only for files that are not whitelisted by Microsoft. For these reasons, before whitelisting, ConfigureDefender executables are often recognized as malicious (false positive). That is why I do not publish applications before whitelisting by Microsoft. Another reason for whitelisting is the ASR prevalence rule that would block non-whitelisted executables.</p><p></p><p>Edit.</p><p>The examples noted in my posts were exceptional (2 events over several years), so if you will be lucky they may not happen to you. The second example is not related directly to ConfigureDefender, but to PowerShell - the same behavior was visible when the command lines were executed from the PowerShell console.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 954764, member: 32260"] Your suggestions make sense only for files that are not whitelisted by Microsoft. For these reasons, before whitelisting, ConfigureDefender executables are often recognized as malicious (false positive). That is why I do not publish applications before whitelisting by Microsoft. Another reason for whitelisting is the ASR prevalence rule that would block non-whitelisted executables. Edit. The examples noted in my posts were exceptional (2 events over several years), so if you will be lucky they may not happen to you. The second example is not related directly to ConfigureDefender, but to PowerShell - the same behavior was visible when the command lines were executed from the PowerShell console. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
