If you’ve ever run the ‘SFC /SCANNOW’ command to repair corrupted system files in Windows 10 or Windows 11, you already know it’s supposed to be a straightforward process. You fire up Command Prompt, run the scan, and let Windows fix itself. Simple, right
Well… not always.
A surprisingly common issue is the scan getting stuck at a specific percentage, especially ‘76%’. It just sits there. No progress, no error message, nothing. You wait a few minutes, then longer, then you start wondering if your system is frozen or if something deeper is wrong
In this guide, I’ll walk you through exactly why this happens and how to fix it step by step in a clear, practical way
Why is SFC /SCANNOW stuck at 76%?
The ‘System File Checker’ scans protected system files and replaces corrupted ones with cached copies. When it stalls at 76 percent, it’s usually because
- The tool hits a corrupted file it struggles to process
- There are disk errors or bad sectors
- System services interfere with the scan
- Windows image files themselves are damaged
- Hardware issues slow or halt access
The key is not to panic. In many cases, the scan is not completely frozen, just extremely slow. But if it stays stuck for more than 30 to 60 minutes with no disk activity, you’ll need to step in.
How to fix SFC /SCANNOW stuck at 76% indefinitely in Windows 10/11
If ‘SFC /SCANNOW’ is stuck at 76 percent in Windows 10 or 11, restart your system, run the scan in Safe Mode, check your disk using ‘CHKDSK’, repair system images using ‘DISM’, and disable background services that may interfere. These steps resolve file corruption and system conflicts, causing the scan to freeze
Let’s fix it properly
Step 1: Confirm it is actually stuck
First things first, don’t interrupt the scan too quickly
Sometimes ‘SFC /SCANNOW’ appears frozen at 76 percent but is still working in the background. This step saves you from unnecessary troubleshooting
Open Task Manager by pressing Ctrl + Shift + Esc and check disk usage
If you see activity under your drive, especially from Windows Modules Installer Worker or TrustedInstaller, the scan is still running
Wait at least 20 to 30 minutes before deciding it’s truly stuck
If disk usage is at zero and nothing changes for a long time, move to the next step
Step 2: Restart your system properly
This might sound basic, but it’s surprisingly effective
Close the Command Prompt and restart your computer normally
A restart clears temporary glitches, resets system services, and removes locked file states that may have caused the scan to freeze
After reboot, Open Command Prompt as Administrator, and run the command again: Type ‘sfc /scannow’ and press Enter.
If it completes successfully this time, you’re done
If it gets stuck again at the same percentage, continue
Step 3: Run SFC in Safe Mode
Running the scan in Safe Mode eliminates interference from third-party apps and unnecessary services
- Press Windows + R and type ‘msconfig’
- Go to the Boot tab
- Enable ‘Safe boot’ and select Minimal
- Restart your system
Once in Safe Mode, open Command Prompt as Administrator: Run ‘sfc /scannow’
In Safe Mode, Windows loads only essential drivers, so the scan often completes without interruptions
After the scan finishes
Open ‘msconfig’ again and disable Safe Boot to return to normal mode
Step 4: Check your disk for errors using CHKDSK
A stuck SFC scan is often linked to disk issues
Type the following command in Command Prompt as Administrator: ‘chkdsk C: /f /r’
Press Enter. If prompted, type Y and restart your system.
This process scans for:
- File system errors
- Bad sectors
- Corrupted disk areas
It may take some time, especially on large drives, but it’s crucial
Once completed, try running ‘sfc /scannow’ again
Step 5: Repair Windows image using DISM
If the underlying Windows image is damaged, SFC won’t work properly
That’s where ‘DISM’ comes in
Open Command Prompt as Administrator and run
‘dism /online /cleanup-image /restorehealth’
This command connects to Windows Update and downloads clean files to repair the system image
Wait until it reaches 100 percent
Then run
‘sfc /scannow’
This combination fixes most stubborn cases
Step 6: Disable background services temporarily
Some services can interfere with system file scans
- Press Windows + R and type ‘msconfig’.
- Go to the Services tab
- Check ‘Hide all Microsoft services’
- Click Disable all
Then go to the Startup tab and disable startup apps
Restart your system and run SFC again
This creates a clean boot environment, reducing conflicts
After fixing the issue, you can re-enable services
Step 7: Run SFC from Windows Recovery Environment
If the scan keeps freezing, try running it outside the normal Windows environment
Restart your PC and enter Advanced Startup
Go to Troubleshoot > Advanced options > Command Prompt > Then run:
‘sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows’
This scans the system offline, avoiding interference from active processes
Step 8: Check for Windows updates
Outdated system files can cause compatibility issues with SFC
- Go to Settings
- Open Windows Update
- Check for updates
Install all pending updates and restart your system
Then run the scan again
Step 9: Scan for malware or system interference
Malware can corrupt system files or block repair processes
Use Windows Security or a trusted antivirus to run a full scan
If threats are detected, remove them and restart your system
After that, run ‘sfc /scannow’ again
Step 10: Consider hardware issues if nothing works
If the problem persists even after all fixes, it could point to hardware problems
Common causes include
- Failing hard drive
- Faulty RAM
- Overheating components
You can test memory using Windows Memory Diagnostic and check disk health using third-party tools
Faqs
Why does SFC /SCANNOW always get stuck at 76%?
This percentage often corresponds to a specific system file or directory. If that file is corrupted or difficult to access, the scan may appear stuck
Is it safe to close SFC while it is running
No, it’s not recommended. Interrupting the scan can leave files partially repaired. Only stop it if you’re sure it’s completely frozen
How long should SFC take to complete
Typically between 10 and 30 minutes. On slower systems or larger drives, it may take longer
Can I run SFC multiple times
Yes, running it more than once can help fix additional issues that were not resolved in the first pass
What if SFC says it found errors but could not fix them
In that case, run the ‘DISM’ command first, then run SFC again