sfc scannow system file checker

To run the sfc scannow system file checker, open Command Prompt as administrator, type sfc /scannow, and press Enter. That single command scans every protected Windows system file and replaces corrupted ones automatically. It takes 5 to 15 minutes. If it reports files it cannot fix, you need DISM first, and this guide covers exactly that.

What Causes Windows System File Corruption?

Most of the corrupted-file jobs that come through our remote support queue trace back to one of five things. Knowing which one applies to your machine helps you pick the right tier of fix without wasting time on steps that will not work.

The most common cause by far is a damaged WinSxS component store. The WinSxS folder (located at C:\Windows\WinSxS) is where Windows keeps known-good reference copies of every protected system file. When SFC needs to replace a corrupted file, it pulls the clean version from there. If WinSxS itself is damaged, usually from an interrupted Windows Update or a failed servicing operation, SFC cannot find the replacement and gives up. That is exactly when you see the dreaded 'Windows Resource Protection found corrupt files but was unable to fix some of them' message.

Disk-level problems are the second big one. Bad sectors on a spinning hard drive, or NTFS file system errors on any drive, can corrupt files silently over time. A forced shutdown mid-write is a classic trigger, especially on laptops that get closed with updates still running. If you suspect the disk, run chkdsk C: /f /r from an elevated Command Prompt before touching SFC. There is no point repairing system files if the drive is going to corrupt them again an hour later.

Malware is another regular culprit. Some strains specifically target system files to disable Windows Defender or prevent removal. If you have any reason to suspect infection, scan the machine with a reputable security tool before running SFC. Repairing files that malware will immediately re-corrupt is just going in circles. For cases where files have been deleted rather than corrupted, file recovery software may be needed alongside SFC to restore what is missing.

Power loss during a Windows Update or a servicing operation is the final common cause. The component store gets written to during updates, and if power drops mid-write you can end up with a half-updated, half-broken store. A UPS on desktops and keeping laptops plugged in during updates prevents this entirely.

SFC Scannow System File Checker: Quick Fix

This is the right starting point for most people. It works in the majority of cases where the component store is healthy and the corruption is limited to a handful of individual files. The whole process takes under 15 minutes on a modern SSD-based machine.

One thing worth flagging: if you are running Windows in a corporate environment with Group Policy restrictions, SFC may be blocked from writing to certain protected locations. In that case, contact your IT department or run the offline repair method covered in the Advanced section.

SFC Scannow System File Checker: Intermediate Fix with DISM

This is the fix Microsoft explicitly recommends when SFC cannot repair files on its own. The logic is simple: SFC cannot replace files if its source (the WinSxS component store) is corrupted. DISM goes out to Windows Update, downloads known-good components, and rebuilds the store. Once that is done, SFC has what it needs to finish the job.

According to Microsoft's official SFC documentation, running DISM before SFC is the recommended sequence for persistent corruption. A lot of guides online skip this step and wonder why SFC keeps failing.

You can also run two optional DISM diagnostic commands before RestoreHealth if you want more detail on the state of the component store. DISM.exe /Online /Cleanup-image /CheckHealth does a quick flag check (takes seconds). DISM.exe /Online /Cleanup-image /ScanHealth does a thorough scan (can take 10 to 20 minutes). Neither of these repairs anything on their own. They just tell you how bad the damage is. Most of the time you can skip straight to RestoreHealth.

The Microsoft DISM image repair documentation covers all the available switches in detail if you want to go deeper on what each command actually does under the hood.

Advanced SFC Scannow System File Checker Fixes

These are the methods we reach for when the standard SFC plus DISM sequence has not sorted things. They are more involved, but they handle cases that the basic approach simply cannot touch, including machines that will not boot and individual files that SFC keeps flagging but cannot replace.

If none of the above clears the corruption, the next step is an in-place upgrade repair. Boot from Windows installation media, choose Upgrade, and select to keep files and apps. This reinstalls all Windows components from scratch while leaving your data and installed applications intact. It is a proper fix, not a workaround, and it is what we recommend to customers when SFC and DISM have both been exhausted. As a last resort after that, Settings > System > Recovery > Reset this PC with the option to keep personal files will get Windows back to a clean state.

The full SFC command reference on Microsoft Learn documents every available switch including the offline options, which is handy if you are scripting repairs across multiple machines.

Preventing Windows System File Corruption

Most of the corruption cases we see are avoidable. Here are the things that actually make a difference, in order of importance.

Let updates finish. The single biggest cause of component store damage is a Windows Update that got interrupted. Never force-restart a machine mid-update, and keep laptops plugged in during update installs. If an update has been sitting at 30% for two hours, wait. Killing it will likely cost you an hour of DISM repair later.

Sort your disk health. Run chkdsk C: /f /r periodically, especially on machines that are a few years old. Check SMART status with a free tool like CrystalDiskInfo. A drive that is starting to fail will corrupt files long before it dies completely, and SFC will keep finding new problems every time you run it.

Use proper security software. Malware that targets system files is a real thing. Keep a reputable, actively updated security product running. Avoid the cheap or free tools that do not get regular signature updates. The AV-TEST and AV-Comparatives independent testing labs publish regular benchmarks if you want objective data on which products actually catch threats before they can touch system files.

Stay away from system optimizer tools. A lot of the worst component store damage we see comes from third-party tools that claim to clean or speed up Windows. They poke around in places they should not, delete files they misidentify as junk, and leave the WinSxS store in a state that DISM struggles to repair. If a tool promises to make Windows faster by cleaning the registry or deleting system files, uninstall it.

Back up before you need to. Set up System Restore points (they are on by default but worth confirming in System Properties > System Protection) and run periodic full image backups. If corruption is severe enough that SFC, DISM, and an in-place repair all fail, a clean image backup from a week ago is worth more than any command-line tool.

SFC Scannow System File Checker: Summary

The sfc scannow system file checker is one of the most useful built-in Windows tools, and it fixes the majority of system file corruption problems without needing any third-party software. Start with a simple sfc /scannow from an elevated Command Prompt. If that cannot repair everything, run DISM.exe /Online /Cleanup-image /Restorehealth first to fix the component store, then rerun SFC. For machines that will not boot, the offline /offbootdir and /offwindir switches let you run the sfc scannow system file checker against a non-running Windows installation from the recovery environment. Check %windir%\Logs\CBS\CBS.log whenever you need more detail than the on-screen summary provides. And if all else fails, an in-place upgrade repair is the clean, reliable way to get Windows back to a healthy state without losing your files.