Use CHKDSK /scan before scheduling a Windows 11 disk repair

CHKDSK can find file-system inconsistencies, but aggressive switches pasted into a forum reply may require downtime and stress a failing disk. On NTFS, Microsoft documents `/scan` as an online scan and `/spotfix` as a way to repair queued defects offline. Running a read-style assessment first gives you evidence and a backup opportunity. It also avoids treating a file-system result as proof of physical drive health.

Before you start​

Back up important files to a separate destination. Note which volume is affected, whether the PC shows storage-health warnings and whether the drive is an SSD or HDD. Use a healthy power source. If the drive is clicking, repeatedly disappearing or reporting critical health, prioritize data extraction and hardware replacement before lengthy repair scans.

Do it step by step​

1. Open Terminal as administrator and identify the exact letter of the local NTFS volume. In File Explorer and Disk Management, confirm that the drive letter matches the data you intend to check.
2. Run `chkdsk C: /scan` for the system volume, or replace C: with the target NTFS letter. Allow the online scan to finish and save the full output, including whether corruption was found and queued for repair.
3. If the scan is clean, do not run every repair switch by habit. Investigate application errors, permissions or hardware health separately. If the scan reports defects requiring repair, plan downtime and confirm the backup first.
4. For queued NTFS defects, use Microsoft's `/spotfix` guidance for the identified volume; the system drive may schedule repair at restart. Read the prompt before agreeing and let the process complete. Do not power off because progress appears slow.
5. After restart, rerun an appropriate check and test the specific file operation that failed. Compare the reported error count and whether a warning recurs.
6. If errors recur quickly, check the disk vendor's diagnostics and arrange replacement rather than repeatedly patching the file system. Preserve the first scan and repair outputs for warranty or support.

Check the result​

A follow-up scan no longer reports the original file-system defect and the failing operation succeeds. The independent backup and hardware-health status remain documented.

If something goes wrong​

CHKDSK applies to local disks; a redirected network drive is not a valid target. If the partition appears RAW or cannot be mounted, do not initialize or format it merely to make CHKDSK run. Recovery and disk-health decisions come first.

Know the limit​

`/scan` and `/spotfix` have NTFS-specific behavior. A repaired file-system structure does not restore every corrupted file and does not prove an SSD or HDD is physically sound. Microsoft discourages interrupting the tool. Microsoft CHKDSK command reference

Decision checkpoint​

Keep the exact CHKDSK output rather than summarizing it as 'disk repaired.' A clean file-system scan with continued read errors points away from a simple metadata issue. Conversely, a queued repair is not evidence that every user file has survived intact; open representative files after the repair.