Fix STATUS_LOG_CORRUPTION_DETECTED 0XC0190030

You're sitting at your desk, Windows just booted up, and instead of your desktop you get a blue screen or a message saying STATUS_LOG_CORRUPTION_DETECTED with the error code 0XC0190030. Maybe it happens after a power outage, a forced shutdown, or a failed Windows update. I've seen this most often on Windows 10 22H2 and Windows 11 23H2 machines after the system crashed while writing event logs. The specific trigger: the system tried to write to the Windows\System32\winevt\Logs folder when the drive had no space, or the write got interrupted mid-stream.

What this error actually means

The error code 0XC0190030 is defined as STATUS_LOG_CORRUPTION_DETECTED. It's not a hardware failure 99% of the time. It's a problem with the binary log files that Windows uses to track everything from application crashes to security events. When one of these files gets corrupted—usually Application.evtx, System.evtx, or Security.evtx—the system can't read it next time it tries, and it throws this error.

The real fix isn't complicated. You need to repair the system files and rebuild the log files. Skip the registry edits you see on some forums—they don't touch the root cause. Here's what works.

Fix: Step-by-step repair

Boot into Safe Mode with Command Prompt.
Restart your PC. As soon as you see the Windows logo, hold the power button to turn it off. Do this three times. On the third restart, Windows will show "Preparing Automatic Repair." Let it load. Click Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart. After the restart, press 6 or F6 to enable Safe Mode with Command Prompt.
Run SFC to fix system files.
In the Command Prompt, type:
```
sfc /scannow
```
Hit Enter. Wait. This will take 5 to 15 minutes. SFC will scan all protected system files and replace any corrupt ones from the local cache. After it finishes, you should see a message like "Windows Resource Protection found corrupt files and successfully repaired them." If it says it found corrupt files but couldn't fix them, don't worry—we'll handle that next.
Run DISM to fix the system image (if SFC couldn't fix everything).
Type this command:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Press Enter. This connects to Windows Update to download clean copies of corrupted system files. It can take 20 minutes or more. When it's done, you'll see "The restoration operation completed successfully." If you get an error about the source, run this instead (it uses Windows installation media—you'll need a USB or DVD):
```
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
```
Replace C:\RepairSource\Windows with the actual path to your Windows install media's sources\install.wim or install.esd file.
Rebuild the corrupted event logs.
This is the step that actually clears the corruption. In the same Command Prompt, type:
```
wevtutil el
```
This lists all event log names. Find the log that's causing trouble—usually it's one of the big ones like Application, System, or Security. To clear and reset a specific log, run:
```
wevtutil cl Application
```
Replace Application with the log name from the list. Run this for each log you want to reset. After running wevtutil cl, the log file is emptied and recreated fresh. No more corruption.
Reboot normally.
Type exit to close the Command Prompt. Click Restart from the Safe Mode screen, or just use Ctrl+Alt+Del and choose restart. Your machine should boot to the desktop without the error.

What to check if it still fails

If you're still seeing 0XC0190030 after those steps, the problem might be deeper. Here's what to try next:

Check your drive for physical errors. Run chkdsk C: /f /r from the Command Prompt (in Safe Mode). This scans the disk for bad sectors and fixes file system errors. It'll ask to schedule a scan on next boot—type Y and then restart. The scan runs before Windows loads, so you'll see a blue screen with percentage progress. Let it finish—it can take hours on a large drive.
Check disk space. If your boot drive is almost full—less than 10% free—Windows can't write logs properly, which triggers this error. Free up space by emptying the Recycle Bin, running cleanmgr (Disk Cleanup), and deleting old Windows update files.
Roll back a recent update. If the error started after a Windows Update, boot into Advanced options again and select Uninstall Updates. Remove the most recent Quality Update or Feature Update. Reboot and see if that fixes it.
Replace the log files manually (last resort). If wevtutil won't clear a log, you can delete the files directly. Boot into Safe Mode, open File Explorer, navigate to C:\Windows\System32\winevt\Logs, and delete the corrupt .evtx files (like Application.evtx). Windows will recreate them on next boot. Warning: This deletes all your event history. That's usually fine for most users.

Note: I've seen this error on laptops that suffered a sudden shutdown during a heavy update. The real fix is almost always the DISM + wevtutil combo. Don't bother reinstalling Windows unless every step above fails—and even then, try a repair install first.