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
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
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 955208" data-attributes="member: 32260"><p>H_C cannot be <strong>directly</strong> involved because its processes do not run at all, except when you manually run H_C, ConfigureDefender, etc. Also, these processes do not use Svchost. The only thing that H_C can cause <strong>indirectly</strong> is a more aggressive Defender setup. So, Defender on default settings could ignore <span style="color: rgb(41, 105, 176)"><strong>Behavior:Win32/WDBlockFirewallRule.P. </strong></span>and detect it with advanced setup.</p><p></p><p><s>The issue can be also related to O&O Shutup, because it changes firewall rules to restrict Windows telemetry (not related to Defender O&O settings). In fact, any application which uses a service and can modify firewall rules can be the issue.</s></p><p><s></s></p><p><s>I am not sure if this issue will happen again, because it could be forced by the Run once key after Windows restart. If so, then a single Defender block simply disabled adding firewall rule and the application will not try to do it again. </s> <----- this possibility seems to be excluded by the details of the issue described on the Glasswire forum.</p><p></p><p>Edit. Checked O&O Shutup. It does not use a service or change Firewall rules under the Registry key:</p><p>HKLM\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules</p><p>From the Glasswire forum about <strong>Behavior:Win32/WDBlockFirewallRule.P</strong> issue it follows that the above Registry key is involved.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 955208, member: 32260"] H_C cannot be [B]directly[/B] involved because its processes do not run at all, except when you manually run H_C, ConfigureDefender, etc. Also, these processes do not use Svchost. The only thing that H_C can cause [B]indirectly[/B] is a more aggressive Defender setup. So, Defender on default settings could ignore [COLOR=rgb(41, 105, 176)][B]Behavior:Win32/WDBlockFirewallRule.P. [/B][/COLOR]and detect it with advanced setup. [S]The issue can be also related to O&O Shutup, because it changes firewall rules to restrict Windows telemetry (not related to Defender O&O settings). In fact, any application which uses a service and can modify firewall rules can be the issue. I am not sure if this issue will happen again, because it could be forced by the Run once key after Windows restart. If so, then a single Defender block simply disabled adding firewall rule and the application will not try to do it again. [/S] <----- this possibility seems to be excluded by the details of the issue described on the Glasswire forum. Edit. Checked O&O Shutup. It does not use a service or change Firewall rules under the Registry key: HKLM\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules From the Glasswire forum about [B]Behavior:Win32/WDBlockFirewallRule.P[/B] issue it follows that the above Registry key is involved. [/QUOTE]
Insert quotes…
Verification
Post reply
Top