A single corrupted system file can turn a fast Windows 11 machine into a machine that crashes on boot, refuses to open Settings, or throws cryptic error codes at the worst possible moment. Microsoft’s built-in System File Checker exists precisely for that scenario, and it has been part of Windows for more than two decades. Yet in practice, most people run it wrong: they type the command into a normal window, get an error, and assume the tool is broken. It isn’t. The tool is strict about how it is launched, and once you know the rules, the whole repair takes about ten minutes of mostly waiting.
This guide walks through the exact steps, the messages you should expect, what to do when the scan reports it cannot fix something, and the mistakes that quietly waste people’s time.
What SFC /Scannow Actually Does
The System File Checker (sfc.exe) is a command-line utility that compares the protected core files of Windows against a known-good cached copy stored on your own drive. If it finds a file that is missing, altered, or corrupted, it swaps in the clean version. That cache lives in a compressed folder inside the Windows directory, which is why the repair works even without an internet connection.
Two limits matter. First, SFC only touches system files. It does not repair your personal documents, third-party drivers, or registry entries, and it is not an antivirus. If the underlying problem is malware, SFC may restore a file that the malware immediately corrupts again. Running a proper scan first is often the smarter order of operations, and a guide on how to check for viruses on a Windows PC covers that groundwork well.
Second, SFC repairs from a local cache. If that cache is itself damaged, the tool will report that it found problems but could not fix them. That is the moment the Deployment Image Servicing and Management tool, or DISM, enters the picture, and we will get to it shortly.
Before You Start: Three Quick Checks
Skipping these is the most common reason a scan “fails” before it even begins.
- Save your work and close heavy apps. The scan reads and writes protected system files. Having a video render or a game running in the background slows it down and occasionally causes a lock conflict.
- Plug in a laptop. A scan on a failing battery that shuts down mid-repair can leave files in a worse state than before.
- Free up a little disk space. The repair process needs room to stage replacement files. A drive with a few hundred megabytes left is asking for trouble.
None of this is exotic. It is the difference between a scan that finishes cleanly and one that stalls at 40 percent while you wonder whether to force a shutdown.
Step-by-Step: Running the Scan in Windows 11
Windows 11 changed one thing that trips people up: the default terminal. On many systems, right-clicking the Start button and choosing “Terminal” opens PowerShell, not Command Prompt. The sfc command works in either, but if you follow older instructions written for Command Prompt, the screens look different and confusion follows.
Here is the sequence that works reliably on Windows 11.
- Open the Start menu and type `cmd` or `Command Prompt`.
- Right-click the result and choose Run as administrator. Accept the User Account Control prompt.
- Confirm the window title says “Administrator: Command Prompt” (or “Administrator: Windows PowerShell” if you went that route).
- Type the command exactly: `sfc /scannow` — note the space after `sfc` and the forward slash.
- Press Enter and leave the window alone. Do not click inside it, do not close it, and do not run other maintenance tools at the same time.
- Wait. The scan typically reports progress in percentages and finishes somewhere between five and fifteen minutes on a healthy SSD. Older mechanical drives and badly damaged systems can take considerably longer.
When it completes, the window prints one of several standard messages and returns you to the prompt. Read it carefully, because the wording tells you what to do next.
Keyboard habits help here. If you spend a lot of time at the command line, the shortcuts in this roundup of Windows keyboard shortcuts everyone should know will speed up copying the result text out of the window. And if you fat-finger the command and need to clear the line, the undo shortcut key for Windows and Mac is worth having in muscle memory.
Reading the Four Possible Results
The scan ends in one of four states. Each one points to a different next step, and treating them all the same is where people go wrong.
| Result message | What it means | What to do next |
|---|---|---|
| Windows Resource Protection did not find any integrity violations | No corruption detected in protected files | Look elsewhere for the cause: drivers, updates, or malware |
| Windows Resource Protection found corrupt files and successfully repaired them | Repairs were made from the local cache | Restart and test whether the original problem is gone |
| Windows Resource Protection found corrupt files but was unable to fix some of them | The cache itself is likely damaged | Run DISM RestoreHealth, then re-run SFC |
| Windows Resource Protection could not perform the requested operation | The scan was blocked or interrupted | Reboot into Safe Mode or the recovery environment and retry |
The third message is by far the most common source of frustration. It does not mean the tool failed. It means the tool ran out of clean source material and needs a better supply.
When SFC Can’t Fix Things: The DISM Follow-Up
Microsoft’s own support documentation for the System File Checker points users toward the DISM repair command when SFC reports unfixable corruption. The logic is straightforward: DISM can pull fresh component files from Windows Update, rebuilding the very cache that SFC depends on. Once that cache is healthy, SFC has something clean to copy from.
The sequence is:
- Open an administrator Command Prompt or PowerShell window.
- Run `DISM /Online /Cleanup-Image /RestoreHealth` and wait for it to reach 100 percent.
- Restart the PC.
- Run `sfc /scannow` again.
In practice, this two-pass approach fixes a large share of cases that a lone SFC run could not. The DISM step needs an internet connection unless you point it at installation media, so make sure you are online before starting.
If both tools still come up short, the next escalation is running SFC from the Windows Recovery Environment or Safe Mode, where fewer system files are locked by running processes. Booting into recovery and opening a command prompt there lets the scan work on an offline Windows installation, which sidesteps file locks entirely.
Where the Real Details Hide: CBS.log
The on-screen summary is deliberately vague. The actual record of what was checked and what was repaired lives in a log file at `C:WindowsLogsCBSCBS.log`. Entries tagged with `[SR]` mark the System File Checker’s own activity, which makes them easy to filter.
Reading that log is not required for a routine repair, but it is genuinely useful when the same file keeps coming back as corrupt. A recurring entry usually means something outside Windows is rewriting that file on every boot, and no amount of scanning will fix a file that gets re-broken each time the machine starts.
A practical tip from people who do this often: copy CBS.log to your desktop before opening it, then search for `[SR]` in a plain text editor. The file can run to hundreds of megabytes on a long-lived installation, and opening it directly in Notepad on a slow drive is an exercise in patience.
Common Mistakes That Waste Time
A few habits reliably cause trouble, and they are easy to avoid once named.
Running the command without elevation. Typing `sfc /scannow` into a standard, non-administrator window produces an error or a scan that cannot repair anything. The window title is your proof that elevation worked.
Closing the window too early. The progress bar can sit at a single percentage for several minutes. That is normal. Killing the process mid-scan leaves the repair half-finished.
Assuming SFC is a malware remover. It is not. If a scan keeps finding the same corruption, the cause may be an infection or a failing drive. Free utilities exist for the malware side, and a list of the best free virus removal tools for Windows is a reasonable starting point. For hardware, check the drive’s SMART status before blaming software.
Ignoring the drive itself. If SFC repairs files successfully but the same errors return within days, the storage may be failing. No software tool fixes a disk that is physically dying.
Skipping the restart. Some repairs only take effect after a reboot. Testing the original problem before restarting tells you nothing useful.
Does SFC Fix Performance Problems?
Honestly, usually not. SFC is a correctness tool, not a tune-up. It restores files to their intended state; it does not clean up startup programs, remove temporary files, or speed up a slow machine. People often run it hoping for a performance boost and come away disappointed.
Where it genuinely earns its keep is in specific, reproducible failures: an app that crashes with a “missing DLL” error, Settings panels that refuse to open, Windows Update failing with certain error codes, or a system that blue-screens after a bad shutdown. In those cases, a clean scan result is valuable diagnostic information in itself, because it rules out corrupted system files and points the investigation toward drivers or third-party software.
For anyone who likes to tinker, the same command-line comfort transfers to other projects — running local language models, for instance, leans heavily on terminal skills, and a walkthrough on how to run AI models locally assumes exactly this kind of familiarity.
A Note on Documentation and Trust
Microsoft maintains an official support article titled “Use the System File Checker tool to repair missing or corrupted system files,” and it remains the primary reference for the command’s syntax and expected output. The broader Windows command reference on Microsoft Learn documents the additional switches, including `/verifyonly` for a read-only check and `/scanfile` for targeting a single file.
It is worth knowing that Microsoft does not publish a fixed runtime for the scan, so any specific number you see quoted online is anecdotal. The five-to-fifteen-minute figure above reflects typical SSD hardware, not an official benchmark. Treat timing claims with appropriate skepticism.
For background on how Windows has handled system integrity over the years, the Wikipedia entry on Windows provides useful context on the evolution of these built-in repair tools across versions.
Conclusion
Running `sfc /scannow` on Windows 11 is genuinely simple once you know the two non-negotiables: launch it from an elevated prompt, and give it time to finish. The command itself has not changed in years, and that stability is a feature. What has changed is the surrounding environment, particularly the shift toward PowerShell as the default terminal, which is why older instructions sometimes confuse newcomers.
The real skill is not typing the command. It is interpreting the result. A clean scan tells you to look elsewhere. A successful repair tells you to restart and retest. An “unable to fix” message tells you to run DISM and try again. And a scan that refuses to run at all tells you to drop into Safe Mode or the recovery environment. Follow that decision tree and the tool becomes what it was designed to be: a fast, reliable way to rule corruption in or out before you start reinstalling anything.
Frequently Asked Questions
How long does sfc /scannow take on Windows 11?
Most scans on a solid-state drive finish in roughly five to fifteen minutes. Slower drives, heavily damaged systems, or machines running other work in the background can take considerably longer. Microsoft does not publish an official duration, so treat any exact figure as a rough estimate rather than a guarantee.
Why does it say “could not perform the requested operation”?
That message almost always means the scan was blocked, interrupted, or launched without proper permissions. Close the window, reopen Command Prompt as administrator, and try again. If it persists, restart the PC and run the scan from Safe Mode or the Windows Recovery Environment, where fewer files are locked.
Do I need to run DISM before or after SFC?
Run SFC first. If it reports that it found corrupt files but could not repair them, then run `DISM /Online /Cleanup-Image /RestoreHealth`, restart, and re-run SFC. DISM rebuilds the repair cache that SFC copies from, so the order matters: fix the source, then repair the files.
Can sfc /scannow remove viruses?
No. The System File Checker restores protected Windows system files from a local cache. It does not detect or remove malware, and it will not clean infected user files. If you suspect an infection, run a dedicated antivirus scan as well, because SFC may restore a file that malware then corrupts again.
Is it safe to close the command window during the scan?
It is not advisable. Closing the window mid-scan interrupts the repair and can leave files partially replaced. The progress indicator sometimes sits at one percentage for several minutes, which is normal behavior rather than a freeze. Let it reach the end and print its final message.
What should I do if the same files keep getting corrupted?
Recurring corruption on the same files points to something outside Windows rewriting them, or to failing storage. Check the drive’s health with a SMART monitoring tool, run a full malware scan, and review the `[SR]` entries in CBS.log to identify which files are affected. If repairs succeed but the problem returns within days, hardware is the more likely culprit than software.
