Fix STATUS_LOG_POLICY_INVALID (0xC01A0016) - 3 Steps

What's this error about?

STATUS_LOG_POLICY_INVALID (0xC01A0016) shows up when the Common Log File System (CLFS) can't read the policy settings tied to a log file. You'll see this error in Event Viewer or during a system process that uses CLFS—like Windows Update, backup software, or disk defragmentation. I've seen it most often after a Windows update crashed halfway through or after a disk had bad sectors.

The real fix? You need to figure out which log file has bad policies and either repair or delete it. Let's walk through this step-by-step, starting with the easiest thing you can try.

Step 1: Quick check—reboot and run SFC (30 seconds)

Before you dig into advanced stuff, reboot your machine. I've seen this error clear up after a simple restart because the log file was stuck in a weird state.

Restart your PC completely—not shut down and power on, but click Restart.
After Windows loads, open Command Prompt as admin. Press Windows Key + X, then click Windows Terminal (Admin) or Command Prompt (Admin).
Type this and press Enter:
```
sfc /scannow
```
Wait for it to finish. It'll check system files for corruption. If it finds anything, it'll fix it automatically.

What you should see: The scan takes 5–10 minutes. At the end, it'll say "Windows Resource Protection found corrupt files and successfully repaired them" or "did not find any integrity violations."

If the error's still there after this, move to Step 2.

Step 2: Check the log file with chkdsk (5 minutes)

This error often points to a disk problem that messed up the CLFS log file. The tool for that is chkdsk.

Open Command Prompt as admin again.
Run this command:
```
chkdsk C: /f /r
```
Replace C: with the drive where your Windows is installed. For most people, that's C:.
It'll say the drive is in use and ask if you want to schedule it for the next restart. Type Y and press Enter.
Restart your PC. The scan will run before Windows loads. It'll check for bad sectors and fix file system errors.

What you should see: A blue screen with a progress bar. The scan can take 30–60 minutes depending on your drive size. Let it finish. After it's done, Windows boots up normally.

If the error persists after this, you've got a corrupted CLFS log file. That's Step 3 territory.

Step 3: Advanced fix—delete or rename the CLFS log file (15+ minutes)

This is the nuclear option. You need to find the specific log file that's causing the problem and get rid of it or move it. I've done this dozens of times and it works.

3a. Find the culprit

The error message often tells you which log file is broken. Check Event Viewer:

Press Windows Key + R, type eventvwr.msc, hit Enter.
Go to Windows Logs > System.
Look for events with Source CLFS or NTFS and error code 0xC01A0016. Double-click one. The General tab will show a file path like C:\Windows\System32\LogFiles\...\something.blf.

If you can't find the exact file, the most common one is in the SoftwareDistribution folder used by Windows Update. Start there.

3b. Take ownership and delete it

You can't delete CLFS files while Windows is running because they're locked. So you'll do this from the Windows Recovery Environment (WinRE).

Hold Shift and click Restart from the Start menu. Your PC will boot into the blue recovery screen.
Click Troubleshoot > Advanced options > Command Prompt.
Your drive letters change in WinRE. Usually C: is your system drive, but it might be D:. Type notepad and press Enter, then in Notepad click File > Open to browse drives until you find your Windows folder.

Once you know the correct letter (let's say it's D:), run these commands one at a time:

takeown /f D:\Windows\System32\LogFiles\FileThatsBroken.blf
    icacls D:\Windows\System32\LogFiles\FileThatsBroken.blf /grant Administrators:F
    del D:\Windows\System32\LogFiles\FileThatsBroken.blf

Replace FileThatsBroken.blf with the actual file name from Event Viewer. If you don't know the file, skip to 3c.

Close the Command Prompt, click Continue to reboot normally.

What you should see: Windows will recreate the log file automatically when it's needed. The error should be gone.

3c. No specific file? Nuke the SoftwareDistribution log

If you couldn't find the exact file, the safest bet is to clear the Windows Update log files. These get corrupted all the time.

In WinRE Command Prompt, run these commands:

takeown /f D:\Windows\System32\LogFiles\WUMed\ /r /d y
    icacls D:\Windows\System32\LogFiles\WUMed\ /grant Administrators:F /t
    del /f /s /q D:\Windows\System32\LogFiles\WUMed\*.*

Reboot. Windows will rebuild these log files fresh.

Warning: This clears the Windows Update log. If you're troubleshooting a failed update, you might lose the history. But honestly, if you're here, the error is more important.

Still stuck?

If none of these work, the issue might be deeper—like a failing hard drive. Run a full disk diagnostic (like SeaTools for Seagate or WD Dashboard for Western Digital). But in 9 out of 10 cases, Step 3b or 3c kills this error dead.