Why is chkdsk stuck at 10 or 11 percent?

These percentages have no special meaning — the scan slows wherever it encounters bad sectors or heavy fragmentation, which can cluster anywhere on the disk.

How long should I wait before assuming it's frozen?

Several hours on a large or older mechanical drive is normal for /r. If there's been zero disk activity for that long, it may genuinely be stuck.

Will interrupting chkdsk damage my drive?

It can leave the file system in an inconsistent state requiring another repair pass, but it doesn't typically cause physical damage to the drive itself.

CHKDSK Stuck at a Percentage: Troubleshooting Guide

Download now

CHKDSK scans can look frozen for long stretches, especially during /r's sector-by-sector scan, without actually being stuck. This guide covers how to tell the difference and what to try.

Updated August 9, 2026 · PC Utility Hub Editorial Team

Is it actually stuck?

chkdsk can sit at the same percentage for a long time, particularly at stages involving /r on large or badly fragmented drives, because it's reading every sector. On a large hard drive with many bad sectors, a stall of an hour or more at one percentage is not unusual. Only consider it truly hung if there's zero progress and no disk activity light for several hours.

Check for actual disk activity

Watch the drive's activity LED (on a desktop or external enclosure) or listen for the drive working. If a mechanical hard drive is silent and the light is off for a long period, the scan may genuinely be stuck; if it's still clicking/spinning and the light flickers, it's likely still working through bad sectors.

Common stages where it appears to hang

Stage	Common stall point
Stage 4 (bad sector scan)	Very slow near large clusters of bad sectors
Stage 5 (free space verification, /r only)	Slow on very large or nearly full volumes
10%, 11%, or similar	No special meaning — just wherever the bad sectors are concentrated

If you must interrupt it

1Give the scan several hours before interrupting, especially on large or old drives.
2If you must stop it, hold the power button to force a shutdown.
3On reboot, run chkdsk /f (not /r) first to restore a stable state, then decide whether to retry /r.

Warning: Forcing a shutdown or reboot mid-scan can leave the file system in a worse state than before you started, and may require the scan to restart from the beginning. Only do this as a last resort, and expect to need chkdsk /f again afterward.

Preventing this next time

Run chkdsk /scan periodically (it runs online, without a lengthy offline pass) so problems are caught early.
Keep backups of important data so a failing drive doesn't force a risky recovery scan later.
If a drive consistently has slow, error-heavy chkdsk runs, treat it as failing hardware and replace it rather than repeatedly running /r.

Frequently asked questions

Why is chkdsk stuck at 10 or 11 percent?: These percentages have no special meaning — the scan slows wherever it encounters bad sectors or heavy fragmentation, which can cluster anywhere on the disk.
How long should I wait before assuming it's frozen?: Several hours on a large or older mechanical drive is normal for /r. If there's been zero disk activity for that long, it may genuinely be stuck.
Will interrupting chkdsk damage my drive?: It can leave the file system in an inconsistent state requiring another repair pass, but it doesn't typically cause physical damage to the drive itself.