File System Integrity Check Failed

Fix "File System Integrity Check Failed" on Windows 10/11

Stop panicking. This error usually means your drive's file system got corrupted. Here's how to fix it, starting with quick steps.

Wait 30 seconds before you do anything

I know this error is infuriating. It pops up when Windows boots, usually after a crash or power loss. I've seen it a lot on systems with SSDs that are nearly full, or after a bad Windows update. But don't start deleting files yet.

First, restart your computer. Just a normal restart. Sometimes the error is a fluke from a temporary glitch. If it goes away, you're done. If it comes back (and it probably will), move on.

Quick fix: Run the built-in repair tool (5 minutes)

Windows has a tool called CHKDSK that checks the file system for errors. It's the same tool the system uses when you see that blue screen. Let me show you how to run it right.

  1. Press Windows Key + X, then click Command Prompt (Admin) or Windows Terminal (Admin). Yes, you need admin rights.
  2. Type this command and press Enter:
    chkdsk C: /f
    Replace C: with the drive letter that's having the error. (Mine is D: in the screenshot you showed.)
  3. If it says the drive is in use, type Y and restart. Let it run before Windows loads.

CHKDSK will scan the drive and fix any problems it finds. This can take a few minutes on a small SSD, or up to an hour on a big hard drive. Don't interrupt it.

If CHKDSK finds and fixes errors, you're probably good. Reboot and check if the error is gone. If not, or if CHKDSK says it can't fix something, try the next step.

Medium fix: Use System File Checker to repair system files (10 minutes)

The error might not be on your data drive. Sometimes it's a system file that's messed up. That's where SFC helps.

  1. Open Command Prompt as admin again (same as above).
  2. Run this command:
    sfc /scannow
  3. Wait. It'll scan all protected system files and replace bad ones. This takes 5-15 minutes.

If SFC finds corrupted files but can't fix them, run DISM first. DISM fixes the system image that SFC uses. Type:

DISM /Online /Cleanup-Image /RestoreHealth
Then run sfc /scannow again.

Restart after that. I've seen this fix the error on Windows 10 version 22H2 and Windows 11 23H2.

Advanced fix: Repair the master file table (15+ minutes)

If the error still shows up, the file system itself is probably damaged. This happens often on external drives or when you shut down while files are open.

You need to run CHKDSK with extra options. This will fix the Master File Table (MFT) and other system structures.

  1. Boot from a Windows installation USB or recovery drive. You can make one using the Media Creation Tool from Microsoft. This is the only way to repair a drive that Windows won't let you touch while it's running.
  2. At the setup screen, click Repair your computer (bottom left).
  3. Go to Troubleshoot > Advanced options > Command Prompt.
  4. Now run this powerful command:
    chkdsk D: /f /r /x
    Replace D: with your drive letter. The /r flag finds bad sectors and recovers readable data. The /x forces the drive to dismount first.

This can take hours on a large drive. Let it run overnight if needed. When it finishes, reboot and check. This has saved drives that looked dead to me.

If nothing works: Check drive health

Sometimes the error means your drive is dying. Download the manufacturer's diagnostic tool (like SeaTools for Seagate, WD Dashboard for Western Digital) and run a short test. If it fails, back up your data now. Replace the drive.

I've seen this error on a 1TB Samsung 860 EVO SSD with 95% health. The fix was replacing it. Don't wait too long.

One last tip: Run chkdsk with the /scan option on modern SSDs. It's faster and doesn't mark bad sectors that aren't really bad. Old advice says use /f always, but on NVMe drives, /scan is gentler.

You got this. Start with the restart, then CHKDSK, then SFC. Most people stop at the first or second step. If you're reading this far, you're probably dealing with a stubborn one. Be patient — it'll work.

Related Errors in Hardware – Hard Drives
0X8010001A SCARD_E_READER_UNSUPPORTED (0X8010001A) fix for smart card readers 0X8011081F COMADMIN_E_BASEPARTITION_REQUIRED_IN_SET (0X8011081F) Fix 0XC0000304 STATUS_MFT_TOO_FRAGMENTED (0xC0000304) Fix: MFT Too Fragmented 0x8007045D (often accompanies this) Fix 'File System Journaling Recovery Failure' on Windows 10/11

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.