sfc /scannow can repair damaged Windows system files. It cannot certify that your entire PC is healthy—and that distinction matters more than the command’s reputation as a troubleshooting cure-all. Microsoft defines System File Checker as a tool for checking protected system files and repairing problems where possible, not diagnosing everything that can go wrong with a computer.The useful question is not simply, “Have you run SFC?” It is, “Does this problem involve something SFC can repair?”
What SFC actually checks
Microsoft’s command reference, which covers Windows 11 and Windows 10, says /scannow verifies protected system files and attempts repairs. That scope is narrower than “scan Windows for problems.” A clean result does not validate your applications, browser extensions, personal documents, hardware, or every installed driver. That conclusion follows from the tool’s documented boundaries.
For example, if an application’s own update introduces a bug, replacing protected Windows files will not correct that application’s code. Likewise, checking file integrity cannot add RAM or fix overheating. Those are illustrations of the scope limit, not diagnoses of any particular crash. SFC is a targeted repair tool, not a general PC health certificate.
Nor is /scannow merely a diagnostic switch: it attempts repairs. Microsoft separately provides sfc /verifyonly to check protected files without repairing them.
Why DISM belongs in the conversation
SFC needs usable replacement files. Microsoft’s troubleshooting documentation describes repairs that copy files from the Windows system store; if repair resources are damaged, identifying a broken file does not guarantee that SFC can restore it.
Deployment Image Servicing and Management, better known as DISM, addresses the Windows image and component-store side of the problem. Microsoft documents DISM as the more extensive check for store issues, while also describing SFC as a possible quick check. That is an important qualification: DISM-before-SFC is Microsoft’s recommended system-file repair sequence, not a universal ritual for every slow application.
How to run the repair sequence
For a running Windows 11 or Windows 10 installation where system-file corruption is suspected, Microsoft Support gives this procedure:
- Search for cmd.
- Right-click Command Prompt, select Run as administrator, and approve the prompt or provide administrator credentials.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth - After DISM completes successfully, run:
sfc /scannow
Keep the window open until SFC reaches 100%. These operations can take several minutes.
Here, /Online targets the running Windows installation; it does not mean “download everything from the internet.” DISM’s repair-source behavior is a separate matter.
Windows Update is the default repair source unless policy specifies otherwise. Microsoft also supports alternative sources, including mounted Windows images and suitable Windows folders. Its documentation warns that source servicing levels and required language components matter: an arbitrary folder of Windows files is not necessarily a usable repair source. On a managed PC, organizational policy may determine where DISM looks.
The /Source option specifies an alternative location, while /LimitAccess prevents DISM from contacting Windows Update. Consequently, internet access is not an absolute requirement when an appropriate local or network repair source is available.
Read the result before choosing the next step
Microsoft documents four main SFC outcomes:
| Outcome | Meaning and next step |
|---|---|
| No integrity violations | No corruption was detected in the protected files checked. Investigate other causes if symptoms remain. |
| Corruption repaired | The repair operation succeeded. Retest the original problem. |
| Some corruption remains | Examine the repair details rather than assuming success. |
| Operation could not complete | Microsoft recommends retrying in Safe Mode and checking the required servicing folders. |
Those folders are PendingDeletes and PendingRenames under %WinDir%\WinSxS\Temp.
An incomplete scan is not a clean bill of health.
When repair fails, inspect the evidence
Microsoft documents that SFC records verification and repair details in %windir%\Logs\CBS\CBS.log. Its entries carry an [SR] tag. From an elevated Command Prompt, this documented command extracts those entries:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt
The output file is written to the current directory. Check timestamps carefully: the extracted entries can include previous runs, not just the latest attempt. Microsoft’s log examples distinguish files that could not be repaired from files successfully restored from the store. That makes the log more useful than another blind rerun.
A repair result is not a root-cause diagnosis
The practical takeaway from Microsoft’s documented scope is straightforward: a clean scan narrows the investigation; a successful repair establishes that files were repaired. Neither result, by itself, proves why the original symptom occurred—or that it has disappeared. Retest the behavior that brought you to the command prompt in the first place.
Keep SFC in the toolbox. Just do not ask the screwdriver to diagnose the entire engine.