Windows Scanning and Repairing Drive Stuck? 5 Quick Fixes

The Windows scanning and repairing drive loop hits at the worst possible time, right after a forced shutdown. We tested this on a Windows 11 desktop with a 500GB Samsung 870 EVO and watched the scan crawl for over an hour before pressing Escape. The fix is straightforward: skip the scan, boot to your desktop, then repair the volume on your own schedule.

#Why Does Windows Get Stuck on Scanning and Repairing Drive?

Your drive has NTFS file system corruption, and Windows is running a consistency check before it loads the rest of the OS. According to Microsoft, the /f flag repairs file system errors on Windows 10 and 11 systems, while the /r flag finds bad sectors and recovers readable data from them. The full reference lives in Microsoft’s CHKDSK documentation.

Force-quitting Windows, a hard crash, or a power outage leaves the file system in a half-written state. Physical damage, ransomware, and faulty SATA cables also trigger it.

If you’ve seen the NTFS.SYS stop code on this machine before, the same root cause is at play. Windows uses the same dirty-volume flag whether you’re on a Surface tablet, a custom desktop, or a budget laptop, so the fix path is identical.

#How Do I Skip the Scanning and Repairing Loop Right Now?

Press Escape as soon as the “Scanning and repairing drive” message appears. Most keyboards register the keystroke within 2 seconds, and Windows continues to your login screen.

Here’s the exact sequence:

1. Wait for the scanning and repairing drive message (usually 30 seconds after power-on)
2. Press Escape or any key on your keyboard
3. Windows skips the scan and continues to your lock screen

That’s the trick. The scan resumes on the next boot if you don’t fix the corruption, so don’t restart without running one of the repair commands below.

If the keyboard doesn’t respond, hold the power button for 10 seconds to force shutdown, then power on again. On the second attempt, Windows often skips the scan automatically and loads recovery options instead, where you can choose Continue to Windows to reach your desktop.

#Best Fixes When Windows Still Boots Normally

Once you’ve made it past the lock screen, you can repair the drive without restarting into Safe Mode. These methods run from the desktop while you keep using your PC.

#Method 1: Run the Error Checking Tool

The graphical front end for CHKDSK lives in File Explorer.

1. Open File Explorer and right-click your system drive (usually C:)
2. Select Properties then click the Tools tab
3. Under Error checking, click Check
4. Click Scan drive when prompted (Windows often says the drive is fine; run it anyway)
5. Reboot when the scan reports completion

In our testing on a 500GB Samsung 870 EVO, the scan finished reasonably fast and found no errors. A 2TB Western Digital Blue spinning drive on the same machine took much longer. SSDs always scan faster than mechanical drives because they don’t seek physically.

#Method 2: Use the Storage Health Monitor

Windows 11 has a hardware-level health check buried in Settings.

1. Go to Settings > System > Storage > Advanced storage settings
2. Click Disks & volumes
3. Pick your system drive and click Properties
4. Read the Drive health card

If health reports Caution or Bad, your drive is degrading. Replace it before the loop becomes permanent. A Healthy verdict means the problem is software, and CHKDSK or Repair-Volume can fix it.

This check pulls SMART data directly from the drive controller, so it’s more reliable than third-party utilities for first-pass triage.

#Repair the Corruption Using Safe Mode Commands

When Windows refuses to boot past the scanning screen, Safe Mode with Command Prompt is the fastest path to a working system.

Step 1: Enter Safe Mode

Force three consecutive failed boots by holding the power button during startup. On the fourth power-on, Windows loads the Automatic Repair screen. Then:

1. Click Advanced options
2. Pick Troubleshoot > Advanced options > Startup Settings
3. Click Restart, then press 6 for Safe Mode with Command Prompt

If you hit the Windows automatic repair loop instead of this menu, that’s a separate fault to clear before continuing here.

Step 2: Run CHKDSK

At the command prompt, type:

chkdsk C: /f /r

The /f flag fixes file system errors. The /r flag finds bad sectors and recovers readable data from them. In our testing on the same 500GB Samsung 870 EVO, this combination took a fair while to complete. A 2TB Western Digital HDD took considerably longer.

Step 3: Use Repair-Volume as a faster alternative

PowerShell ships with a newer command called Repair-Volume that targets only critical metadata. According to Microsoft’s PowerShell guidance, the -SpotFix parameter takes the volume offline for a few seconds rather than the hours needed for a full scan. Full reference: Repair-Volume on Microsoft Learn.

1. Right-click Windows PowerShell and pick Run as Administrator
2. Type:

Repair-Volume -DriveLetter C -SpotFix

When we ran this on the same 500GB SSD that CHKDSK had taken a while to scan, Repair-Volume -SpotFix finished far faster. SpotFix is the right call for first-pass repair because it skips sectors that aren’t flagged dirty.

Step 4: Reboot

After either command finishes, type exit and restart the PC. The scanning loop should be gone.

#Preventing the Loop From Coming Back

A successful repair means nothing if the same corruption returns next week. Two causes account for almost every recurring case: malware activity and degrading hardware.

#Check for Malware

Ransomware and file-locking malware corrupt the NTFS journal repeatedly. Run a full antivirus scan if the loop returns within a week of a successful repair. Microsoft Defender catches most threats, but a dedicated tool like Malwarebytes Free is worth running as a second opinion.

When we tried this combination on a deliberately infected test machine, Microsoft Defender caught a Trojan quickly, and Malwarebytes flagged two adware payloads Defender missed. If your loop pairs with high disk usage symptoms, malware is the most likely cause.

#Update Storage Drivers

Outdated AHCI, NVMe, or RAID controller drivers can corrupt write operations and trigger the scan on every boot. To update:

1. Go to Settings > Windows Update
2. Click Check for updates
3. Open Advanced options > Optional updates to find driver updates Windows hasn’t installed yet
4. Restart after applying any storage-related drivers

If Windows Update doesn’t surface a fresh driver, pull the latest one from your motherboard or laptop OEM support page. Tools like the Driver Talent driver utility can scan for outdated controllers, though we recommend checking the OEM page first to avoid bundled software.

#Knowing When to Replace the Drive

If the loop returns after a clean malware scan and updated drivers, the drive itself is the problem. Pull SMART data using a free tool like CrystalDiskInfo. Pay attention to these attributes:

• Reallocated Sectors Count: any value above 0 means the drive has remapped damaged sectors
• Pending Sector Count: a non-zero count signals sectors waiting to be marked bad
• Power-On Hours: drives over 40,000 hours are well past warranty for most consumer SKUs

Microsoft recommends replacing any drive that reports a SMART failure prediction. If your drive shows Caution in Windows Storage health and any of the warning attributes above, back up everything you can read and replace it within the week. A boot device not found error on the next start means you’ve waited too long.

The scan loop combined with SSD not showing up symptoms at boot is also a hardware-failure signal. SSDs often die suddenly rather than degrade gracefully, so don’t trust the drive past the first warning.

#Bottom Line

Press Escape to skip the scan, boot to Windows, then run Repair-Volume -DriveLetter C -SpotFix in an admin PowerShell. That’s the 5-minute fix for the majority of cases we’ve seen. If the loop returns within a week, run a full Malwarebytes scan first, then check SMART status with the Settings health card. A drive showing Caution health and re-triggering the scan needs replacement, not another CHKDSK pass.

#Frequently Asked Questions