The Security Log is Now Full: 5 Ways to Fix This Error

Restart the Event Viewer or fix corrupt system files

4 min. read

Updated onJanuary 26, 2024

updated onJanuary 26, 2024

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

Withthe Windows Event Viewer tool, you can track important system information such as application and event logs. Using these data, you can quickly troubleshoot various system crashes, errors, or malfunctions on both the hardware and software levels.

However, multiple user reports show them an error The security log is now full – Event ID 1104. If you are also facing this issue, and want to resolve the problem, then in this guide, we will give you a bunch of solutions that you can use and possibly fix. So, let us get right into it.

What is Event ID 1104 and what triggers this problem?

The errors in the Event Log are common, and you will come across different errors with different error IDs. For example, Event ID 1104 pops up when the upper limit of the Security Log Event file size is attained, and there is no room to log more events.

Here are a few common reasons because of which you will come acrossThe security log is now full – Event ID 1104.

How can I fix The security log is full – Event ID 1104?

1. Turn on Event Overwriting

When you turn on the overwriting logs option, this will allow the Event Viewer to overwrite the old logs, in turn saving the memory from getting full.

2. Restart the Event Viewer service

If the Event Viewer is going through an issue, then this could cause it to malfunction and throw up errors. Restart the service following the above steps and see whether this resolves the problem.

3. Enable Event Viewer

Often the Event Viewer service can get disabled because of a conflict with another service, which is why you might getThe security log is now full – Event ID 1104error.

In such a scenario, you can go to the Services menu, enable the Event Viewer service and see if this fixes the error.

4. Uninstall the recently installed Windows update

Chances are that the recently installed Windows update is having a bug that is triggeringThe security log is now full – Event ID 1104error. Uninstall the recently installed update and check whether this fixes the issue.

5. Repair system files

You can use the in-built SFC Scan tool to identify corrupt or missing system files and replace them with new ones.

That is it from us in this guide. Several alternatives to Event Viewer will give you more detailed information about the processes and events on your PC.

You can check out our guide that gives you alist of the best third-party, even logging tools.

We have a guide to help you resolveEvent 2545 on the Microsoft-Windows-DeviceManagement Log.

You can also refer to our guide tofix the Esent error Event ID 455. And here are some quick tips in casesecurity info change is pending.

Feel free to let us know in the comments below which one of the above solutions helped you fix the Event ID 1104 – The SecurityLog is now fullerror.

The Security Log is Now Full: 5 Ways to Fix This Error#

How can I fix The security log is full – Event ID 1104?#

1. Turn on Event Overwriting#

2. Restart the Event Viewer service#

3. Enable Event Viewer#

4. Uninstall the recently installed Windows update#

5. Repair system files#