SFC /scannow is one of the most useful built-in Windows troubleshooting commands for diagnosing and repairing corrupted, missing, or incorrectly modified protected operating-system files.

SFC stands for System File Checker.

The System File Checker is part of Windows Resource Protection and can verify the integrity of protected Windows system files. When SFC detects a protected file that does not match the expected Windows version, it attempts to restore the correct version.

Microsoft supports SFC on current Windows client and server platforms, including Windows 11 and Windows Server editions.

The basic command is:

sfc /scannow

The command must normally be run from an elevated Command Prompt or Windows Terminal with administrator privileges.

What Does SFC /scannow Actually Do?

When you execute:

sfc /scannow

Windows performs several operations.

1. Scans Protected Windows System Files

SFC examines files protected by Windows Resource Protection.

These include many important operating-system components such as:

• DLL files
• Windows executables
• system components
• Windows libraries
• drivers and supporting system files
• files required by built-in Windows features

SFC is therefore different from an antivirus scanner.

It is checking the integrity of protected Windows files, not searching your entire computer for malware.

2. Detects Corrupted or Modified Files

System files can become damaged for many reasons, including:

• interrupted Windows Updates
• sudden power failures
• disk errors
• improper shutdowns
• failed software installations
• failed driver installations
• storage problems
• malware activity
• unsuccessful Windows upgrades
• manual modification of Windows files

SFC compares protected files against the versions Windows expects.

If inconsistencies are found, SFC attempts to repair them.

What Problems Can SFC /scannow Fix?

SFC can be useful when Windows problems are being caused by damaged protected operating-system files.

Examples include:

Windows features not working

Built-in Windows features may fail to open or behave incorrectly.

Windows applications crashing

Applications that depend on damaged Windows components may crash or fail to start.

Windows Explorer problems

File Explorer or the Windows shell may behave abnormally if required components have become corrupted.

Windows Update problems

Some Windows Update failures can be associated with damaged system files or component corruption.

Missing or corrupted DLL files

If the affected DLL is a Windows-protected system file, SFC may restore it.

Windows instability

Unexpected freezing, errors, crashes, or other abnormal behavior can sometimes result from system-file corruption.

Blue Screen errors

SFC may help if a BSOD is ultimately being triggered by corruption in protected Windows files.

However, BSODs can also be caused by:

• faulty RAM
• storage failure
• defective drivers
• overheating
• firmware problems
• hardware faults

Therefore, SFC should not be considered a universal BSOD repair command.

Does SFC /scannow Delete Personal Files?

Normally, no.

SFC is designed to check and repair protected Windows system files.

It does not intentionally delete normal user data such as:

• Word documents
• Excel files
• PDFs
• photographs
• videos
• email data
• accounting data
• desktop files
• downloads

It also does not function as a Windows reset.

Nevertheless, maintaining a current backup is always recommended before performing significant operating-system troubleshooting, especially when disk corruption or hardware failure is suspected.

Does SFC /scannow Remove Installed Programs?

Normally, no.

Running:

sfc /scannow

is not equivalent to:

• Reset this PC
• Windows reinstall
• Windows upgrade
• application uninstall
• System Restore

Its purpose is to verify and repair protected Windows files.

How to Run SFC /scannow Correctly

Method 1 – Command Prompt

Click Start and search for:

cmd

Right-click Command Prompt and select:

Run as administrator

Accept the UAC prompt.

Then enter:

sfc /scannow

Press Enter.

Do not close the Command Prompt while verification is running.

Wait until it reaches:

Verification 100% complete.

Recommended Modern Repair Procedure: DISM First, Then SFC

For current versions of Windows, Microsoft recommends repairing the Windows image/component store with DISM before running System File Checker when troubleshooting system corruption.

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for DISM to complete.

If successful, you should receive a message similar to:

The restore operation completed successfully.
The operation completed successfully.

Then run:

sfc /scannow

Therefore, a practical repair sequence is:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart Windows after the repair if you are troubleshooting operating-system problems.

Why Run DISM Before SFC?

This distinction is important.

DISM can repair the Windows image/component store that provides components needed for servicing Windows.

SFC checks and repairs protected Windows system files.

A simplified way to understand the relationship is:

Windows Component Store
        ↓
       DISM
        ↓
Repair component/image corruption
        ↓
       SFC
        ↓
Verify and repair protected system files

If the underlying Windows repair source is damaged, SFC may be unable to repair some files.

Repairing the Windows image first can therefore allow SFC to complete successfully afterward.

Understanding SFC Scan Results

