Windows feels slow, files corrupt themselves, or a strange clicking sound has started. Before blaming Windows, check the disk — but with the right tool, because "disk check" actually means two different tests.
People say "run a disk check" as if it were one thing. It is two. chkdsk examines the file system — the map Windows uses to find your files — and repairs its errors. SMART status asks the drive hardware itself how healthy it feels. A disk can pass one test and fail the other, so a technician runs both. This guide shows each command, how to read the verdict, and the honest limits of the old wmic health command.
👆 The two answers you want to see: a clean file system from chkdsk and Healthy from the drive itself. Disk name shown is an example.
chkdsk C: — it reports problems without changing anythingchkdsk C: /f. On the Windows drive Windows will ask to schedule the check at the next restart — press Y and restartchkdsk C: /r also hunts for bad sectors and tries to recover readable data — it takes much longer, so use it only when bad sectors are suspectedThe classic one-liner still works on many PCs:
wmic diskdrive get model,status⚠️ Honest note: wmic is deprecated by Microsoft and disappearing from new Windows builds. The modern equivalent gives more detail — use the next step as your main method.
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, HealthStatus, SizeGet-CimInstance -Namespace root\wmi -ClassName MSStorageDriver_FailurePredictStatus — PredictFailure False is good newsUnderstand what SMART is: the drive’s self-report. It catches many slow deaths — growing bad sectors, motor and temperature trouble — but a drive can also die suddenly with SMART still smiling. SMART is a warning system, not a guarantee, which is why backups exist.
chkdsk and its repair partners are all in the 60 commands video — see the complete disk and repair sections there.
▶️ Watch Full Video/f fixes file system errors it finds. /r does everything /f does, plus scans every sector of the drive for physical damage and tries to recover readable information from bad sectors. /r takes far longer — on a big drive it can run for hours — so it is reserved for suspected physical problems.
A healthy disk is only one part of speed. Check RAM pressure and startup programs in Task Manager, run sfc /scannow for Windows file damage, and look at temperatures if fans run loud. The 60-commands toolkit approach is to test each suspect quickly instead of guessing.
A read-only chkdsk C: changes nothing and is completely safe. The repairing modes /f and /r modify the file system to fix it, which is normally safe and necessary — but on a physically dying drive, any heavy repair can be the last straw. That is why this guide insists on backing up important data before repair scans on a suspect drive.