Command Prompt Fix Bad Sectors: What Works and What Doesn't

Use Command Prompt’s CHKDSK /f /r only for file-system errors and weak sectors; if it reports unreadable sectors or the drive keeps reappearing with bad blocks, stop and clone it instead. Back up important files first, because repair attempts can stress a failing drive. This guide shows what CHKDSK can actually fix and when cloning is the safer move.

What bad sectors mean in Windows

Bad sectors are disk areas that cannot reliably store or read data. In Windows, they can lead to crashes, freezes, corrupted files, missing folders, or a drive that hangs during reads.

Windows may show slow opens, copy errors, missing folders, or a drive that hangs during reads. By the time the warning appears, files may already be damaged.

Logical bad sectors versus physical bad sectors

Some problems come from file-system corruption and may be repaired by Windows. Other problems come from actual damage to the storage medium and cannot be truly fixed by software. In those cases, CHKDSK can only mark areas bad so Windows stops using them.

• Logical: file-system corruption, interrupted writes, or bad mappings.
• Physical: damaged HDD platter areas or worn SSD flash cells.
• Result: CHKDSK may help with file-system errors, but repeated new bad blocks usually mean the drive is failing.

Can Command Prompt fix bad sectors?

Command Prompt can help only when the problem is logical or the disk has weak spots that can be isolated. CHKDSK /f is used to repair file-system errors, and CHKDSK /r is used to scan the surface, try to recover readable data, and mark unreadable clusters so Windows can avoid them. It does not restore physically damaged media. (Microsoft Learn)

What CHKDSK /f checks and repairs

Run cmd as administrator, then use chkdsk C: /f for file-system repair on the system volume. The /f switch is used to fix directory and allocation errors. On a non-system drive, Windows can usually run it right away; on C:, it often asks for a reboot.

What CHKDSK /r does during a surface scan

chkdsk C: /r does everything /f does, then checks each readable area for bad sectors. If data can be read, it is moved. If not, the sector is marked unusable. That is why /r can help preserve usable files, but it is not a cure for a failing drive.

When CHKDSK only marks a sector instead of repairing it

If a block cannot be read back reliably, CHKDSK cannot rebuild the damaged area. It marks the area bad and moves on. That may stop fresh errors for a while, but repeated new bad blocks mean the drive is losing health, not improving.

What command checks bad sectors on a hard drive?

The main Windows command-line check is CHKDSK, usually with /f or /r. For a quick file-system pass, use chkdsk X: /f. For a full surface scan that looks for bad sectors, use chkdsk X: /r. Replace X with the drive letter.

1. Open Start, type cmd, then choose Run as administrator.
2. Back up important files first.
3. Run chkdsk D: /r for a data drive, or chkdsk C: /f /r for the system drive.
4. Read the result for bad sectors, unreadable clusters, or file recovery messages.

Administrator privileges are often required when the target is the system drive. If Windows asks to schedule the scan for the next restart, accept it and reboot.

What causes bad sectors most often?

Most often, they come from file-system corruption after power loss, forced shutdowns, or interrupted writes. Less commonly, they come from failing HDD platters, worn SSD flash cells, bad cables, flaky USB enclosures, or unstable power on external drives. The cause matters because the fix changes with it.

File system corruption and interrupted writes

1. Open Command Prompt as administrator.
2. Run chkdsk X: /f first if the drive still reads normally.
3. If errors return, run chkdsk X: /r once.
4. Copy critical data off the drive after the scan completes.

Failing HDD platters or SSD flash wear

1. Use File Explorer or Robocopy to copy important files to another drive as soon as possible.
2. If CHKDSK reports new unreadable clusters or bad sectors, treat that as a sign the drive is degrading.
3. Do not keep rerunning repair passes if the number of bad areas grows.
4. Plan to replace the drive if the errors continue.

External drive cable, enclosure, or power issues

