Helping millions of people navigate the world of technology.

What to Do When SFC SCANNOW Does Not Complete

Quick Tips
  • An SFC being stuck or not completing is something that can be fixed with other processes like CHKDSK and DISM.
  • You can also help the process by freeing up memory in Task Manager.
  • Try running SFC in Safe Mode for minimal interruption.

The System File Checker is a vital part of most troubleshooting routines, which helps users check for and repair errors in important system files. But what happens when the troubleshooter needs troubleshooting? Today, we’re going to be looking at what to do when the “SFC SCANNOW” does not complete.

SFC SCANNOW Does Not Complete – Fixes to Try

So, if you’re stuck with a System File Checker that won’t finish the job, we’ve got several troubleshooting methods to help you out below:

Run DISM First

Deployment Image Servicing and Management (DISM) and SFC go together so often in troubleshooting that they’re often mentioned in the same breath. If SFC does not complete, try running the DISM scan before it and see if it either fixes the issue or allows the file checker to run again. Here’s what to do:

Step 2. To check if issues picked up can be repaired, once the above process is done, type “DISM /Online /Cleanup-Image /CheckHealth” and press “Enter.”

Step 1. Open the Run dialog (Win + R) and type “cmd” before clicking (Ctrl + Shift + Enter) to run as Administrator.

Step 3. In Command Prompt, you’ll first need to scan for disk corruption. Type “DISM /Online /Cleanup-Image /ScanHealth” and click “Enter.” The process will begin running.

Step 4. Finally, to begin fixing any issues picked up, type “DISM /Online /Cleanup-Image /RestoreHealth” and click “Enter.”

What to Do When SFC SCANNOW Does Not Complete 1

Step 5. Restart your machine. If your issue isn’t resolved by the DISM, try running the SFC scan in Command Prompt and see if the issue is resolved.

Run CHKDSK

Disk Checker is yet another close troubleshooting cousin of SFC. If things are getting stuck, this is also a good option to try:

Step 1. Open Command Prompt as Administrator.

Step 2. Type “chkdsk C: /f” into the prompt (“C” is your OS drive and “/f” tells CHKDSK to automatically repair detected file-system errors).

What to Do When SFC SCANNOW Does Not Complete 2

Step 3. Select “Enter.” You’ll be told the volume is in use. Type “Y” and click “Enter” to begin the scan when the system restarts.

Step 4. Restart your PC and let the process run.

Close Demanding Tasks

Unsurprisingly, SFC needs a lot of processing power to perform optimally. It’s a good idea, therefore, to give it as much freedom to run as possible. Close all your most demanding apps, including browsers, and free up memory. If you want to check what’s taking up the most resources, open Task Manager by pressing (Ctrl + Shift + Esc) and sorting processes by “Memory.”

What to Do When SFC SCANNOW Does Not Complete 3

Try SFC in Safe Mode

To ensure no third-party apps and processes are interfering with the file checker, you should try running it in Safe Mode. To boot into it:

Step 1. Open the Run Dialog (Win + R) and type “msconfig” into the box, and press “OK.”

Step 2. The System Configuration Window will pop up. Navigate to the “Boot” tab at the top of the window.

Step 3. In the “Boot Options” subgroup, check “Safe boot.” Choose your specific subtype of Safe Mode. “Minimal” is the most stripped-down, while “Network” offers connectivity.

What to Do When SFC SCANNOW Does Not Complete 4

Step 4. Once done, click “Apply,” then “OK” to finalize.

Step 5. Another pop-up will ask you to restart your PC to finalize changes. Click the “Restart,” and you’ll boot into Safe Mode automatically.

What to Do When SFC SCANNOW Does Not Complete 5

Was this helpful?

Thanks for your feedback!

Last updated on 15 June, 2026

Leave a Reply

Your email address will not be published. Required fields are marked *

The article above may contain affiliate links which help support Guiding Tech. The content remains unbiased and authentic and will never affect our editorial integrity.