SFC Scannow: What It Repairs and What It Doesn’t

SFC /scannow checks protected Windows system files and replaces damaged or missing copies with valid versions when a suitable repair source is available. It can help fix corruption that causes Windows features or built-in tools to malfunction, but it does not repair personal files, most third-party software, hardware faults, or every cause of a Windows problem.

What SFC checks and repairs

System File Checker (SFC) is a Windows command-line utility for checking the integrity of protected operating-system files. The command sfc /scannow scans those files and attempts to repair ones it finds corrupted, altered, or missing. Depending on the Windows version and servicing state, it may use cached copies or other files maintained by Windows as repair sources.

Examples of problems SFC may address include a damaged protected file needed by a Windows component, or a system-file change that causes an included feature to fail. It is not a general-purpose repair command: it does not scan every file on the PC, and a clean result does not establish that all software, settings, or hardware are healthy.

How the scan works

SFC compares protected system files with expected versions and tries to replace files that fail its integrity checks. It needs administrative permission to make system-level repairs. Allow the scan to finish; interrupting it can leave you without a useful final result.

Run it from Windows Terminal, Command Prompt, or PowerShell opened as an administrator. Search for the app, choose Run as administrator, approve the prompt if shown, and enter:

sfc /scannow

The command may take some time. Keep the window open until the verification reaches 100% and a completion message appears. The wording of the result indicates whether SFC found no integrity violations, repaired files, found corruption but could not repair some files, or could not perform the requested operation.

What SFC does not fix

SFC is limited to protected Windows system files. It is not a substitute for diagnosing the wider computer, and it cannot reliably fix problems outside that scope. In particular, do not expect it to:

Recover deleted documents, photos, or other personal data.
Repair application files for most third-party programs or reinstall an application that is broken.
Remove malware, correct every unwanted system change, or undo all configuration and registry changes.
Fix a failing drive, defective memory, overheating, a loose connection, or another hardware problem.
Restore a missing feature, driver, or Windows update in every case, or resolve an issue caused by incompatible software.
Guarantee that Windows will stop crashing or that a particular symptom will disappear.

A damaged component store can also prevent SFC from obtaining a sound replacement copy. In that situation, SFC may report that it found corrupt files but could not fix some of them. That does not necessarily mean the scan itself is useless; it means another repair step may be needed.

When to use DISM first

For Windows 10 and Windows 11, Microsoft’s usual repair sequence for persistent system-file corruption is to run the Deployment Image Servicing and Management tool (DISM) to repair the Windows image, then run SFC again. DISM addresses the component store that can provide repair files; SFC checks and repairs protected system files. They have related but different roles.

Open an elevated terminal and run:

DISM /Online /Cleanup-Image /RestoreHealth
Wait for DISM to finish. It may use Windows Update as a source and can take a while.
Run sfc /scannow again and let that scan complete.

/Online means the command targets the Windows installation currently running. If the computer cannot start normally, or DISM cannot obtain the needed files, the appropriate recovery procedure or repair source can differ. Avoid downloading individual system files from unofficial sites; mismatched files can create further problems.

How to read the results and handle failures

If SFC reports that it did not find any integrity violations, it found no protected-file corruption it could identify. That is reassuring but does not rule out other causes. If it says it found corrupt files and successfully repaired them, restart Windows and check whether the original symptom remains. If corruption was found but some files could not be fixed, run DISM and then SFC again.

If SFC says it could not perform the requested operation, check that the terminal is elevated, the scan has not been interrupted, and the file system and Windows installation are accessible. For a scan that repeatedly fails, consider running it from Windows Recovery Environment or obtaining help with the exact message and system condition. Do not assume that repeating the command indefinitely will fix an underlying disk or servicing problem.

When SFC reports repairs, it records details in the CBS log at %windir%\Logs\CBS\CBS.log. That log can be large and contains servicing activity as well as SFC information. It is mainly useful when a repair result needs further diagnosis; most users do not need to inspect it after a successful repair.

Common misconceptions and safe use

One common misconception is that SFC is a virus scan. It is not designed to detect or remove malware. Another is that “no integrity violations” means the whole computer is verified as healthy. It means only that the scan did not identify a problem in the protected files it checks.

SFC is a built-in Windows maintenance tool, but it still changes protected files when it makes repairs. Use the exact command, run it with administrator rights, and let it finish. Save work first and avoid force-shutting down the PC during servicing. If you suspect a failing drive or have important files that are not backed up, prioritize protecting the data and diagnosing the storage problem rather than repeatedly running repair commands.

Frequently Asked Questions

Does SFC /scannow delete personal files?
SFC is intended to repair protected Windows system files, not remove personal documents or photos. Still, keep important files backed up, especially if the PC is unstable or may have a storage fault.

How long does an SFC scan take?
There is no fixed duration. It varies with the computer and Windows installation. Wait for the scan to reach 100% and display its final message before closing the terminal.

Should I run DISM or SFC first?
If you are following the standard repair sequence for corruption on Windows 10 or Windows 11, run DISM with /RestoreHealth first, then run SFC. DISM can repair the source SFC relies on.

What if SFC says it cannot repair some files?
Run DISM to repair the Windows image, restart if appropriate, and run SFC again. If the same files remain unrepaired, consult the CBS log or use Windows recovery or repair options suited to the exact problem.

Can SFC fix a slow computer or blue-screen errors?
It may help if protected system-file corruption is contributing, but those symptoms have many possible causes, including drivers, software, hardware, and storage. A scan cannot identify or fix all of them.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →