CHKDSK /f /r: Check and Fix a Hard Drive

What CHKDSK Does – and What It Doesn't

CHKDSK stands for "Check Disk" and has been part of the operating system since the early Windows and DOS versions (back then as ScanDisk). The utility examines the logical structure of a storage device: it checks the file system (NTFS, FAT32 or exFAT), the Master File Table (MFT), index entries, cluster chains and the way files are mapped to their storage areas. If CHKDSK finds inconsistencies, it tries to fix these file system errors.

The distinction matters: CHKDSK repairs the management logic of a partition; it is not a data recovery program. The tool does not restore deleted files and is no substitute for a backup. With purely logical problems – for instance after a power failure or an unclean shutdown – it can often bring a drive back into a consistent state. If there is a physical defect, however, the command reaches its limits.

CHKDSK Parameters at a Glance

Without any parameter, CHKDSK only runs a read-only check and writes a report without changing anything – that is the lowest-risk option for an initial diagnosis. The program only becomes write-active with the following switches:

The command always refers to a drive letter. chkdsk C: /f /r checks and repairs drive C, chkdsk D: /f only drive D. The combination /f /r is the most commonly used call, because /r includes the check for bad sectors and already covers the file system repair.

Running chkdsk /f /r Correctly

CHKDSK needs elevated rights for a repair. The procedure is straightforward:

1. Open the command prompt as administrator: type cmd in the Start menu, right-click "Command Prompt" and choose "Run as administrator". You can also use PowerShell.
2. Enter the command: type chkdsk C: /f /r and confirm with Enter. Use the matching letter for other partitions.
3. Schedule the system drive: on the drive Windows runs from, the volume cannot be locked. CHKDSK offers to run the check on the next restart – confirm with Y.
4. Restart: after the reboot, the error check runs before Windows itself starts. With /r active, this process can take from a few minutes to several hours, depending on the size and condition of the hard drive.
5. Review the result: you can later find the log in the Event Viewer under the source "Wininit" (for scheduled checks) or "Chkdsk". It documents which errors were found and fixed.

If CHKDSK aborts the check or stays stuck at a fixed percentage for a long time, that is a serious warning sign. In that case do not force the process – instead, work out the cause, which is often a hardware problem.

When CHKDSK Puts Your Data at Risk

On a healthy drive with a purely logical file system error, CHKDSK is a sensible and usually safe tool. It becomes critical as soon as the device is already damaged – and these are exactly the situations the program does not detect reliably, because it only looks at the logical layer.

• Mechanical or electrical defect: clicking or grinding noises, a drive that is no longer recognised, or abnormal SMART values point to a physical defect. The /r parameter forces CHKDSK to scan the entire surface with countless read attempts. On an unstable drive this puts extra strain on already weakened read heads and sectors – the condition can deteriorate until data is lost for good.
• RAW file system or severely damaged structure: if Windows shows the drive as RAW, the file system structure is already badly disturbed. CHKDSK may then rewrite directory and index entries or move fragments it identifies as orphaned into a found.000 folder. That makes a later reconstruction without formatting harder.
• SSDs, USB sticks and memory cards: with flash memory there is no physical magnetic disk that would need scanning for bad sectors. chkdsk /r offers little benefit here, and with a controller or firmware problem every write access can be counterproductive.

The common denominator: with /f and /r, CHKDSK always changes the original. If important data is affected and no current backup exists, this intervention carries a risk.

Decision Aid: Run CHKDSK or Not?

The overview below sums up when the command is safe and when other steps come first. It does not replace a diagnosis, but it helps avoid the most common wrong decisions.

Safe Alternatives and Complementary Windows Tools

Before you start a write-active repair run, there are lower-risk ways to narrow down a problem:

• Check only, don't repair: a call without parameters (chkdsk C:) or the online scan chkdsk C: /scan merely creates a report. That way you can see whether any file system errors exist at all, without CHKDSK changing anything.
• Secure a copy first: for important data, a 1:1 image or a clone of the drive is worthwhile before any intervention. Repair attempts then run on the copy while the original stays untouched. A well-thought-out backup strategy makes such steps far more relaxed anyway.
• Treat system files separately: if Windows starts faultily, the cause is often not the drive's file system but damaged system files. That is the job of sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth – they repair Windows components, not your personal files.
• Check drive letters and partitions: if a partition is not accessible, a look at Disk Management or diskpart helps to verify the letter and state of the volume before you trigger a repair.

These tools address different problems. CHKDSK is meant for errors in the file system, while sfc and DISM target the operating system itself – confusing them quickly leads to unnecessary or risky steps.

When Professional Data Recovery Is the Safe Route

For everyday logical errors on a working hard drive, CHKDSK is the right solution. But once hardware symptoms come into play or the data is irreplaceable, the balance shifts. Every further repair and read attempt on an unstable drive can change its logical and physical condition – and thus reduce the chances of a later recovery.

In a specialised lab the device is first analysed gently, before any write operation takes place. Instead of straining the original, the experts work with a secured copy and with methods that deliberately skip critical areas. This means data can often still be recovered even when a CHKDSK run has already failed or the drive can no longer be read cleanly. That applies to classic HDDs as well as SSDs, USB sticks and memory cards.

Conclusion: Assess First, Then Run

chkdsk /f /r is a reliable tool for fixing file system errors and bringing a hard drive back into a consistent state – provided the device is fundamentally stable. The right order is decisive: first assess the symptoms, back up important data, then check, and only repair last. If the drive shows signs of a physical defect or a RAW file system, restraint is the better choice. In that case a professional analysis takes you to your goal more safely than a repair command that changes the original.

Frequently Asked Questions About CHKDSK

Does chkdsk /f /r delete my data?

Normally not – on a working drive CHKDSK fixes file system errors without removing intact files. In damaged structures, however, the program may move fragments it identifies as orphaned into a found.000 folder or rewrite directory entries. As a result, files can sometimes appear to have "vanished". If the data is irreplaceable and the structure is already disturbed, you should create a backup before a repair run.

How long does chkdsk /r take?

That depends heavily on the capacity and condition of the drive. The /r parameter scans the entire surface for bad sectors. On a healthy drive in the mid-terabyte range this often takes from one to several hours. If CHKDSK finds many problematic sectors, the process slows down noticeably. A run that lingers at a fixed percentage for a very long time usually points to a hardware problem.

CHKDSK is stuck at a percentage – what should I do?

If the error check stays permanently at the same point, CHKDSK is probably trying to process a hard-to-read area. On a mechanically defective hard drive, every further read attempt can enlarge the damage. Do not repeatedly force an abort and, if possible, avoid switching the drive on again and again. If the data is important, professional data recovery is the safer route than further start attempts.