We are required to maintain the security log for 365 days. We have had this policy in place since windows 2k- however, the latest patched edition of Windows 11 causes the log file to grow insanely fast. We really need to find a solution to this- because not applying updates is not the solution.
The security log is now full (Windows 11 Only)
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
- I clear log and overwrite in event viewer but still happen back on the next day.
Thanks.
Windows for home | Windows 11 | Accounts, profiles, and login
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.
64 answers
Sort by: Oldest
-
Anonymous
2023-02-28T14:08:22+00:00 -
Anonymous
2023-02-28T14:24:25+00:00 I have not heard a WORD about this issue yet. I am still having some issues with the PC's getting the error that the security log is full and needs admin to fix...very frustrating. I run a EDR called ThirySeven4 and have Windows Defender and Security Essentials turned off so i am not experiencing issues with the WFP Logs.
-
Anonymous
2023-03-09T15:29:22+00:00 I have also been experiencing this issue with Windows 11 22H2 systems. Happens on my primary work laptop and my Windows 365 cloud PC which literally has nothing installed.
-
Anonymous
2023-03-15T14:11:36+00:00 Beyond finding out which events are filling up the log, has anyone found a way to have the log keep the "overwrite as necessary" setting?
-
Anonymous
2023-03-15T17:26:32+00:00 I was hoping yesterday's March Updates might have included a fix, but nope. My machine rebooted last night after the updates, and I was greeted first thing in the morning with not being able to log into my system yet again.
We aren't running Windows 11 in Production fortunately and it seems to be limited to Win11 22H2, so I haven't really been looking for a clever solution to fix it, I was just hoping it would be fixed by Microsoft. I am losing hope that this will be addressed and will probably need to come up with a solution.