To run chkdsk in Windows 11, right-click Start, choose Terminal (Admin), and type chkdsk C: /f to find and fix file system errors, or chkdsk C: /r to also scan for bad sectors. Replace C: with the drive you want to check. If the drive is in use, which is always the case for C:, chkdsk asks to run at the next restart; type Y and restart. For a quick check without the command line, open File Explorer, right-click the drive, choose Properties → Tools → Check.
This guide covers both methods, which switches to use, how to read the results, how to find them after a restart, and the situations where running chkdsk is a bad idea.
What chkdsk does
chkdsk (Check Disk) examines a volume's file system: the tables and indexes that record which files exist and where their data is stored. It finds and fixes problems like lost clusters, cross-linked files and damaged directory entries, typically caused by crashes, power cuts or unplugging a drive mid-write. With the right switch it also reads the disk surface to find bad sectors.
It is not a full health test. chkdsk does not read the drive's SMART data, wear level or temperature. A drive can pass chkdsk and still be failing.
Method 1: Error checking in File Explorer
- Open File Explorer and click This PC.
- Right-click the drive and choose Properties.
- Open the Tools tab and click Check under Error checking.
- Click Scan drive, even if Windows says you do not need to.
This runs an online scan of the file system while you keep working. If it finds problems, it offers to repair them, which may need a restart. It does not scan for bad sectors.
Method 2: Command Prompt or Terminal
- Right-click Start and choose Terminal (Admin). Click Yes at the User Account Control prompt. Without admin rights, chkdsk reports "Access Denied".
- Type the command for what you want to do (see the table below), for example
chkdsk D: /f, and press Enter. - If the drive is in use, chkdsk offers to dismount it (for data drives) or to schedule the check for the next restart (for C:). Type Y.
- For C:, restart the PC. The check runs before Windows loads. Do not switch off the PC while it runs.
chkdsk switches explained
| Command | What it does | When to use it |
|---|---|---|
chkdsk C: | Read-only check, reports problems but fixes nothing | A quick look |
chkdsk C: /scan | Online scan (NTFS) while the drive stays in use | Checking without downtime |
chkdsk C: /f | Fixes file system errors | After a crash or unsafe removal |
chkdsk C: /r | Everything /f does, plus finds bad sectors and recovers readable data | Suspected bad sectors, on a backed-up drive |
chkdsk D: /x | Forces the volume to dismount first; includes /f | Data drives with open files |
chkdsk C: /spotfix | Quickly fixes problems found by an earlier scan (NTFS) | After /scan reports issues |
The difference between /f and /r is time. /f usually finishes in minutes. /r reads every sector, which can take hours on a large hard drive. Our guide to checking a hard drive for bad sectors explains when the longer scan is worth it.
Reading the results
When chkdsk runs in a window, the summary appears at the end. Look for these lines:
- "Windows has scanned the file system and found no problems." All good.
- "Windows has made corrections to the file system." Errors were found and fixed. Run it once more to confirm the volume is now clean.
- "0 KB in bad sectors." No bad sectors found. Any other figure means chkdsk marked damaged areas as unusable.
- "Found.000" folders at the root of the drive contain fragments chkdsk could not reattach to their original files.
Finding the results after a restart
A boot-time check flashes by before Windows loads. To read it afterward:
- Press Win + X and open Event Viewer.
- Go to Windows Logs → Application.
- Click Filter Current Log on the right, type
Wininitin the Event sources box, and click OK. - Open the most recent entry to read the full chkdsk report.
When not to run chkdsk
Do not run chkdsk /r or /f as your first step on a drive that is clicking, disappearing, or showing rising SMART warnings. Repairs change the file system and can remove damaged data, and a long scan puts heavy load on a weak drive. Copy your important files off first.
- Failing hard drives. Back up first. See how to back up a failing hard drive.
- RAW drives. chkdsk cannot check them and will tell you so. Read how to fix a RAW drive without formatting instead.
- Routinely on SSDs. chkdsk is safe on SSDs, but a
/rsurface scan adds little, because SSDs manage bad blocks internally. Use/for/scanfor file system issues.
Common chkdsk problems
chkdsk runs at every startup
The volume is marked "dirty", meaning Windows thinks it needs checking. Run fsutil dirty query C: to see the flag. Letting one full chkdsk C: /f run to completion usually clears it. If it keeps coming back, check the drive's health.
chkdsk is stuck at a percentage
Some stages take much longer than others, and a /r scan slows down at damaged areas. Give it several hours. If it does not move at all for hours, the drive is probably failing; power off, then copy your data off before trying again.
Check the file system and the drive together
chkdsk answers one question: is the file system intact? It does not tell you whether the drive underneath is healthy. Disk Detector checks both. It finds file system errors on NTFS, FAT32 and exFAT partitions, and reads each drive's SMART health so you can see whether errors are a one-off or a sign of a failing disk. Its surface scan is read-only, so you can look for bad sectors without changing anything on the drive, then decide whether to run a repair. Disk Detector explains every result in plain English, so you are not left decoding chkdsk output.
Frequently asked questions
What is the difference between chkdsk /f and /r?
/f fixes file system errors. /r does everything /f does and also reads the whole surface to find bad sectors, so it takes much longer.
Why does chkdsk ask to run at the next restart?
It cannot lock a drive that Windows is using, such as C:. Type Y and restart, and the check runs before Windows loads.
Can chkdsk cause data loss?
It can when it repairs badly damaged structures, because unreadable fragments may be removed or moved to a found folder. Back up important files first.
