Post actualizado el día octubre 17, 2026 by DeiviSanzPlay
Running chkdsk on a Windows PC isn’t some magic fix-all. It’s a low-level disk checker that scans your drive’s file system, finds inconsistencies, and tries to repair them. But what actually happens when you type that command? Spoiler: it depends on the flags you use, and most people run it wrong.
What chkdsk Actually Does Under the Hood
When you execute chkdsk without any parameters, it just reads the disk. It doesn’t fix anything. It checks three things: the file system metadata (NTFS or FAT), file names and directory structure, and the security descriptors. If it finds logical errors, it reports them. That’s it.
To actually repair, you need chkdsk /f (fix errors) or chkdsk /r (locate bad sectors and recover readable info). The /r flag is the heavy one. It scans every sector, which on a 2TB drive can take 4+ hours. And here’s the kicker: if you run chkdsk on a drive in use, Windows will schedule it for the next reboot. That’s why you see that blue screen with a percentage counter before login.
The real purpose of chkdsk isn’t speed. It’s integrity. It’s the difference between a drive that boots and one that throws a «file system is corrupt» error on startup.
Why Most People Run chkdsk for the Wrong Reasons
People run chkdsk when their PC feels slow or a file won’t open. That’s usually not a file system problem. It’s a dying drive, a full disk, or malware. chkdsk won’t fix fragmentation (that’s defrag), and it won’t recover deleted files. It only fixes structural corruption.
If you see «Windows detected a hard disk problem» or «The file or directory is corrupted and unreadable,» that’s when chkdsk /f /r makes sense. Otherwise, you’re just burning hours for nothing. I’ve seen people run chkdsk weekly as «maintenance.» That’s pointless. NTFS is journaling. It doesn’t corrupt itself randomly.
What Happens When chkdsk Finds Bad Sectors
Bad sectors are physical. The magnetic surface of the platter has degraded. chkdsk cannot repair them. What it does is mark them as bad in the file system’s bad cluster list (for NTFS, it’s $BadClus). Then it moves any readable data to good sectors. If the sector is unreadable, that data is gone.
Here’s the nuance: a few bad sectors on an old HDD are normal. A growing number is a death sentence. If chkdsk reports «bad sectors were found and repaired» every time you run it, your drive is failing. Back up immediately. On SSDs, bad sectors work differently—the controller handles them via wear leveling, and chkdsk rarely sees them. If you’re getting chkdsk errors on an SSD, it’s usually a firmware issue or a loose SATA cable, not the NAND itself.
How to Run chkdsk the Right Way (Without Losing Data)
First, back up. chkdsk can sometimes make things worse if the drive is physically dying. If the drive is making clicking noises, stop. chkdsk will kill it faster.
Open Command Prompt as Administrator. Then:
- chkdsk C: /f — fixes file system errors. Schedules on reboot if C: is in use.
- chkdsk C: /r — includes /f plus bad sector scan. Takes forever.
- chkdsk C: /scan — online scan, no reboot. Only works on NTFS. Finds errors but doesn’t fix them.
- chkdsk C: /perf — uses more memory for faster scanning. Only useful with /scan or /r on big drives.
If you run chkdsk /r on a drive with many bad sectors, it can take days. Literally. And if the drive is failing, it might not finish. So always check the drive’s SMART status first with CrystalDiskInfo. If it says «Caution» or «Bad,» don’t run chkdsk. Clone the drive with ddrescue or Macrium Reflect first.
Common Myths About chkdsk That Need to Die
Myth 1: chkdsk improves performance. No. It might fix a corruption that was slowing things down, but it doesn’t optimize anything. If your PC is slow, check Task Manager, not chkdsk.
Myth 2: chkdsk can recover deleted files. False. It can sometimes recover lost chains (orphaned data) as .CHK files, but those are rarely useful. Use Recuva or PhotoRec for deleted files.
Myth 3: You should run chkdsk regularly. No. Only when you have symptoms: sudden freezes, file system errors in Event Viewer (Event ID 55, 98, 140), or after an unexpected shutdown. Running it monthly is a waste of time and adds wear to your drive.
When chkdsk Fails or Hangs
If chkdsk gets stuck at a percentage (like 11% or 27%) for hours, the drive likely has unreadable sectors. It’s retrying. You can try to let it finish, but if it’s been 24 hours, force a reboot. Then run chkdsk /f without /r to skip the sector scan. If that also hangs, your drive is done. Replace it.
Another scenario: chkdsk says «Cannot lock current drive» because the volume is in use. That’s normal for C:. It’ll ask to schedule on next restart. Say yes. For other drives, close all programs using them.
Bottom Line: chkdsk Is a Diagnostic Tool, Not a Cure
Understanding what happens when you run chkdsk means accepting its limits. It fixes logical corruption. It can’t fix physical damage, and it won’t make a slow drive fast. Use it when Windows tells you to, or when you see file system errors. Otherwise, leave it alone. And if chkdsk keeps finding the same errors after multiple runs, stop running it. Your drive is telling you something. Listen.