SFC can produce several important messages.

Result 1: Windows Resource Protection Did Not Find Any Integrity Violations

You may see:

Windows Resource Protection did not find any integrity violations.

This is a good result.

It means SFC did not detect integrity problems with the protected system files it checked.

However, this does not prove that the entire computer is healthy.

Your problem could still be related to:

• application corruption
• drivers
• registry settings
• user profile corruption
• malware
• storage problems
• RAM
• Windows configuration
• third-party software

Result 2: Windows Resource Protection Found Corrupt Files and Successfully Repaired Them

You may see:

Windows Resource Protection found corrupt files and successfully repaired them.

This means corruption was detected and SFC successfully repaired the affected protected files.

Recommended next step:

Restart Windows.

Then test whether the original problem has been resolved.

For important troubleshooting cases, you can run:

sfc /scannow

again after restarting.

If the second scan reports:

Windows Resource Protection did not find any integrity violations.

the protected files checked by SFC are now passing verification.

Result 3: Windows Resource Protection Found Corrupt Files but Was Unable to Fix Some of Them

You may receive:

Windows Resource Protection found corrupt files but was unable to fix some of them.

This means SFC detected corruption but could not automatically repair every affected file.

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

After DISM completes, restart Windows if appropriate and run:

sfc /scannow

again.

Result 4: Windows Resource Protection Could Not Perform the Requested Operation

You may receive:

Windows Resource Protection could not perform the requested operation.

Possible troubleshooting steps include:

1. Restart Windows.
2. Run Command Prompt as Administrator.
3. Try SFC again.
4. Run DISM.
5. Try SFC in Safe Mode.
6. Check the Windows component store.
7. Check the system drive for filesystem or storage problems.

Microsoft specifically recommends trying SFC in Safe Mode for this condition and checking the required PendingDeletes and PendingRenames locations under the Windows servicing folders.

How to View the SFC Log

Detailed SFC activity is recorded in:

C:\Windows\Logs\CBS\CBS.log

The complete CBS log contains considerable Windows servicing information, so it can be difficult to analyze directly.

Microsoft provides a useful command for extracting SFC-specific entries.

Run:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

This creates:

sfcdetails.txt

on the current user's Desktop.

Open the file and look for entries referring to files that could not be repaired.

Important

The extracted file can contain information from multiple SFC runs.

Check the date and time of entries when identifying the results of your latest scan.

Other Useful SFC Commands

/scannow is only one function of System File Checker.

Verify Files Without Repairing Them

sfc /verifyonly

This checks protected system files but does not attempt repairs.

This is useful when you want to diagnose integrity problems before making repairs.

Scan and Repair One Specific System File

Syntax:

sfc /scanfile=<file>

Example:

sfc /scanfile=C:\Windows\System32\kernel32.dll

SFC checks the specified protected file and attempts to repair it if necessary.

Verify a Specific File Without Repairing It

Use:

sfc /verifyfile=<file>

Example:

sfc /verifyfile=C:\Windows\System32\kernel32.dll

This verifies the specified protected file without performing a repair.

SFC Offline Repair

SFC can also work against an offline Windows installation.

Microsoft provides the following parameters:

/offbootdir
/offwindir

Typical syntax:

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

This can be useful when the installed Windows operating system cannot boot normally.

Important

Drive letters inside Windows Recovery Environment may be different from those seen during normal Windows operation.

For example, your normal:

C:\Windows

installation might appear as:

D:\Windows

inside WinRE.

Always identify the correct Windows partition before running offline repair commands.

How to Identify the Windows Drive in Recovery Environment

From Command Prompt in WinRE, try:

dir C:\Windows

If Windows is not there, try:

dir D:\Windows

and then:

dir E:\Windows

Continue until you identify the correct Windows installation.

Do not assume that Windows will always be assigned drive C: in the recovery environment.

SFC vs DISM – What Is the Difference?

Tool	Primary Purpose
SFC	Checks and repairs protected Windows system files
DISM	Services and repairs the Windows image/component store
CHKDSK	Checks filesystem/storage-related problems
Startup Repair	Diagnoses certain Windows startup failures

These tools perform different jobs.

For system corruption, a common repair sequence is:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

For suspected filesystem or disk-related problems, additional disk diagnostics may be necessary.

Should You Run CHKDSK Before SFC?

Not normally.

SFC and CHKDSK solve different problems.

Use SFC when you suspect:

• Windows system-file corruption
• damaged Windows components
• missing protected files

Consider disk diagnostics when you suspect:

• filesystem corruption
• storage errors
• bad sectors
• SSD/HDD failure
• disk-related Event Viewer errors

If the physical drive itself is failing, repairing Windows files alone will not solve the underlying problem.

Back up important data immediately when hardware failure is suspected.

Can SFC Fix Malware?

SFC is not an antivirus or anti-malware scanner.

Malware may modify Windows system files, and SFC might restore certain protected files afterward, but it does not replace security scanning.

If malware is suspected, use an appropriate security product such as Microsoft Defender Antivirus or another trusted security solution.

A reasonable process can be:

1. Scan for malware
2. Remove or isolate the threat
3. Repair the Windows image if necessary
4. Run SFC
5. Restart
6. Verify system integrity again

Can SFC Fix Windows Update Errors?

Sometimes.

System-file or servicing corruption can contribute to Windows Update failures.

A common troubleshooting sequence is:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Restart Windows and retry Windows Update.

However, Windows Update errors can also result from:

• insufficient disk space
• update cache problems
• network issues
• proxy/VPN configuration
• incompatible drivers
• third-party security software
• servicing stack problems
• pending reboot operations

Therefore, SFC should be treated as one diagnostic and repair step rather than a universal Windows Update solution.

Can You Use the Computer While SFC Is Running?

Technically, Windows may remain usable during an online SFC scan.

However, for troubleshooting purposes it is preferable to minimize activity while the scan is running.

Most importantly:

Do not close the Command Prompt or Windows Terminal before verification reaches 100%.

How Long Does SFC /scannow Take?

There is no fixed duration.

The time depends on factors such as:

• SSD versus HDD
• system performance
• Windows installation size
• system workload
• amount of corruption
• storage condition

It may finish relatively quickly on a modern SSD or take considerably longer on slower systems.

What If SFC Appears Stuck?

SFC may appear to pause at a particular percentage for some time.

Do not immediately terminate it.

Allow sufficient time for the process to continue, particularly on:

• older computers
• HDD-based computers
• heavily loaded servers
• systems with servicing corruption

If it remains stuck for an unusually long period, investigate Windows servicing and storage health rather than repeatedly terminating the scan.

Can SFC Be Run on Windows Server?

Yes.

SFC is supported on Windows Server platforms as well as Windows client operating systems.

It can be particularly useful when troubleshooting servers experiencing:

• Windows component errors
• failed Windows Updates
• unexplained Windows service failures
• corrupted system components
• system instability
• operating-system file corruption

However, production servers should be handled carefully.

Before repair operations:

• verify backups
• consider maintenance windows
• check recent Windows Updates
• review Event Viewer
• document existing errors
• ensure critical applications are protected

This is especially important for RDS, database, accounting, ERP, file, and application servers.

Recommended Administrator Workflow

For a Windows computer that is unstable but still boots normally, a practical troubleshooting workflow is:

Step 1 – Restart Windows

Eliminate pending reboot conditions where possible.

Step 2 – Install appropriate Windows updates

If the machine is in a supported and stable servicing state, ensure required updates are applied.

Step 3 – Open elevated Command Prompt

Use:

Run as administrator

Step 4 – Repair Windows image

DISM.exe /Online /Cleanup-Image /RestoreHealth

Step 5 – Run System File Checker

sfc /scannow

Step 6 – Review the result

Determine whether corruption:

• was not found,
• was found and repaired, or
• was found but could not be repaired.

Step 7 – Restart

Restart Windows after successful repairs where practical.

Step 8 – Run SFC Again

sfc /scannow

Ideally, the final result should be:

Windows Resource Protection did not find any integrity violations.

Step 9 – Continue troubleshooting if the original problem remains

A clean SFC result does not mean every Windows problem is fixed.

Investigate:

• Event Viewer
• application logs
• drivers
• disk health
• RAM
• startup services
• user profile
• Windows Update
• third-party software

depending on the symptoms.

Important Limitations of SFC

SFC is powerful, but understanding what it cannot do is equally important.

SFC normally cannot directly repair:

• failing SSDs or HDDs
• defective RAM
• overheating
• faulty motherboard components
• application-specific corruption
• third-party software bugs
• incorrect application settings
• every registry problem
• every driver problem
• malware infections
• damaged user profiles
• network problems
• BIOS/UEFI problems

Therefore:

A successful SFC scan means protected Windows system files passed SFC's integrity check. It does not certify the entire PC as fault-free.

Useful Command Reference

Standard repair

sfc /scannow

Verification only

sfc /verifyonly

Verify one file

sfc /verifyfile=C:\Windows\System32\kernel32.dll

Scan and repair one file

sfc /scanfile=C:\Windows\System32\kernel32.dll

Repair Windows image

DISM.exe /Online /Cleanup-Image /RestoreHealth

Extract SFC entries from CBS.log

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

Example offline SFC scan

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Frequently Asked Questions (FAQ)

1. What does SFC /scannow do?

It scans protected Windows system files for integrity problems and attempts to replace incorrect or corrupted protected files with correct Windows versions.

2. Is SFC /scannow safe?

Yes. It is a built-in Microsoft Windows administration and repair utility.

3. Does SFC delete personal data?

SFC is designed to repair protected operating-system files, not user documents and other personal data.

4. Does SFC uninstall applications?

Normally, no. It is not an application-uninstallation tool.

5. Should I run DISM or SFC first?

Microsoft's current repair guidance recommends running:

DISM.exe /Online /Cleanup-Image /RestoreHealth

before:

sfc /scannow

when repairing Windows corruption.

6. Do I need administrator rights?

Yes. Open Command Prompt or Windows Terminal with Run as administrator.

7. Can I run SFC multiple times?

Yes. Running SFC again after repairs and a restart can help verify that protected system files now pass integrity checks.

8. What does "no integrity violations" mean?

It means SFC did not detect integrity violations in the protected system files it checked.

9. What if SFC finds corruption but cannot repair it?

Run DISM /RestoreHealth, restart if appropriate, and run SFC again. If corruption remains, examine the CBS log and continue with advanced repair procedures.

10. Where is the SFC log?

SFC-related information is recorded in:

C:\Windows\Logs\CBS\CBS.log

11. Can I create an easier SFC log file?

Yes. Run:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

12. Can SFC repair Windows 11?

Yes.

13. Can SFC repair Windows 10?

Yes, although organizations should also consider the support status of the specific Windows 10 installation they are maintaining.

14. Can SFC be used on Windows Server?

Yes. Microsoft documents SFC for supported Windows Server versions as well as Windows client editions.

15. Can SFC repair a computer that will not boot?

Offline SFC can sometimes be used from Windows Recovery Environment, but non-booting systems may require Startup Repair, DISM, boot configuration repair, storage diagnostics, or other recovery procedures depending on the cause.

16. Does SFC fix Blue Screen errors?

It can help when corrupted protected Windows files are contributing to the BSOD, but many BSODs are caused by drivers or hardware and require separate diagnosis.

17. Does SFC remove viruses?

No. SFC is not antivirus software.

18. Can SFC fix missing DLL errors?

It may repair a missing DLL if that DLL is a protected Windows system file. It will not necessarily repair third-party application DLLs.

19. Can I cancel SFC while it is running?

It is better to allow the verification process to reach 100%. Do not routinely terminate an active SFC repair.

20. Why does SFC keep finding corrupted files?

Repeated corruption can indicate a deeper problem such as component-store corruption, failed Windows servicing, storage errors, unstable hardware, or other system issues. Investigate the root cause rather than repeatedly relying on SFC.

21. Does a successful SFC scan mean Windows is completely healthy?

No. It verifies protected system files within SFC's scope. Drivers, applications, hardware, user profiles, networking, and many other components can still have problems.

22. What is sfc /verifyonly?

It checks protected Windows files for integrity violations without attempting repairs.

23. Can SFC check only one file?

Yes. Use /scanfile to scan and potentially repair a specific protected file or /verifyfile to verify it without repair.

24. Can SFC run from Safe Mode?

Yes. Safe Mode can also be useful when Windows Resource Protection reports that it could not perform the requested operation.

25. What should I do if DISM and SFC both fail?

Review the error codes and CBS/DISM logs, verify the repair source and Windows version, check storage health, consider offline repair, and evaluate Windows recovery or repair-install options if corruption cannot otherwise be corrected.

Conclusion

SFC /scannow remains one of the most important built-in Windows troubleshooting commands for administrators, support engineers, and advanced users.

Its primary purpose is straightforward:

Verify protected Windows system files and repair incorrect or corrupted versions when possible.

For modern Windows troubleshooting, however, SFC should often be considered part of a broader repair process.

A particularly useful sequence is:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If corruption continues after these commands, do not assume that repeatedly running SFC will solve the problem. Review the CBS log, check the Windows component store, investigate storage and hardware health, and troubleshoot the original symptoms systematically.

Used correctly, SFC is a safe and valuable first-line tool for diagnosing and repairing Windows operating-system file corruption.

#Tags