Security event 1104
The security log is now full
Channel: Security. Category: Other Events.
What it records
Generated when the Security event log reaches its maximum configured size while the log's retention method is set to 'Do not overwrite events (clear logs manually)': new events stop being recorded until the log is archived or cleared.
Why it matters
This flags a potential logging gap during triage: if retention isn't set to overwrite, a full log silently stops capturing new Security events, and the timing of 1104 tells you exactly when that blind spot began, useful both for catching misconfigured hosts and for noticing a log flooded to force this state.
What triggers it
Legitimately: high event volume on a busy host combined with a small maximum log size and 'do not overwrite' retention, simply filling up over normal operation. Rarely, maliciously: an attacker generating large volumes of benign-looking events to force the log to fill as a crude logging-suppression tactic.
In practice
Logged when the Security log reaches its configured maximum size and the retention setting prevents overwriting older events - for example a 20 MB log on a busy file server filling up after a spike in object-access auditing (4656/4663). Once logged, new security events stop being recorded until an administrator archives or clears the log (itself generating a 1102), so 1104 flags a collection gap an investigator needs to account for.
Sample record
The security log is now full.
Sources
Paste a record into Event XML or open a log in EVTX Reader.