sodcalculator

10 Tech How-To

Chkdsk Stuck in Stage 4? Fixes for Windows 11

Guide 10-52409 · Updated · Step by step

If chkdsk stays stuck in Stage 4 on Windows 11, the most reliable fix is to wait 1–2 hours for it to finish, then force-restart if it still hasn’t moved; afterward, run a targeted repair with sfc /scannow and DISM to address the underlying corruption that caused the hang. This article explains why Stage 4 stalls, how to tell if it’s truly frozen, and step-by-step recovery methods without losing data.

What Stage 4 Actually Does

CHKDSK (Check Disk) verifies the file system on your drive. It runs in five stages:

  • Stage 1: Scans file records in the master file table (MFT).
  • Stage 2: Checks index entries for each directory.
  • Stage 3: Validates file security descriptors.
  • Stage 4: Verifies that all file data clusters are correctly referenced.
  • Stage 5: Checks free space and marks bad clusters.

Stage 4 is the most I/O-intensive step because it reads every cluster of every file on the volume. On a large, heavily fragmented, or failing drive, that can take hours. Windows 11 doesn’t show a progress percentage during this stage—only the stage number and the drive letter—so it’s easy to mistake a slow scan for a freeze.

Why It Gets Stuck (and What “Stuck” Really Means)

Most “stuck” reports are actually slow progress. A 1 TB hard drive with 500 GB of data can take 4–6 hours for a full chkdsk. SSDs are faster, but if the drive is nearly full or has many small files, Stage 4 can still crawl. A true freeze happens when the scan hasn’t advanced for 2+ hours with no disk activity (check the HDD/SSD LED on your PC case or listen for clicking). Common causes include:

  • Bad sectors that force repeated read retries.
  • Firmware bugs on certain SSD models.
  • Corrupted system files that confuse the scan.
  • Third-party antivirus or disk encryption software interfering.
  • Failing drive hardware (mechanical or electrical).

If you’re on a laptop, also check that it’s plugged in—CHKDSK will pause if the battery is low, and a shutdown mid-scan can cause more corruption.

How to Safely Interrupt a Stalled Scan

If you’ve waited more than two hours and the percentage hasn’t moved (or the drive light is off), you can force a restart. Press and hold the power button for 10 seconds. On the next boot, Windows will offer to continue or skip the scan—choose Skip to get to the desktop. Then run these commands from an elevated Command Prompt (right-click Start → Terminal (Admin)):

  1. sfc /scannow — repairs corrupted system files.
  2. DISM /Online /Cleanup-Image /RestoreHealth — fixes the Windows image that sfc relies on.
  3. Restart and run chkdsk C: /f /r again, but this time with the /x flag to force-dismount the volume first.

If the scan still hangs, run chkdsk C: /scan (online mode) instead—it’s faster and doesn’t require a reboot.

Preventive Steps Before You Run CHKDSK Again

Before retrying, reduce the load on the drive:

  • Disable third-party antivirus temporarily (Windows Defender is fine).
  • Unplug external drives and memory cards—they can confuse the scan.
  • Close all open programs and disable startup apps.
  • Run chkdsk C: /f (without /r) first—it only fixes file system errors and is much faster. Only add /r if you suspect bad sectors.

Also, check your drive’s health with wmic diskdrive get status in Command Prompt. If it returns “Predictive Failure,” back up your data immediately—CHKDSK won’t fix a dying drive.

When to Skip CHKDSK Altogether

If CHKDSK repeatedly stalls at Stage 4, the drive may be beyond software repair. In that case:

  • Boot from a Windows 11 USB installer and choose Repair your computer → Troubleshoot → Command Prompt, then run chkdsk C: /f from there.
  • Use sfc /scannow and DISM as above—they often resolve the underlying corruption that makes CHKDSK hang.
  • If the drive still fails, replace it. For SSDs, update the firmware from the manufacturer’s site (without naming brands, note that most major SSD makers provide a firmware tool).

For data recovery, stop using the drive immediately and use a Linux live USB with ddrescue to clone it—this is more reliable than CHKDSK on failing hardware.

Frequently Asked Questions

How long should I wait before assuming CHKDSK is stuck?

Wait at least 2 hours with no progress. If the drive light is blinking, it’s working. On a 2 TB HDD, Stage 4 can legitimately take 6+ hours.

Will interrupting CHKDSK damage my files?

It can, but a forced restart is safer than letting a hung scan run indefinitely. Windows will usually resume or skip the scan on reboot. Always back up important data before running CHKDSK.

Why does CHKDSK run at boot and then get stuck?

It’s scheduled to run at boot if the drive has file system errors. If it hangs, use the steps above to skip it and run a targeted repair from Windows.

Can I run CHKDSK on an SSD?

Yes, but avoid /r on SSDs—it causes unnecessary wear. Use /f for file system errors, and rely on the SSD’s own TRIM and SMART health monitoring instead.

What’s the difference between /f and /r?

/f fixes file system errors; /r also scans for bad sectors and attempts recovery. /r includes /f and is much slower.

Does CHKDSK fix bad sectors?

It marks them as unusable and recovers readable data, but it doesn’t repair physical damage. If you have bad sectors, back up and replace the drive.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →