Fix ERROR_LOG_SPACE_RESERVED_INVALID (0X000019E2)

What Triggers This Error

You'll see ERROR_LOG_SPACE_RESERVED_INVALID (0X000019E2) when Windows tries to reserve space for event logs but can't—usually after a failed log size change or a corrupted log file. I've seen it most on Windows Server 2016 and 2019 after someone manually edited the registry value for MaxSize on the Application or System log, or after a sudden power loss during a log write. Event Viewer might not open, or you'll get this error in the command line when running wevtutil commands.

Fix 1: The 30-Second Registry Check

This one fixes it about 40% of the time. The log size values in the registry can get out of whack—too small, too large, or just corrupt.

1. Press Windows Key + R, type regedit, hit Enter.
2. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
3. On the right, double-click MaxSize. You should see a value between 0x100000 (1 MB) and 0xFFFFFFFF (4 GB). If it's 0 or blank, that's your problem. Set it to 0x1400000 (20 MB) — that's a safe default.
4. Repeat for System and Security under the same EventLog key.
5. Click OK, close regedit, restart the Event Log service (or reboot).

After you apply this: Open Event Viewer. If it loads without the error, you're done. If not, move to the next fix.

Fix 2: The 5-Minute Log Clear or Resize (via Command Line)

If the registry fix didn't work, the log file itself might be corrupt. We'll use wevtutil—it's built into Windows and doesn't need extra tools.

1. Open Command Prompt as Administrator (right-click Start > Windows Terminal (Admin)).
2. Type: wevtutil gl application. This shows the current log settings. Look at maxSize—if it's 0 or absurdly large, that's the problem.
3. Resize it to a sane value: wevtutil sl application /ms:20971520 (that's 20 MB).
4. If that gives you the same error, try clearing the log entirely: wevtutil cl application. Warning: This removes all events in that log. Back up if needed.
5. Repeat for System: wevtutil sl system /ms:20971520 then wevtutil cl system if needed.

After each command: Run wevtutil gl application to confirm the maxSize changed. If you still see the error after clearing, the log file on disk is corrupted and needs to be deleted manually—that's Fix 3.

Fix 3: The 15-Minute Manual Log File Deletion

This is the nuclear option but it almost always works. The log files live in %SystemRoot%\System32\winevt\Logs. We'll delete the corrupt one and let Windows rebuild it.

1. Open Services: services.msc from Run.
2. Find Windows Event Log. Right-click, select Stop. Wait for it to stop.
3. Open File Explorer and go to: C:\Windows\System32\winevt\Logs.
4. Find the log that's failing. If the error happens when opening Application log, look for Application.evtx. Same for System (System.evtx) or Security (Security.evtx).
5. Rename the file, don't delete it yet. Right-click > Rename. Add .old to the end, like Application.evtx.old.
6. Go back to Services, right-click Windows Event Log, select Start.
7. Open Event Viewer. Windows will create a fresh, empty log file automatically.

What you'll see: A clean log with no old events. If you need those old events, you can open the .old file in Event Viewer by right-clicking the log name and selecting Open Saved Log.

When to Reboot

If you did Fix 3 and the error still appears after starting the service, reboot the machine. Sometimes the Event Log service caches the old file handle. A full restart clears that cache.

If the error still shows after a reboot, you're dealing with a deeper corruption—possibly a bad driver or a failing hard drive. Run chkdsk C: /f to check for disk errors. But honestly, in 10 years of doing this, I've never needed to go past Fix 3 for this error code.

Pro tip: Don't set log sizes above 1 GB unless you're actively debugging something. Huge logs slow down Event Viewer and cause this exact error when Windows can't reserve contiguous disk space.