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
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 910771" data-attributes="member: 32260"><p>You do not need to turn off the Log (it will not help). The 24 hours limitation follows from the fact that on Windows 10 there are many <span style="color: rgb(184, 49, 47)"><strong>inbound connection events </strong></span>that can wipe out other events in the Windows Security Log.</p><p>[URL unfurl="true"]https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5152[/URL]</p><p></p><p>FirewallHardening makes the Security Log twice as bigger as the default Log (MaxSize = 0x01400000) and this is usually OK for surviving the events related to outbound connections for about 24 hours. If you want you can tweak the MaxSize of the log:</p><p>HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Security</p><p>MaxSize = 0x02800000 (change to a bigger value)</p><p></p><p>When you turn Off Logging, the value is automatically changed to Windows default (MaxSize = 0x01400000).</p><p>When you turn ON logging, the value is twice bigger (MaxSize = 0x02800000). So, do not turn OFF/ON Logging if you tweaked MaxSize.</p><p></p><p><strong>Anyway, you should look at the time moments in the Log when the AdGuard connections were blocked to find the possible correlation with the process which blocks AdGuard.</strong></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 910771, member: 32260"] You do not need to turn off the Log (it will not help). The 24 hours limitation follows from the fact that on Windows 10 there are many [COLOR=rgb(184, 49, 47)][B]inbound connection events [/B][/COLOR]that can wipe out other events in the Windows Security Log. [URL unfurl="true"]https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5152[/URL] FirewallHardening makes the Security Log twice as bigger as the default Log (MaxSize = 0x01400000) and this is usually OK for surviving the events related to outbound connections for about 24 hours. If you want you can tweak the MaxSize of the log: HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Security MaxSize = 0x02800000 (change to a bigger value) When you turn Off Logging, the value is automatically changed to Windows default (MaxSize = 0x01400000). When you turn ON logging, the value is twice bigger (MaxSize = 0x02800000). So, do not turn OFF/ON Logging if you tweaked MaxSize. [B]Anyway, you should look at the time moments in the Log when the AdGuard connections were blocked to find the possible correlation with the process which blocks AdGuard.[/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Top