Bad Sector Repair in Windows 10: What CHKDSK Can and Cannot Fix

A bad-sector warning can refer to unreadable storage or to file-system records marking damaged areas. Windows tools can correct some logical errors and recover readable information, but they cannot physically repair an HDD surface or worn-out flash cells.

Before running a lengthy repair, decide whether your priority is recovering valuable files or testing an expendable drive. Heavy scanning is not the first step for a disk that is already failing.

Recognize when recovery comes before scanning

Stop ordinary use if the drive clicks, disappears, repeatedly times out, or produces increasing read errors. Do not install utilities on that disk or repeatedly attempt a full scan. For irreplaceable data, consider professional recovery; for a stable readable disk, protect the most important files first.

Check the manufacturer's diagnostic information and storage health warnings. A single successful file copy does not establish that every area is healthy. Likewise, a clean file-system report cannot guarantee that the hardware will remain reliable.

Do not wipe a disk, write zeros, or isolate a guessed range in an attempt to save files. Those actions can destroy recoverable content and do not reverse physical deterioration.

Back up readable files from a stable drive

Use Qiling Disk Master only while the source remains readable and stable. This workflow protects selected files; it is not a specialized fault-tolerant imaging procedure for a mechanically failing disk.

• Free Download
• Windows 11/10/8.1/8/7,100% Secure

Step 1. Connect a healthy destination disk and open File backup.

Step 2. Select essential folders directly in the tree control. Prioritize unique documents and photographs rather than expendable downloads.

Step 3. Set the backup destination on the healthy disk, review it, and click Proceed. Inspect the completion details for unreadable or skipped files.

Step 4. Restore representative files into a separate folder and open them. Keep a list of anything that was not recovered before deciding whether further scanning is acceptable.

Check the file system with the appropriate CHKDSK option

For a protected, stable NTFS data volume in Windows 10, open Command Prompt as administrator. In these examples E: is the verified affected volume:

chkdsk E: /scan

This checks NTFS online. If a repair is required, close programs using that volume and arrange an interruption:

chkdsk E: /f

If the system volume cannot be locked, Windows may offer to schedule the check for a restart. Save work and confirm the maintenance time before accepting.

When a full read check is justified after data protection, chkdsk E: /r searches for bad sectors and attempts to recover readable information. It includes file-system repair and can take many hours. It does not restore physically unreadable bytes or make damaged hardware new.

Microsoft explains these distinctions in the CHKDSK reference. If the volume is RAW, do not force this NTFS workflow; investigate recovery first.

Review the result and decide whether to replace the drive

1. Read the completion report. Note whether errors were repaired, whether bad sectors were reported, and whether the operation completed at all.
2. For a scheduled startup check, review the corresponding Windows Application log entry after sign-in.
3. Open files from the backup and compare important folders. A repaired directory does not prove that every file's content is intact.
4. Use the manufacturer's diagnostic result and recurring symptoms to decide on replacement. Do not keep the only copy of important data on a drive with continuing errors.

On SSDs, controller-managed remapping and wear are hardware matters. Repeated full-surface scans or defragmentation are not a cure. After replacing the disk, restore verified files and retain the old device only as needed for any outstanding recovery.

Related Articles

• Check Whether a Hard Drive Is Failing
  Recognize hardware warning signs before attempting logical repairs.
• Writing Zeros and Bad Sectors
  Understand why destructive overwriting is different from recovering files.

Is this information helpful?   Yes   No

This information is not relevant.

This information is not easy to understand.

This information is not deep enough.

What can we do to improve this information? (Optional)

Refresh Please enter the verification code!