Last Updated on June 5, 2026
As you probably know, working with computers is not always a flawless experience. They can freeze up, crash, not startup and give you blue screen of death messages (BSOD). Even though Windows is a fairly stable operating system, you will still eventually have some sort of issue with your computer.
One common issue that many people run into is having hard drive errors. You can have these types of errors with traditional spinning disks as well as the newer SSD and NVMe drives. Many of these drive manufactures will offer diagnostic software that you can download if you can find it. But Windows has its own command line tool for checking drives that has been around even before Windows itself in the MS-DOS days. In this article, we will be showing you how to use check disk (CHKDSK) in Windows to fix hard drive errors.
The chkdsk command in Windows is specifically used to thoroughly scan and repair deep file system errors. It completely checks the sector integrity of your active disk volumes. It can safely detect and permanently mark physical bad sectors on a hard drive or SSD so the operating system explicitly avoids using them.
Top Reasons to Use the Chkdsk Command
1. Identify and Repair File System Errors
This is the absolute most common use for this built-in utility. The chkdsk tool can actively scan the entire file system for hidden logical errors on NTFS or FAT32 drives. These specific errors usually include severe issues with file metadata, broken directory structures, and lost Windows folders.
2. Locate Physical Bad Sectors
Hard drives naturally develop physical bad sectors over time with heavy daily usage. These are microscopic areas on the actual disk platter or flash memory chips that can no longer reliably store user data. The utility explicitly maps these exact dead zones out so the operating system never attempts to write data there again.
3. Troubleshoot System Instability
If your computer is experiencing frequent random crashes or sudden blue screen errors, hidden disk corruption could be a massive contributing factor. Running the command line tool helps correctly diagnose and immediately resolve these exact issues. Fixing deep file system fragmentation stops random reboot cycles completely.
4. Recover Data from Damaged Drives
This is technically not a dedicated third party data recovery tool. The specific /r parameter can sometimes successfully recover readable data from failing bad sectors. It actively forces the operating system to migrate surviving files directly to healthy areas of the drive before total mechanical failure occurs.
5. Prepare a Drive for Cloning
You should always run a disk check before actively cloning or creating a system image of a physical drive. Running specific repair parameters helps ensure the source file system is completely healthy. This simple preliminary step minimizes the massive chances of terrible errors being perfectly transferred to the brand new drive.
Essential Chkdsk Command Line Switches
1. The Standard Fix Switch
The /f parameter explicitly tells the utility to fix any logical errors found on the target disk. It repairs file allocation table problems and automatically corrects deep directory errors. This is the absolute most common switch users type when running basic disk maintenance.
2. The Bad Sector Recovery Switch
The /r parameter forces the tool to aggressively locate physical bad sectors and actively recover any readable information. Running this specific command automatically implies the /f switch is active at the exact same time. You will use this exact combination when you suspect hardware failure is imminent.
3. The Volume Dismount Switch
The /x parameter forcefully tells the volume to dismount first before any scanning starts. All open application handles to the active drive are instantly invalidated. This strict action ensures the scanning utility gains absolute exclusive access to the target drive to perform dangerous repairs.
4. The Advanced NTFS Parameters
Windows offers specialized scanning switches strictly for NTFS formatted volumes. The /scan parameter runs a completely online background scan without requiring a disruptive volume dismount. You can also pair this with the /perf switch to force Windows to use more system resources to complete the scan significantly faster.
Running the Chkdsk Tool from Within Windows
1. Open the Drive Properties Menu
One incredibly easy way to perform the disk checking process is to go directly to File Explorer. You must right click exactly on your target drive and choose Properties from the context menu. You can then click directly on the Tools tab located at the very top of the window.
2. Start the Error Checking Tool
Look for the specific Error checking section inside the Tools menu. Click the Check button to instantly start the background scanning process. If you are scanning your primary Windows drive, the graphical tool will only perform a basic read scan from within the active operating system.
3. Review the Scan Recommendations
The graphical interface cannot actually do any structural repairs when Windows is actively running. If the scan finds errors that strictly require exclusive disk access, Windows will prompt you to schedule a deep scan on the next reboot. If you are scanning a secondary non-system drive, the tool can repair those specific errors without needing to reboot the machine first.
4. Override the Clean Disk Warning
You may also run across a strange situation where the utility tells you that you simply do not need to scan your drive. A prompt will pop up stating it does not see anything currently wrong with the volume. You can just click the Scan drive option to continue with the forced scan if you want to double check the hardware integrity yourself.
Using Chkdsk from the Command Line
1. Open an Elevated Command Prompt
Most technology professionals heavily tend to run this utility straight from the command line. You must run the prompt as a local administrator if you actually want to fix errors on a drive rather than just read them. Type cmd directly in the Windows taskbar search box and choose the Run as administrator option from the right side menu.
2. Execute the Repair Command
For our specific example, we will be running the exact command with the F and R switches active. This forces the system to fix any structural errors and aggressively repair physical damage sectors at the exact same time. Type chkdsk C: /F /R and press enter to officially execute the instruction.
3. Schedule the Boot Scan
When running this strict command against the primary Windows drive, you will immediately get a text prompt warning you the volume is currently in use by another process. The terminal will explicitly ask if you would like to schedule this volume to be checked the next time the system restarts. Type Y and press enter to accept this critical maintenance schedule.
4. Restart the Computer
The deep check disk process is officially queued to run the very next time you reboot the hardware. Go ahead and restart your machine right now. Once the computer reboots, you will see a prominent text message appear on a black screen. You will have exactly 8 seconds to press a random key on your keyboard to skip the disk check and go straight back into Windows.
5. Wait for the Scan Stages
If you let the active scan continue past the timer, you will see that it needs to go through several distinct processing stages to complete. This thorough inspection process can take several minutes or even several hours based entirely on the total capacity of your physical drive. The specific combination of switches you used will also greatly impact the total execution time.
Checking the Results of the Chkdsk Scan
1. Open the Event Viewer
Once the background scan has fully completed, Windows will automatically load back up to your standard desktop. You can then manually check the hidden background results of the scan to see if it actually found and fixed anything broken. Open the Windows Event Viewer application and expand the Windows Logs folder section.
2. Filter the Application Logs
Click directly on the Application Logs category on the left side of the screen. Look specifically in the Sources column for log entries named Wininit with an exact event ID of 1001. You can then read through the detailed text log to see exactly what severe errors were flagged and if they were successfully repaired.
3. Use the PowerShell Alternative
You can also pull this exact same log data using a modern command line interface instead of clicking through the graphical Event Viewer application. Open an administrator PowerShell window directly from your start menu. Type the specific command below and press enter to generate similar text results directly inside the terminal window.
Get-WinEvent -FilterHashTable @{logname=”Application”; id=1001} | ? {$_.providername -match “wininit”} | fl timecreated, message
As you can see, it’s not too difficult to use check disk in Windows to fix hard drive errors.
For additional training resources, check out our online IT training courses.
Check out our extensive IT book series.
