Yusuf,
Have you tried the AuditPol command-line on that page to turn off WFP logging, anyway? I think that will help.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
Need your help, all devices that i monitor using windows 11 will hit the error (The security log is now full - Event ID 1104.) Need your advise for solve this problem
Temporary solution
Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Yusuf,
Have you tried the AuditPol command-line on that page to turn off WFP logging, anyway? I think that will help.
Hi Ramesh,
No, We can't stop WFP logging we need logs for auditing. the problem only comes in Windows 11 Version 22H2,
Here one thing notable in this version GPO behavior is changed automatically. but same GPO applied on other machines.( 21H2).
This is absolutely REDICILOUS that Microsoft knows this is a MAJOR issue, especially when you a have it on 1 couple HUNDRED Computers....this UPDATE is broken...please fix it....this is a SECURITY Logging issue and we should NOT have to disable anything....
Hi Butch,
Have you received any updates from Microsoft regarding this issue? We're encountering this problem on multiple machines that have been updated to Windows 11 version 22H2. We noticed that WFP logs are also being created on Windows 11 version 21H2, but we're not experiencing any login issues due to the GPO behavior remaining unchanged.
Our concern is why there are multiple entries being created in the WFP logs on Windows 11. Do you have any insights or suggestions on how to address this?
Thank you.
Hi, All,
From what I can tell, the chrome team thinks this is a microsoft issue and the microsoft team thinks this is a chrome issue. aka 'going to take a long time to resolve'. This dynamic means that Microsoft & Google together are creating an alley with no security logging on our company windows machines.
I have been slowly deriving what logging I have to turn off in order to keep our company laptops' security logs from filling up.
Originally: 40MB log files would fill up on computer startup, and then we'd have no security logging at all...unacceptable.
Logging these two items is required to achieve DoD security certification, so we're taking a hit here. But having no security logging is worse than incomplete ones.
Our standard is 365 days of logs, so I'll probably keep experimenting with a combination of reducing logging, increasing the log file size, and I may have to introduce a log shipping solution (the latter would be good for our security architecture anyway...)