Fix ERROR_LOG_FULL (0X000019E4) – Log Space Exhausted

You're seeing ERROR_LOG_FULL (0x000019E4) and your application or service just stopped working. Classic symptom: you open Event Viewer and it's blank or stuck loading. The culprit here is almost always the Windows event log hitting its maximum size. I've seen this on Windows Server 2012 R2, 2016, 2019, and even Windows 10 Pro workstations that have been running for months without a log rotation or cleanup.

Don't bother with sfc /scannow first—that rarely helps here. The fix is straightforward: clear the full log, increase its size, or fix a corrupted log file. Below are the three most common causes and how to fix each one.

1. The Event Log Hit Its Max Size (Most Common)

By default, Windows caps each event log (System, Application, Security) at 20 MB. Once it's full, new events get dropped—unless you've set the log to retain old events by overwriting them. Most admins don't, so the log fills up and throws 0x000019E4.

Fix: Clear the log or increase its size

Open Event Viewer (eventvwr.msc). Right-click the log that's full (usually Windows Logs > System or Application). Select Properties. You'll see the current max size and it'll likely be at 20 MB. Set it to at least 100 MB for production servers—I usually go with 200 MB. Then click Clear Log to free space immediately.

If Event Viewer is unresponsive, use the command line. Open PowerShell or CMD as admin:

wevtutil gl System
wevtutil sl System /ms:209715200
wevtutil cl System

The gl command shows current settings (look for maxSize). The sl command sets a new max size in bytes—209715200 bytes = 200 MB. The cl command clears the log. Repeat for Application and Security logs if needed. This fix works on Windows 8.1 through Server 2022.

2. Corrupted Event Log File

Sometimes the log file itself gets corrupted, especially after a crash or forced shutdown. You'll see 0x000019E4 even after clearing the log. Event Viewer might crash when you try to open it.

Fix: Delete and recreate the log file

First, stop the Windows Event Log service:

net stop EventLog

Then navigate to C:\Windows\System32\winevt\Logs. You'll see files like System.evtx, Application.evtx, etc. Rename the problematic one (e.g., System.evtx.old). Do not delete it immediately—keep the backup in case you need it for forensics.

Start the service again:

net start EventLog

Windows will create a fresh log file automatically. You'll lose old events but the error goes away. If you need to preserve the old events, use wevtutil epl System backup.evtx before stopping the service.

I've seen this on Windows Server 2016 after a dirty shutdown. The log file was 20 MB but completely unreadable—Event Viewer threw an error about log corruption. Renaming the file fixed it instantly.

3. Log File on a Full Disk

This one trips people up. Even if the log size is set correctly, if the drive (usually C:) is out of space, Windows can't write new entries. The error is the same: 0x000019E4.

Fix: Free up disk space

Check your free space on C:. If it's below 1 GB, that's your problem. Run Disk Cleanup (cleanmgr) and select System files to clear Windows Update cache, temp files, and old logs. Also check if the pagefile or hibernation file is eating space—disable hibernation with powercfg -h off if you don't need it.

For servers, I've had to move the event log folder to another drive. You can do this via registry:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\EventLog" /v FilePath /t REG_EXPAND_SZ /d "D:\Logs" /f

Then restart the EventLog service. This is rare but worth knowing if you're managing a database server with limited C: space.

Quick-Reference Summary

This error is annoying but easy to fix once you know what you're dealing with. Start with the log size—that's the fix in 80% of cases. If you're still seeing 0x000019E4 after that, check disk space. If that's fine, it's corruption. You'll have it sorted in under 10 minutes.