How to Run Check Disk on Windows (And What It Actually Does)

Check Disk — known by its command-line name chkdsk — is a built-in Windows utility that scans your hard drive or SSD for file system errors, bad sectors, and structural problems that can cause data loss, crashes, or slow performance. It's been part of Windows for decades, and knowing how to use it correctly can mean the difference between catching a disk issue early and losing files without warning.

What Check Disk Actually Does

When you run chkdsk, it performs one or more of the following tasks depending on the options you choose:

• Scans the file system for logical errors — inconsistencies in how files and folders are recorded in the file allocation table or NTFS metadata
• Checks for bad sectors — physical or logical areas of the disk that can no longer reliably store data
• Attempts repairs — if run with repair flags, it tries to fix logical errors and mark bad sectors so the OS avoids writing to them

It's worth understanding the distinction between a read-only scan (default behavior) and an active repair run. Running chkdsk without any flags simply reports problems. Fixing them requires additional parameters.

How to Run Check Disk Using File Explorer 🖥️

The simplest method for most users requires no command line at all.

1. Open File Explorer and navigate to This PC
2. Right-click the drive you want to check (usually C: for your system drive)
3. Select Properties
4. Go to the Tools tab
5. Under "Error checking," click Check
6. Windows will either report no errors found or offer to scan and repair

This method is sufficient for routine maintenance checks on non-system drives. For the system drive (C:), Windows will often schedule the scan to run on the next restart, since it can't fully check a drive that's actively in use.

How to Run Check Disk from the Command Prompt

The command-line version gives you more control and is often necessary for deeper scans or scripted maintenance.

Open Command Prompt as Administrator:

• Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator

Basic syntax:

chkdsk [drive letter]: [options] 

Common commands and what they do:

The /r flag is the most thorough option but also the slowest — on a large HDD it can take several hours. On SSDs, bad sector scanning works differently because NAND flash doesn't degrade the same way spinning disks do, so /r is less meaningful but still valid for file system repairs.

Running Check Disk on a Locked System Drive

If your PC is having serious problems — won't boot properly, crashes frequently — you may need to run chkdsk from the Windows Recovery Environment (WinRE).

1. Boot from a Windows installation drive or access recovery options from Settings → Update & Security → Recovery
2. Choose Troubleshoot → Advanced Options → Command Prompt
3. Identify your system drive letter (it may not be C: in the recovery environment — use dir to check)
4. Run chkdsk C: /f /r

This approach bypasses the lock that normally prevents scanning an active system partition. 🔧

How Long Does Check Disk Take?

This varies significantly based on:

• Drive type — HDDs take much longer than SSDs due to mechanical read speeds
• Drive size — a 4TB HDD can take 4–8 hours under /r; a 500GB SSD might finish in minutes
• Number of errors found — more problems means more time spent attempting repairs
• Scan type — a read-only chkdsk C: scan is faster than a full /r scan

A scan that appears frozen isn't necessarily stuck — percentage progress on large HDDs can stall for extended periods, especially when working through bad sectors.

What the Results Mean

After a scan, chkdsk outputs a summary. Key things to look for:

• "Windows has scanned the file system and found no problems" — no action needed
• Errors found but not fixed — you ran without /f; re-run with repair flags
• Bad sectors reported — some bad sectors on an HDD are normal over time, but a rapidly increasing count is a warning sign of imminent drive failure
• "The disk does not have enough space to replace bad clusters" — the drive is in serious trouble

If chkdsk repeatedly finds errors on the same drive — especially bad sectors — that's not a software problem. That's the drive telling you it's wearing out.

Factors That Change What You Should Do Next

How you interpret and respond to chkdsk results depends heavily on variables specific to your situation:

• Drive age and type — a 7-year-old HDD reporting bad sectors is a different situation than a 1-year-old SSD showing file system errors
• What the drive contains — a boot drive with your OS behaves differently and carries higher stakes than a secondary storage drive
• Whether errors are recurring — a one-time fix after a power outage is different from errors appearing on every scan
• Your Windows version — Windows 10 and 11 handle NTFS online scanning differently than older versions, affecting which flags are most appropriate
• Whether SMART data corroborates the findings — chkdsk doesn't read S.M.A.R.T. health data; cross-referencing with a tool like CrystalDiskInfo gives a fuller picture

The same chkdsk output on two different machines can warrant entirely different responses depending on what's underneath it.