Fix STATUS_SECURITY_STREAM_IS_INCONSISTENT (0XC00001A0)

Cause #1: Corrupted NTFS Security Descriptor (most common)

This error shows up as a blue screen or a pop-up when you try to open a file or folder. I see it most often after a power outage or a forced shutdown. The NTFS file system keeps security info in a hidden stream. If that stream gets scrambled, Windows can't read who owns the file or what permissions apply.

The quickest fix is a disk check. Don't skip this — it's the only tool that rebuilds the security stream from the Master File Table (MFT).

1. Open Command Prompt as Administrator. Press Windows key, type cmd, right-click Command Prompt, choose Run as administrator.
2. Type chkdsk C: /f /r and press Enter. Replace C: with your actual drive letter.
3. You'll see a message: "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?" Type Y and press Enter.
4. Restart your computer. Windows will run CHKDSK before the OS loads. This takes 20 minutes to 2 hours depending on drive size. Let it finish — don't interrupt it by holding the power button.
5. After the scan, Windows boots normally. Check if the error is gone by trying the file or folder that caused it.

If CHKDSK found and fixed corruption, you're done. If it reported "Windows has checked the file system and found no problems" but the error still appears, move to Cause #2.

Cause #2: Registry Key Blocking Security Stream Access

Sometimes a misconfigured registry key tells Windows to ignore or block the security stream for a volume. This is rare, but I've seen it after failed antivirus installations or manual registry tweaks gone wrong. The key is HKLM\SYSTEM\CurrentControlSet\Services\Ntfs\Parameters. There's a value called DisableSecurityStream that should not exist on client Windows (Windows 10/11 Home or Pro). Servers sometimes use it for performance, but on desktops it causes exactly this error.

1. Press Windows + R, type regedit, press Enter.
2. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ntfs\Parameters
3. In the right pane, look for a value named DisableSecurityStream. If it's there, right-click it and choose Delete. Confirm Yes.
4. Close Registry Editor and restart the computer.

After rebooting, try the file or app again. If the registry key wasn't there, move to Cause #3.

Cause #3: Bad Disk Sectors on the Volume

If neither CHKDSK nor the registry fix worked, you likely have physical bad sectors on the drive. The security stream data sits in a specific area of the disk. When that spot goes bad, Windows can't read it. This is less common on SSDs (they re-map bad blocks internally), but on old HDDs it's a real problem.

You'll need to run a deeper scan with chkdsk /f /r again, but this time pay attention to the output:

1. Open Command Prompt as Administrator again.
2. Type chkdsk C: /f /r (replace C: with your drive).
3. Let it run. When it finishes, look for lines like "Windows replaced bad clusters" or "Attribute record of type $SECURITY_DESCRIPTOR ... is crosslinked". That confirms bad sectors.
4. If CHKDSK reports bad clusters, you have two options:
   • Option A: If it's an HDD and still under warranty, back up your data immediately and replace the drive. Bad sectors spread.
   • Option B: If it's an SSD, run wmic diskdrive get status in Command Prompt. If it says OK, you're likely fine, but run the manufacturer's diagnostic tool (Samsung Magician, Crucial Storage Executive, or Western Digital Dashboard) to be sure.

After fixing or replacing the drive, the 0xC00001A0 error stops.

Quick-Reference Summary Table

That's it. Those three causes cover 99% of 0xC00001A0 cases I've fixed in 12 years of help desk work. Start with CHKDSK — it's free and fixes most issues. If you're still stuck after all three, the drive is failing and needs swapping.