1. Try a different USB cable and port.
2. Connect the drive directly instead of through a hub.
3. Open Device Manager > Disk drives and confirm the device stays stable.
4. Then run chkdsk X: /r only once, after backup.

How do I repair logical bad sectors in Windows 10?

Back up first, then run CHKDSK from an administrator Command Prompt, starting with /f and moving to /r if needed. If CHKDSK finds file-system damage only and the drive stays stable, one repair pass may be enough.

1. Open cmd as administrator.
2. Run chkdsk C: /f or chkdsk D: /f.
3. If Windows reports bad sectors or unreadable clusters, run chkdsk X: /r once.
4. Review the log in Event Viewer > Windows Logs > Application if needed.
5. Copy off anything important immediately after the scan.

Do not keep rerunning full-disk scans on a drive that is already getting worse. One clean pass is useful. Repeated passes on a failing disk can add stress without adding much recovery value.

When should I stop trying to fix the drive?

Stop when CHKDSK keeps finding new bad sectors, or when the drive starts becoming less reliable during copies or scans. That is the point where repair becomes triage. Clone first if the data matters. Replace the drive if cloning becomes unstable or incomplete.

Decision table for the next action

For Windows troubleshooting, the practical next step is to copy your files off the drive and stop using it for important data if the errors continue.

Surface Test and SMART testing

If you need to confirm where errors appear, use standard Windows tools such as CHKDSK and File Explorer copy tests. A surface scan is already covered by chkdsk X: /r, which can check the drive and mark unreadable areas so Windows avoids them. It is for identification, not repair.

Third-party Linux commands such as fixhdd.py, hdparm, or paths like /dev/sda are not needed for a standard Windows repair path.

Does bad sector repair work on SSDs too?

Only partly. On SSDs, bad-sector repair usually means the controller remaps weak flash blocks or Windows marks unreadable areas so they are avoided. Command Prompt cannot repair worn-out NAND. If an SSD keeps showing new media errors, back up the data and replace the drive.

SSD versus HDD versus external drive

1. HDD: one CHKDSK /r pass can be useful; repeated new sectors mean the disk is failing.
2. SSD: treat new media errors as replacement warning signs, not a repair target.
3. External: check cable and enclosure first, then run CHKDSK once.

Prevention: keep a current backup before any surface scan. That matters more than the repair command when a drive is already throwing errors.

Frequently asked questions

Can bad sectors be fixed with Command Prompt?

Only logical bad sectors are candidates for repair. Use chkdsk X: /f for file-system damage and chkdsk X: /r for a surface scan. Physical damage is not fixed by Windows commands, so a drive that keeps reporting unreadable blocks should be cloned or replaced.

What is the difference between logical and physical bad sectors?

Logical bad sectors come from software-related problems and file-system corruption. Physical bad sectors come from actual damage to the storage medium. That difference decides the next step: CHKDSK may help the first case, while the second case usually means backup and replacement.

Is CHKDSK /f /r safe to run on a failing drive?

It is safer after a backup, not before one. On a failing drive, CHKDSK can stress the disk while reading every sector. If the drive already has worsening errors, clone it first and avoid extra full scans.

How long does a bad sector scan take?

It depends on drive size, connection speed, and how many unreadable areas exist. A full CHKDSK /r pass can take a long time, especially on large or slow drives. External drives and drives with many retries usually take the longest.

Can bad sectors cause corrupted files and freezing?

Yes. Bad sectors can cause corrupted and unusable files, plus crashes, freezes, and unexpected shutdowns. If Windows starts hanging during copies or boots with read errors, treat that as a data-warning event and copy off important files before doing another repair pass.

Why does Windows keep finding new bad sectors after chkdsk?

Because the drive is still degrading. CHKDSK can mark a bad area, but it cannot stop new physical damage or worn flash from spreading. If new sectors keep appearing, back up immediately, clone if possible, and replace the drive instead of repeating scans.