How to Fix File System Errors With CHKDSK in Windows 11, 10, 8, and 7

File system errors in Windows can leave files unreadable, trigger repair prompts, or make a drive disappear. You needed this drive working, so start with the least disruptive CHKDSK check.

Fix #1: Scan the drive through File Explorer

Windows 11 and Windows 10 provide a graphical Error Checking tool. It scans the selected drive and offers a repair option only when it finds errors.

1. Press Windows + E to open File Explorer.
2. Select This PC in the left pane.
3. Right-click the affected drive and select Properties.

4. Open the Tools tab.
5. Select Check under Error checking.

6. Select Scan drive if Windows says, “You don’t need to scan this drive.”

7. Keep the window open while Windows checks the drive.

8. Select Repair drive if Windows finds errors.
9. Follow the restart prompt if Windows needs exclusive access to the drive.

The final dialog should report that Windows scanned the drive successfully or repaired its errors. Select Show Details if you want to inspect the CHKDSK log.

If File Explorer says the drive is healthy but corruption continues, run an online command-line scan next.

Fix #2: Run an online NTFS scan

The /scan option checks an NTFS volume while Windows is running. It doesn’t make repairs, so it’s a sensible command when you’re wary of changing a drive that contains important files.

1. Press Windows + X.
2. Select Terminal (Admin) in Windows 11 or Windows PowerShell (Admin) in Windows 10.
3. Select Yes when User Account Control appears.

4. Enter the following command, replacing C: if the affected drive uses another letter:

chkdsk C: /scan

5. Read the final lines of the result.

You should see either “Windows has scanned the file system and found no problems” or a message explaining that errors require repair. If CHKDSK reports corruption, back up essential files to an external backup drive before continuing.

The /scan switch works with NTFS drives on Windows 8, Windows 10, and Windows 11. Use the standard chkdsk C: read-only command for FAT16 or FAT32 volumes.

Fix #3: Repair logical file system errors

Use /f when CHKDSK finds logical errors in file records, indexes, or other file system structures. This command changes the volume, so confirm that your backup opens before running it.

1. Open Terminal (Admin) or Command Prompt (Admin).
2. Enter this command:

chkdsk C: /f

3. Press Y if you see “Chkdsk cannot run because the volume is in use by another process” and Windows asks to schedule the volume.
4. Restart the computer.
5. Don’t press a key when Windows offers to skip disk checking.

CHKDSK should run before the sign-in screen appears. Windows will then start normally.

On modern NTFS volumes, /spotfix can apply targeted repairs identified during an online scan:

chkdsk C: /spotfix

If the volume is busy, Windows may ask to dismount it or schedule the repair. A second option scans online and queues required fixes for an offline repair:

chkdsk C: /scan /forceofflinefix

Use one repair method. Running every switch back-to-back wastes time and makes the result harder to interpret.

Fix #4: Check for bad sectors

The /r switch locates unreadable sectors and tries to recover readable information. It includes /f, can take several hours, and shouldn’t be your first CHKDSK command.

1. Copy accessible files to another drive.
2. Open Terminal (Admin) or Command Prompt (Admin).
3. Enter the original full repair command:

chkdsk C: /f /r /x

The /x switch dismounts the volume first and includes /f. Close any open files on that drive before approving the dismount.

4. Press Y if CHKDSK asks to schedule the check.
5. Restart Windows.
6. Leave the computer connected to power until the scan finishes.

The percentage can remain unchanged for a long time, especially on a large hard drive with damaged sectors. Don’t force a shutdown unless the computer has clearly stopped responding for an extended period.

CHKDSK also supports /b on NTFS volumes:

chkdsk C: /b

This switch clears the existing bad-cluster list and checks every cluster again. It includes /r and is mainly useful after copying a Windows image onto a different disk. I’d skip it for routine checks.

Repeated /r scans aren’t useful maintenance for an SSD. If an SSD reports new errors after repairs, run the manufacturer’s drive diagnostic and prepare for a replacement SSD.

Fix #5: Run Error Checking in Windows 7 or Windows 8

Windows 7 and Windows 8 are outside Microsoft support, but their built-in disk checker still works. The labels can differ slightly between editions.

1. Open Computer or This PC.
2. Right-click the affected drive.
3. Select Properties.
4. Open the Tools tab.
5. Select Check now… under Error-checking.

6. Select Automatically fix file system errors.
7. Select Scan for and attempt recovery of bad sectors only when you suspect physical disk damage.

8. Select Start.
9. Select Schedule disk check if Windows can’t check the system drive while it’s running.

10. Restart the computer without pressing a key during the scheduled check.

The computer should return to the Windows sign-in screen when CHKDSK finishes. Copy critical files elsewhere if the result mentions bad sectors or unrecoverable errors.

CHKDSK command options

Switch	What it does	When to use it
/f	Repairs logical file system errors	CHKDSK found corruption
/r	Finds bad sectors and recovers readable data; includes /f	Files produce read errors or a hard drive may be damaged
/scan	Runs an online NTFS scan	Initial diagnosis on Windows 8, 10, or 11
/spotfix	Applies targeted NTFS repairs	An online scan identified repairable errors
/forceofflinefix	Sends detected NTFS repairs to an offline check	Online repair can’t finish
/b	Clears and rebuilds the NTFS bad-cluster map; includes /r	A volume was imaged onto another disk
/i	Runs a less thorough NTFS index check	You need a faster check and accept reduced coverage
/c	Skips NTFS folder-structure cycle checks	You need a faster check and accept reduced coverage

Use /i and /c only when scan time matters more than a complete check. They intentionally skip parts of the normal verification.

Check the CHKDSK log

A boot-time scan can disappear before you read its summary. Event Viewer keeps the result.

1. Right-click Start.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select Application.
5. Select Find in the Actions pane.
6. Search for Wininit if CHKDSK ran during startup.
7. Search for Chkdsk if the scan ran inside Windows.
8. Open the matching event and read the General tab.

You should see the checked volume, repair status, and any reported bad sectors. The event number can vary, so searching by source is more dependable than filtering for one event ID.

When CHKDSK doesn’t fix the drive

CHKDSK repairs file system structures, but it can’t repair failing hardware. Back up the drive immediately if bad sectors return, files keep becoming corrupted, or Windows repeatedly schedules checks.

Run the drive manufacturer’s diagnostic next. If Windows can’t read the disk, a USB hard drive enclosure may help you copy files from another computer, but stop if the drive disconnects or makes unusual noises.

Conclusion

Fix #3, running chkdsk C: /f, is the breakthrough that usually clears persistent logical errors after the initial scan identifies them. If the errors return, replace the drive; finally getting a clean CHKDSK result isn’t worth trusting hardware that keeps damaging files.