Windows Stuck on "Repairing Disk Errors": Wait or Power Off?
You turn on your laptop or PC and instead of the login screen you get: “Repairing disk errors. This might take over an hour to complete.” Sometimes there’s a percentage, sometimes just a spinner. An hour later it’s still there. Should you keep waiting, or pull the plug? The answer to “repairing disk errors” depends on one thing: whether the drive underneath is healthy.
What “Repairing disk errors” actually is
This screen is Windows running CHKDSK automatically at boot. NTFS volumes carry a flag called the dirty bit. Windows sets it when it detects a file-system problem, or when the volume wasn’t shut down cleanly (a power cut, a forced shutdown, a crash, or a drive that dropped out during a write). At the next startup, Windows sees the flag and runs a check on the volume before loading.
On a healthy drive, this is routine. CHKDSK fixes inconsistencies in the file system’s records, clears the flag, and Windows boots. It can take a while on a large, full hard drive, but it finishes.
On a failing drive, it’s a different story. CHKDSK keeps hitting sectors it can’t read, retries them, and moves slowly or not at all. Meanwhile it’s actively rewriting file-system structures based on what it can read. That’s how a recoverable drive turns into a much harder recovery.
When to wait
Give it time if:
- The percentage is moving, even slowly.
- The drive is an SSD, or a hard drive that has never shown problems before.
- The check followed an obvious cause, like a power outage or a forced shutdown.
- The computer is quiet, with no clicking or grinding.
On a large hard drive, a few hours with steady progress is normal. Leave it plugged in (laptops on AC power) and let it finish.
When to power off
Hold the power button to shut down if:
- The percentage has been stuck at the same number for several hours.
- The drive is clicking, grinding, or repeatedly spinning up and down. See hard drive clicking: what to do.
- The check runs again on every boot and never finishes.
- The laptop had been slow, freezing, or showing file errors before this started.
Forcing a shutdown in the middle of CHKDSK isn’t risk-free: it can leave the file system half-repaired. But on a drive that’s failing, letting CHKDSK grind through bad sectors for hours is the bigger risk. If your files matter, the data is worth more than the repair.
Step 1: Check the drive’s health
Before letting any repair run again, find out if the drive is failing. The most reliable way when Windows won’t boot is to connect the drive to another computer:
- Laptop 2.5” SATA drive: remove it and use a USB-to-SATA adapter or enclosure.
- M.2 SSD: use an M.2 USB enclosure that matches the drive type (SATA or NVMe).
Plug it into a working Windows PC and check SMART with CrystalDiskInfo or a similar tool. Be careful: the other computer may try to run its own disk check or prompt you to scan the drive. Decline the scan.
- Good with zero pending and reallocated sectors → the drive is probably fine. Copy your files off, then let the check run.
- Caution or Bad, or a nonzero Current Pending Sector Count → stop. Don’t let CHKDSK run on this drive again. Go to Step 3.
If you can’t remove the drive (many thin laptops have soldered storage), skip to Step 2.
Step 2: Use the Windows Recovery Environment
The Windows Recovery Environment (WinRE) lets you reach a command prompt without booting the installed Windows, so the automatic check doesn’t run.
- Boot from a Windows installation USB (create one with Microsoft’s Media Creation Tool on another PC), then choose Repair your computer. Windows also enters recovery on its own after several failed boots.
- Go to Troubleshoot > Advanced options > Command Prompt.
- Drive letters can be different in WinRE. Find your Windows volume with:
diskpart
list volume
exit- If the drive is healthy enough to read, copy your critical files to a USB drive (here,
D:is the Windows volume andE:is the USB drive; adjust for yours):
robocopy "D:\Users\YourName\Documents" "E:\Backup\Documents" /E /R:1 /W:1The /R:1 /W:1 switches keep robocopy from retrying unreadable files over and over. Don’t run chkdsk /r from here on a drive you haven’t confirmed is healthy.
Step 3: Skipping the automatic check
If Windows reaches the desktop, you can check the dirty bit and stop the boot-time check from an administrator Command Prompt:
fsutil dirty query C:
chkntfs /x C:chkntfs /x C: excludes drive C: from the automatic check at the next boot. Run it from the installed Windows, not from WinRE, because WinRE has its own separate settings. This doesn’t fix anything. It buys you a boot so you can copy files off. Restore the default later with chkntfs /d.
Step 4: Image first, repair second
If the drive is failing, the safest path is to clone or image it with tools designed for weak media, which read the healthy areas first and come back to bad sectors last. Then repair or recover from the copy, never the original. Once your data is safe, you can let CHKDSK run, reinstall Windows, or replace the drive.
On a healthy drive with your data backed up, let the check run, or run chkdsk C: /f yourself and let it finish.
The bottom line
“Repairing disk errors” is CHKDSK running at boot because the volume was flagged as dirty. If progress is moving and the drive is healthy, wait. If it’s stuck at the same percentage for hours, the drive is making noise, or the check repeats every boot, power off. Check SMART, copy your files or image the drive, and only then let a repair run. If it keeps coming back, review the hard drive failure warning signs.
If your laptop won’t get past this screen and the files on it matter, our laptop data recovery service recovers data from failing laptop drives for one flat $1,200 price for a single device. Shipping is free and prepaid, and you pay nothing unless we recover your data.