Chkdsk Found Bad Clusters What Happens to the Files Inside Them

Running chkdsk C: /f /r makes Windows read every cluster of the volume, not just the ones holding files. When a cluster cannot be read, chkdsk records it in a hidden file system list — the bad cluster file — and from that moment Windows will never allocate that cluster again. New data is routed around the damage automatically.

Notice what did not happen: the cluster was not repaired, polished or restored. It was condemned and fenced. The drive's surface is exactly as damaged after the scan as before it; only the map changed.

If a file lived partly inside a bad cluster, chkdsk splits its fate in two:

1. The readable parts are copied to healthy clusters. The file keeps its name and place, and often opens and works — a document may be missing a paragraph, a video may glitch at one point, a program file may simply be broken. The damage is inside the file now, quietly.
2. The unreadable part is gone from that copy. Nothing in Windows can argue it back — the drive itself could not read it.
3. Orphaned fragments — pieces whose file records were lost — are placed in a hidden folder named FOUND.000 as files like FILE0000.CHK. Honest assessment: these are usually unrecoverable shards. Occasionally a fragment is a recognisable document or photo you can rename and salvage, but treat that as luck, not a method.

The full log survives the restart: open Event Viewer → Windows Logs → Application and find the Chkdsk or Wininit entry from the scan. Two things matter in it:

1. The names in the replaced lines — the exact files that lost data. Open each one and check it while you still remember what it should contain.
2. The KB in bad sectors total. Zero means the scan found a clean surface. A small, stable total is fenced history. A total that grows between scans months apart means fresh damage — the drive is still failing, whatever the fence says.

Write the total and the date somewhere. One report is a snapshot; two reports are a diagnosis.

Here is the part that confuses everyone: after chkdsk, Windows may work perfectly while CrystalDiskInfo or Hard Disk Sentinel still shows warnings. Both are telling the truth, about different layers.

Windows is reporting on the file system: the bad ground is fenced, everything is consistent again. The drive's SMART counters are reporting on the hardware: the sectors failed, spares were spent, and that history is permanent. The fence satisfies Windows; it does not rewind the drive's diary. A drive can be fenced and stable for years — or keep failing behind the fence. The counters and repeat chkdsk totals are how you find out which.