The security log is now full (Windows 11 Only)

Anonymous
2022-12-20T07:02:25+00:00

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.

0 comments

64 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-04-25T18:14:20+00:00

    Sorry, don't know what the abbreviation of "sc" is. Would this be done on the admin side through powershell?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-04-25T18:30:21+00:00

    The SC command is used toconfigure, query, stop, start, delete, and add system services on the Windows command line. It's run via an elevated command prompt.

    Just looked up "sc command line" in a browser.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-05-10T15:39:18+00:00

    Also now seeing this issue in Windows 10 22H2 build. Not always the same PC but random across the whole network

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-08-16T16:54:10+00:00

    Hey yall,

    Only thing found from my MSP

    The fix I have found is to open gpedit.msc and apply the local group policy for the following.

    Select
    Computer Configuration > Administrative Templates > Windows Component
    > Event Log Service > Security > Control Event Log Behavior when the
    log file reaches its maximum size, Set it to Disable.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-08-21T09:02:53+00:00

    Hi,

    we have the same problem.

    For now for fix temporarily the issue we increased the log file to 1 gb, set automatic in security property and in cmd (in administrator mode) used this comand:

    for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1"

    The policy solution is not clean because applies it in all pc (also w10) and every reset.

    Microsoft please after six months the problem should already be fixed.

    It is a big problem because many people are in domain and can be possible that this issue happen when the worker aren't in office.

    Thanks.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments