Windows reports errors or chkdsk fails to start? The most common immediate cause is permissions or the disk being in use — but many different issues can make CHKDSK doesn’t work in Windows 10. This article explains the typical causes and shows clear, step‑by‑step fixes so you can run CHKDSK successfully or use alternatives when it can’t fix the problem.
You’ll learn why CHKDSK can fail (permissions, encryption, hardware faults, stuck scans, wrong syntax, etc.), how to run it correctly (including from WinRE), and what to do if the disk is physically failing or the file system is too damaged for CHKDSK to repair.
Key Takeaway
Run CHKDSK from an elevated Command Prompt or WinRE when the volume is locked, unlock or decrypt encrypted volumes first, repair corrupted system files with SFC/DISM if CHKDSK won’t run, and treat hardware errors with manufacturer diagnostics — CHKDSK is a logical repair tool, not a hardware fixer.
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| 1. Not running with administrator privileges | Right‑click Command Prompt and choose Run as administrator, then run chkdsk C: /f /r. |
| 2. Volume is in use (locked by Windows) | Schedule CHKDSK at next boot or run it from Windows Recovery Environment (WinRE). |
| 3. BitLocker or drive encryption | Unlock the drive in Control Panel > BitLocker Drive Encryption or use manage-bde before running CHKDSK. |
| 4. Drive shows as RAW / unsupported file system | Try data recovery tools (e.g., TestDisk) or convert/restore from backup — CHKDSK cannot run on RAW. |
| 5. Severe file system corruption CHKDSK can’t fix | Use SFC/DISM, restore from backup, or run professional recovery tools. |
| 6. Physical disk failure or bad sectors | Run manufacturer diagnostics (SeaTools/Samsung Magician) and replace the drive if SMART fails. |
| 7. Third‑party software locking the disk | Temporarily disable/uninstall disk utilities and antivirus, or perform a clean boot. |
| 8. Incorrect CHKDSK syntax or options | Use correct command: chkdsk X: /f /r /x (replace X: with the drive letter). |
| 9. Corrupted system files or missing CHKDSK binary | Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files. |
| 10. Storage controller or driver problems (RAID/Intel RST) | Update or roll back storage drivers in Device Manager or run CHKDSK from WinPE matching the driver environment. |
| 11. CHKDSK appears hung or very slow | Check progress in Event Viewer & let it run; boot to WinRE if genuinely stuck and re-run with /f /r. |
Detailed Fixes for “CHKDSK doesn’t work in Windows 10”
1. Not running with administrator privileges
Explanation
Why it causes the problem: CHKDSK needs elevated privileges to fix disk errors and modify on‑disk structures. Running a regular Command Prompt may let you view information but will not repair.
Step-by-step solution
- Press Start, type cmd, right‑click Command Prompt, and select Run as administrator.
- In the elevated prompt type: chkdsk C: /f /r (replace C: with the drive letter).
- /f fixes errors, /r locates bad sectors and recovers readable information (implies /f).
- If prompted to schedule at next restart, type Y and reboot.
Notes/tips
- Always run CHKDSK as admin; if an unprivileged user runs it from File Explorer > Properties > Tools, it may just offer a scan or fail to fix errors.
2. Volume is in use (locked by Windows)
Explanation
Why it causes the problem: Windows locks the system volume while it’s running; CHKDSK cannot lock the drive to repair it live. The OS will schedule repairs at boot or you must run from an offline environment.
Step-by-step solution
Option A — Schedule at boot:
- Open elevated Command Prompt.
- Run chkdsk C: /f. If Windows replies that the volume is in use and asks to schedule at next restart, type Y and reboot.
Option B — Use WinRE:
- Open Settings > Update & Security > Recovery > Advanced startup > Restart now.
- After restart choose Troubleshoot > Advanced options > Command Prompt.
- At the Command Prompt run chkdsk C: /f /r.
Notes/tips
- Use /x to force dismount before checking: chkdsk X: /x /f /r (careful on system volume — use WinRE instead).
3. BitLocker or drive encryption
Explanation
Why it causes the problem: Encrypted volumes are locked; CHKDSK can’t access raw sectors until the volume is unlocked, so it fails or reports the drive as inaccessible.
Step-by-step solution
- Unlock via Control Panel: Control Panel > System and Security > BitLocker Drive Encryption and click Unlock drive.
- Or in elevated Command Prompt use: manage-bde -unlock X: -RecoveryPassword YOUR-48-DIGIT-KEY.
- After the volume is unlocked, run chkdsk X: /f /r.
Notes/tips
- If using BitLocker with TPM, ensure you provide the recovery key if required. If you can’t unlock the drive, recover data before proceeding.
4. Drive shows as RAW or unsupported file system
Explanation
Why it causes the problem: RAW means Windows cannot interpret the file system; CHKDSK operates on NTFS/FAT volumes and will not work on RAW partitions.
Step-by-step solution
- Confirm RAW status: open Disk Management (diskmgmt.msc) and look at the partition type.
- If data is important, use recovery tools like TestDisk, PhotoRec, or commercial recovery software to extract files before attempting fixes.
- After data recovery, reformat the partition to NTFS: right‑click the partition in Disk Management > Format > choose NTFS.
Notes/tips
- Do not reformat before attempting data recovery. CHKDSK on RAW can make recovery harder.
5. Severe file system corruption CHKDSK can’t fix
Explanation
Why it causes the problem: CHKDSK repairs certain logical inconsistencies; if master file table (MFT) or critical metadata is heavily damaged, CHKDSK may fail or report unfixable errors.
Step-by-step solution
- Run system file checks first: open elevated Command Prompt and run sfc /scannow.
- If SFC fails, run DISM /Online /Cleanup-Image /RestoreHealth then rerun sfc /scannow.
- If CHKDSK still fails, use specialized recovery utilities (e.g., TestDisk, Recuva) or restore from backup.
- Consider cloning the drive sector‑by‑sector before further repairs using tools like Clonezilla.
Notes/tips
- When damage is severe, professional recovery services may be necessary; stop attempts that could worsen data loss.
6. Physical disk failure or bad sectors
Explanation
Why it causes the problem: CHKDSK can mark bad sectors but cannot repair hardware; if SMART reports failing attributes, CHKDSK may fail repeatedly.
Step-by-step solution
- Check SMART status: open PowerShell (admin) and run wmic diskdrive get model,status or use third‑party tools like CrystalDiskInfo.
- Download the drive maker’s diagnostic (e.g., SeaTools, WD Data Lifeguard, Samsung Magician) and run full diagnostics.
- If diagnostics show failure, back up data immediately and replace the drive.
Notes/tips
- Disk replacement is the only reliable fix for hardware failure. Use CHKDSK only to salvage readable files before replacement.
7. Third‑party software locking or interfering with the disk
Explanation
Why it causes the problem: Antivirus, disk managers, encryption utilities, or backup software can keep files open and prevent CHKDSK from gaining exclusive access.
Step-by-step solution
- Perform a clean boot: press Win + R, type msconfig, go to Services, check Hide all Microsoft services, click Disable all, then Startup > Open Task Manager and disable startup apps, reboot.
- Temporarily disable real‑time protection: Settings > Update & Security > Windows Security > Virus & threat protection > Manage settings > toggle off Real‑time protection.
- Uninstall or pause third‑party disk utilities, then retry CHKDSK from elevated Command Prompt.
Notes/tips
- Remember to re‑enable security software after the check.
8. Incorrect CHKDSK syntax or options
Explanation
Why it causes the problem: Using wrong parameters or forgetting the drive letter will make CHKDSK do nothing or perform unexpected actions.
Step-by-step solution
- Use the standard repair command: chkdsk X: /f /r /x where X: is the target drive.
- For just a surface scan without fixing, use chkdsk X:.
- To only fix errors without checking for bad sectors, omit /r and use /f.
Notes/tips
- Don’t run /r on very large disks unless you’re prepared for a long run — it checks every sector.
9. Corrupted system files or missing CHKDSK binary
Explanation
Why it causes the problem: If the CHKDSK executable or system libraries are corrupted, CHKDSK can fail to start or crash.
Step-by-step solution
- Run System File Checker: open elevated Command Prompt and run sfc /scannow.
- If SFC reports issues it can’t fix, run DISM /Online /Cleanup-Image /RestoreHealth and then re-run sfc /scannow.
- Reboot and attempt CHKDSK again.
Notes/tips
- If the system is unbootable, run SFC/DISM from WinRE or use a matching Windows installation media.
10. Storage controller or driver problems (RAID, Intel RST)
Explanation
Why it causes the problem: RAID drivers or Intel Rapid Storage Technology (RST) drivers may not be available in WinRE or may interfere with CHKDSK in Windows, making volumes inaccessible.
Step-by-step solution
- Open Device Manager, expand IDE ATA/ATAPI controllers or Storage controllers, right‑click your controller and choose Update driver.
- Download the latest storage driver from the PC or motherboard manufacturer and install it.
- If using RAID or RST, run CHKDSK in the same environment (WinPE) containing the correct drivers, or inject drivers into WinPE before running CHKDSK.
Notes/tips
- For complex RAID arrays, consult vendor docs; running CHKDSK on an array with mismatched drivers can cause additional trouble.
11. CHKDSK appears hung or very slow
Explanation
Why it causes the problem: CHKDSK can take hours on large or noisy drives, and some operations (like scanning for bad sectors) progress slowly; it can look like it’s frozen.
Step-by-step solution
- Be patient: for large drives or many errors, let CHKDSK run overnight.
- Check progress in the console; if CHKDSK was scheduled at boot, view results after boot in Event Viewer > Windows Logs > Application and look for Source: Wininit.
- If truly stuck (no CPU or disk activity for many hours), reboot into WinRE and rerun CHKDSK: chkdsk C: /f /r.
- As a last resort, clone the drive sector‑by‑sector and try repairs on the clone.
Notes/tips
- Avoid interrupting CHKDSK during the phase that modifies disk metadata; aborting can worsen corruption.
Preventive maintenance and alternatives
- Backup regularly: maintain current backups (cloud, external drive, or image backups) to avoid dependence on CHKDSK for recovery.
- Monitor SMART: use tools like CrystalDiskInfo to get early warnings of hardware failure.
- Use manufacturer SSD tools (e.g., Samsung Magician) for firmware updates and health checks — CHKDSK is for logical repairs, not SSD maintenance.
- For advanced recovery, tools like TestDisk (for partition/table repairs) and PhotoRec (file recovery) are more capable than CHKDSK at recovering lost data.
- Consider creating a Windows 10 recovery USB or WinPE boot media with necessary drivers so you can run CHKDSK offline when needed.
FAQ
Can CHKDSK cause data loss?
CHKDSK fixes file system errors and may remove references to irrecoverable files; this can look like data loss. Always back up critical files before running CHKDSK if possible, and consider creating a disk image if the drive is unstable.
How long should CHKDSK take?
It depends on drive size, errors, and options: a quick check can be minutes, a full /r scan on multi‑TB drives can take many hours. Expect longer on drives with many problems.
Can I cancel a running CHKDSK?
If CHKDSK is running in Windows you can press Ctrl+C to attempt to stop it, but if it’s modifying the disk (especially at boot) cancelling can cause further corruption; better to let it finish or reboot only if stuck with no activity.
Is CHKDSK necessary for SSDs?
CHKDSK is useful for logical file system errors on SSDs, but it does not fix wear‑leveling or physical SSD issues — use SSD manufacturer tools for hardware health and firmware updates.
My PC won’t boot and CHKDSK won’t run — what now?
Boot from Windows installation media or WinRE, choose Repair your computer > Troubleshoot > Advanced options > Command Prompt, then run chkdsk C: /f /r. If that fails, consider data recovery from another machine or clone the disk before further repairs.
Conclusion
When CHKDSK doesn’t work in Windows 10, the root cause is usually access (permissions/locking), encryption, severe corruption, or hardware/driver issues — each requires a different approach such as running CHKDSK from WinRE, unlocking BitLocker, repairing system files with SFC/DISM, or using manufacturer diagnostics. Follow the step‑by‑step fixes above, back up important data, and replace failing hardware when diagnostics indicate physical damage.
