Learning how to fix corrupted system files using SFC is one of the most useful skills a Windows user can pick up, especially when the operating system starts acting unstable for no obvious reason. The System File Checker tool scans protected Windows files and replaces any that are damaged or missing. This guide walks through the entire process from start to finish, including what to do when the scan finds problems it cannot repair on its own.
Key Takeaways
- SFC (System File Checker) scans and repairs corrupted or missing Windows system files automatically.
- The command must be run from an elevated Command Prompt or PowerShell window.
- A full scan typically takes several minutes, depending on drive speed and system size.
- If SFC cannot fix an issue, running DISM first often clears the way for a successful repair.
- A restart after the scan completes helps finalize any repairs that were made.
How to Run an SFC Scan to Fix Corrupted System Files
The process itself is simple, but each step matters. Skipping the elevated permissions step, for example, is the most common reason the scan fails before it even starts.
- Step 1: Open the Start menu, type ‘Command Prompt’ or ‘PowerShell’, then right-click the result and choose ‘Run as administrator’. Approve the User Account Control prompt if it appears.
- Step 2: In the elevated window, type sfc /scannow and press Enter. Note that quotation marks are never part of the command itself.
- Step 3: Let the scan run without closing the window or restarting the PC. The progress percentage updates as the scan works through protected system files.
- Step 4: Once finished, read the message that appears. It will report one of a few outcomes: no integrity violations found, violations found and repaired, or violations found that could not be repaired.
- Step 5: Restart the computer regardless of the outcome. Some repairs only take effect after the next boot.
- Step 6: If SFC reported that it could not fix everything, run DISM with the command DISM /Online /Cleanup-Image /RestoreHealth, then repeat the SFC scan afterward.
Tip: Running DISM before SFC, rather than after, often saves a step. DISM repairs the underlying Windows component store that SFC pulls clean file copies from, so a healthy component store gives SFC a better chance of success on the first pass.
Checking the Scan Results Log
For a closer look at exactly what SFC found and fixed, the CBS log holds the details. Open an elevated Command Prompt and run findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log > “%userprofile%\Desktop\sfcdetails.txt”, then open the resulting text file on the desktop. Lines marked with ‘SR’ relate directly to the System File Checker’s activity and show which specific files were flagged.
Common Problems and Fixes
Windows Resource Protection Could Not Perform the Requested Operation
This message usually points to a service that has not started correctly. Open the Services app, confirm that Windows Modules Installer is running, then try the scan again from an elevated window.
SFC Finds Corrupted Files but Cannot Fix Them
This is the scenario where DISM becomes necessary. Run the DISM RestoreHealth command described in Step 6, wait for it to finish, and then run sfc /scannow a second time. Most cases resolve after this combination.
The Scan Seems Stuck at a Certain Percentage
SFC can pause for a noticeable stretch at certain points, particularly around 30 percent and 60 percent, as it works through larger file sets. This is normal behavior in most cases. Give it at least 15 to 20 minutes before assuming it has frozen.
DISM Cannot Reach the Restore Health Source
DISM sometimes needs an active internet connection to pull replacement files from Windows Update. If it fails, check the network connection first. Where internet access is not available or reliable, a Windows installation disc or a matching Windows image (ISO) mounted locally can serve as an alternate source for the repair files.
Errors Continue After Multiple SFC and DISM Attempts
When repeated scans do not resolve the problem, deeper file system corruption or a failing drive may be involved. Running CHKDSK to check the disk for errors is a reasonable next step. If problems persist after that, a repair install or clean install of Windows becomes the more reliable option.
Frequently Asked Questions
What does the SFC command actually do?
SFC scans all protected system files, compares them against a known-good cached version, and replaces any file that appears corrupted, altered, or missing.
How long does an SFC scan usually take?
Most scans finish within 10 to 20 minutes, though slower drives or systems with a large number of installed features can take longer.
Is it safe to interrupt an SFC scan partway through?
Interrupting the scan is not recommended. Closing the window or shutting down mid-scan can leave the repair process incomplete and may require running the scan again from the start.
Does SFC require an internet connection?
No. SFC pulls replacement files from a local cache stored on the system, so it works without internet access. DISM, on the other hand, may need a connection depending on the repair source used.
What is the difference between SFC and DISM?
SFC repairs individual system files using a local cache. DISM repairs the Windows component store itself, which is the source SFC relies on. When SFC alone cannot fix a problem, it is often because the component store needs DISM’s attention first.
Can SFC fix a computer that will not boot into Windows?
SFC needs a running instance of Windows to work in the way described here. For a system that will not boot, the same repair can be run from the Advanced Startup options using Command Prompt, or from a bootable Windows installation drive using the offline repair syntax.
What does it mean if SFC reports no integrity violations?
This means the scan found no corrupted or missing system files at the time it ran. If symptoms persist despite this result, the cause likely lies outside the system files SFC checks, such as a driver conflict or a failing hardware component.
Should SFC be run regularly as routine maintenance?
Running it occasionally does no harm, but it is primarily a troubleshooting tool rather than a scheduled maintenance task. It is most useful after a crash, an unusual error, or after installing something that may have altered system files.
Why does the CBS log show entries that are not related to the current scan?
The CBS log accumulates entries over time from previous scans and system servicing events. Filtering for the most recent timestamps in the log helps isolate results from the latest scan specifically.
