SFC Scannow Windows 11 is the built-in System File Checker command for checking protected Windows files. It scans them and attempts to repair corrupted versions when possible.
Microsoft recommends running DISM before System File Checker. Open an elevated terminal, run DISM.exe /Online /Cleanup-image /Restorehealth, then run sfc /scannow and keep the window open until verification reaches 100%.
FREE TOOL FOR THIS TOPIC
Windows Help Navigator
Built specifically for readers of SFC Scannow Windows 11: How to Run It and Fix Errors. Answer four quick questions to receive a focused result immediately—no email required.
Windows Help Navigator
Choose the fastest support path for a common Windows problem.
Continue building your career
Use another free CareersForge resource to turn this result into your next application, resume or interview step.
This guide explains the exact Windows 11 command, what each Windows Resource Protection result means, and what to do when SFC cannot finish, cannot repair files, or the PC will not boot.
You need an administrator account to repair protected files. Keep a current backup of important data before attempting broader recovery or reinstall steps.
For broader steps, see our How to Get Help in Windows guide. SFC is useful when protected Windows files may be damaged, but it cannot diagnose every crash or hardware problem.
Table of Contents
Why corrupted system files happen in Windows 11 and what SFC can fix
Before you run any repair tool, it helps to know why system files go bad.
Unexpected shutdowns, interrupted updates, storage errors, or malware can be associated with Windows problems, but symptoms alone do not confirm system-file corruption.
SFC scans protected Windows system files and attempts to replace corrupted versions with cached copies. It can help with file-integrity problems, but it does not diagnose every crash or hardware fault.
How resource protection reports integrity problems
Windows Resource Protection watches critical files and blocks casual changes. After a scan it reports whether it could find integrity violations and whether repairs succeeded.
When the component store needs repair, Microsoft recommends running DISM before SFC; the steps appear below.
Signs you may have a corrupted system
- Random app crashes or Settings acting oddly.
- Features fail to open, updates keep failing, or repeated blue screens.
- Messages about found corrupt files or protection find integrity in logs.
SFC addresses protected Windows files. It does not repair failing storage, drivers, or every cause of system instability.
Before you start: prep steps for running System File Checker safely
Before you start, save open work and make sure important files are backed up. Open an elevated console, and do not close it before verification reaches 100%.
Open an elevated command prompt: search for “cmd”, right-click Command Prompt, then choose Run as administrator. A UAC prompt may ask for approval.
If you prefer PowerShell (Admin) or Windows Terminal (Admin), those work the same. You don’t need the classic black box; you need elevation so the tool can replace protected system files.
How to run the console and what to expect
- Fast ways: Start search for cmd, or use Win+X and select an admin option.
- Type the repair command carefully, then press enter once and let it run.
- Progress may be slow. Microsoft instructs users to keep the Command Prompt window open until verification reaches 100%.
- Save open files, avoid restarts, and keep your desktop visible so you can watch completion.
Microsoft says the DISM operation may take several minutes; the actual duration varies by device and repair source. Allow it to finish before closing the window.
Method: Run DISM first to repair the Windows image component store
Microsoft recommends running DISM before SFC because DISM can supply files needed to repair protected system files. Start with this elevated command:
Run DISM RestoreHealth using Windows Update as the source:
Open an elevated prompt and type the command below, then press Enter:
DISM.exe /Online /Cleanup-image /Restorehealth
If Windows Update is blocked or broken, use a local repair source instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Here’s what each part means: /Online targets your running image, /RestoreHealth applies fixes, and /Source points to local recovery files when needed.
DISM often downloads components via Windows Update, so a stable internet connection speeds the repair. Timing varies—sometimes a few minutes, sometimes much longer on older machines.
The command may appear to pause while it works. Allow it to complete rather than closing the window.
If SFC reports that it could not repair some files, run DISM RestoreHealth, restart if prompted, and run SFC again. If Windows Update cannot supply source files, you may need a compatible local repair source.
Method: Run SFC Scannow Windows 11 from an elevated console
Run SFC from an elevated Command Prompt, PowerShell, or Windows Terminal. Administrator permissions are needed to repair protected files.
The exact one-liner: type sfc /scannow, then press Enter and wait. Run it in Command Prompt, PowerShell, or Windows Terminal — any elevated prompt works.
SFC checks protected Windows files and attempts to replace corrupted versions with cached copies when possible.
Keep the console open until verification reaches 100%. When SFC finishes, follow the exact Windows Resource Protection message shown in the results section below.
Restart if Windows requests it or if the original issue remains, then check whether the same symptoms continue.
| Command | Where to run | Primary action | Next step |
|---|---|---|---|
| sfc /scannow | Elevated Command Prompt or PowerShell | Scan protected files and replace corrupted copies | Reboot if repairs applied |
| Tip | Any admin prompt | Don’t close before 100% completes | Check logs if issues persist |
How to interpret SFC results: Windows Resource Protection messages explained
Use the exact Windows Resource Protection message to choose the next step; the explanations below separate a clean scan from a successful repair and an unresolved error.
Windows Resource Protection did not find any integrity violations
This means core system files passed the check. Next, look at drivers, disk health, apps, or updates as likely culprits.
Windows Resource Protection found corrupt files and successfully repaired them
Good news. Reboot and test the issue that sent you here. Many problems clear after a restart.
Windows Resource Protection found corrupt files but was unable to fix some of them
Here you should review the CBS.log at %Windir%\Logs\CBS\CBS.log. Try a component-store repair, then rerun the scan or use Safe Mode for an unlocked attempt.
Windows Resource Protection could not perform the requested operation
For this message, Microsoft recommends running the SFC scan in Safe Mode and checking that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.
Pro tip: CBS.log is the factual record—use it before assuming the worst. These messages guide next steps, not final judgments.
📚 Read Next
If SFC could not repair files, see our DISM RestoreHealth Windows 11 guide for the next supported repair step.
For the broader Windows 11 troubleshooting sequence, see our Windows 11 troubleshooting guide or return to How to Get Help in Windows.
Official references: Microsoft’s SFC and DISM repair steps and the SFC command reference.
| Message | What it means | Next step |
|---|---|---|
| Did not find any integrity violations | System files OK | Check drivers, disk, or apps |
| Found corrupt files — repaired | Repairs applied | Reboot and retest |
| Found corrupt files — unable to fix | Partial repairs logged | Review CBS.log, run component repair |
| Could not perform requested operation | Files locked or pending | Try Safe Mode; verify Temp folders |
Why Is SFC /scannow Not Working or Stuck in Windows 11?
If SFC reports that it could not perform the requested operation, Microsoft recommends trying the scan in Safe Mode. That step addresses this specific error; it is not a fix for every slow-looking scan.
Why Safe Mode helps
Safe Mode starts with a minimal set of drivers and services. That reduces file locks and lets the scan access protected files.
Check the Temp folders the repair uses
Before you rerun the command, verify PendingDeletes and PendingRenames exist under %WinDir%\WinSxS\Temp (for example, C:\Windows\WinSxS\Temp). Missing temp paths can block fixes.
- Boot into Safe Mode from advanced startup.
- Open an elevated command prompt and run the same scan command you used earlier.
- Reboot back into normal mode after a successful run and confirm the original issue is resolved.
| Problem | Why Safe Mode helps | Action |
|---|---|---|
| Resource protection could not perform operation | Files locked by drivers or services | Boot Safe Mode → verify Temp folders → run command in elevated prompt |
| Pending file operations blocking repair | Missing PendingDeletes/PendingRenames | Create or restore Temp folders → rerun scan → reboot |
Method: Run SFC offline using Windows Recovery Media for unbootable PCs
If Windows will not start, SFC supports an offline scan from Windows Recovery Environment. First identify the actual boot and Windows volumes; their letters may differ from the ones used during normal startup.
How to reach the prompt: boot from recovery media, choose Repair your computer, pick Troubleshoot, then Advanced options → Command Prompt.
After confirming the correct volumes, use the matching paths in this command template:
sfc /scannow /offbootdir=<boot directory> /offwindir=<Windows directory>
In Windows Recovery Environment, drive letters can change. Verify which volume contains the Windows folder and boot files before replacing the placeholders; do not assume the installation is on C:.
The scan may take several minutes or longer. Keep the recovery console open until it finishes, then restart and check the result.
| Step | Action | Why it matters |
|---|---|---|
| Boot recovery | Repair your computer → Troubleshoot → Advanced options → Command Prompt | Gives offline access when the system won’t start |
| Confirm drive | Use diskpart list vol or dir to find the correct volume | Avoid scanning the wrong partition |
| Run command | sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows | Targets and repairs the offline installation |
| Wait & reboot | Allow up to an hour, then restart | Reboot applies repairs and may restore boot |
Which SFC options are supported in Windows 11?
For Windows 11, Microsoft documents these SFC options. Run them from an elevated terminal. The current reference does not list the older /scanonce, /scanboot, /cancel, or /enable switches as supported Windows 11 commands.
sfc /scannowscans all protected system files and attempts repairs.sfc /verifyonlychecks protected system files without repairing them.sfc /scanfile=<full path>scans and attempts to repair one specified file.sfc /verifyfile=<full path>checks one specified file without repairing it.- For an offline installation, add
/offbootdir=<boot directory>and/offwindir=<Windows directory>to the appropriate scan command after confirming both paths.
How do I fix corrupt files in Windows 11 after running SFC /scannow?
When SFC finds corrupt files but cannot repair some of them, the result is a diagnostic step—not a reason to replace DLLs manually right away.
To extract SFC entries from the CBS log, open an elevated Command Prompt and run findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt". Check the timestamps in sfcdetails.txt so you read entries from the latest scan.
Retry the repair loop
Run DISM.exe /Online /Cleanup-image /Restorehealth, let it finish, restart if prompted, and run sfc /scannow again. Review the new result before trying another repair.
Why manual file replacement needs extra care
Avoid replacing protected system files with DLLs downloaded from third-party sites. Manual replacement changes Windows files and should only be attempted with verified Microsoft guidance, a known-good source, and a backup; if you are unsure, use Windows recovery options or ask a qualified technician.
Repair Windows before considering a clean install
If DISM and SFC still fail, Windows 11 may offer a repair reinstall under Settings → System → Recovery → Fix problems using Windows Update → Reinstall now. Availability depends on the device. Read Microsoft’s repair-reinstall guidance and back up important data before any recovery that may remove files or apps.
| Issue | Action | Why |
|---|---|---|
| Found corrupt files — unable fix | DISM RestoreHealth → reboot → run scan | Refresh component store so repair can succeed |
| Specific file failing | Create sfcdetails.txt from CBS.log and review the latest entries; consult Microsoft Support | Avoid replacing protected files without verified guidance |
| Persistent corruption | Clean install / recovery | Restore system stability when repairs fail |
Conclusion
For most Windows 11 SFC repairs, follow this order: run DISM, run sfc /scannow from an elevated terminal, read the exact result, and use Safe Mode or an offline scan only when the error calls for it.
The next step depends on the exact result—not on repeating the same command without addressing the message Windows displayed.
Use the command prompt or Windows Terminal to give the system permission to repair itself. After repairs complete, reboot and check whether the original issue still happens.
If the issue keeps returning, review Windows Update and storage health, then use supported Windows recovery options. Back up important data before a reset or clean installation.
FAQ
What does the system file checker tool actually do?
Why do protected system files become corrupted?
How do I run the checker safely from an elevated console?
What should I do before I run a repair scan?
When should I run a DISM health repair first?
What if Windows Update can’t be used as the repair source?
How long will image repairs or scans take?
What do the different resource protection messages mean?
If some files are “unable to fix,” what next?
Why run the checker in Safe Mode?
How do I run an offline scan when the PC won’t boot?
Can I schedule different types of scans or cancel pending ones?
Where do I find the detailed log that shows which files failed repair?
When should I consider a clean install?
Rodrigo Durães is the founder and editor of CareersForge, where he publishes career-development resources on career planning, resumes, interviews, and job search. His professional experience and education are listed on his LinkedIn profile, including his role as Global CEO of VisionCorp International from 2011 to 2023. View Rodrigo’s LinkedIn profile.