How to Repair Corrupted Windows Files with SFC and DISM

Missing DLL errors, a broken Start menu, sudden Windows Explorer crashes, or Windows Update error codes (like 0x800f081f) are classic hallmarks of corrupted system files. Rather than reinstalling Windows from scratch, you can deploy the native repair tandem: DISM and SFC.

Why You Need Both DISM and SFC (The Common Mistake)

Most users simply run sfc /scannow and give up when it reports: "Windows Resource Protection found corrupt files but was unable to fix some of them."

Here is why that happens: SFC checks Windows files against a local cache located at %WinDir%\System32\WinSxS (the Component Store). If the local WinSxS store itself has corrupted bits or missing manifests, SFC has no clean source from which to copy!

The Golden Rule of Windows Repair

Always run DISM first to repair the local WinSxS component store from Microsoft's cloud servers. Then run SFC to replace files in your active Windows installation.

Step 1: Open Terminal / Command Prompt as Administrator

Both tools require root NT kernel privileges to touch protected system directories:

Press Win + X on your keyboard.
Select Terminal (Admin) or Command Prompt (Admin).
Click Yes when prompted by User Account Control (UAC).

Step 2: Run the DISM Component Store Repair

Execute the command below to inspect and restore the health of your Windows image:

Command Prompt (Admin)

DISM /Online /Cleanup-Image /RestoreHealth

What happens during this scan: DISM connects to Windows Update servers over your internet connection, downloads pristine hash-verified manifests, and rebuilds any damaged binaries inside C:\Windows\WinSxS. This typically takes 5 to 15 minutes. Wait until you see: "The restore operation completed successfully."

Step 3: Run the System File Checker (SFC)

Now that your WinSxS component store is 100% healthy, run SFC to repair your active system files:

Command Prompt (Admin)

sfc /scannow

Step 4: Interpreting SFC Results

When the scan hits 100%, you will receive one of three messages:

Scan Outcomes

            1. "Windows Resource Protection did not find any integrity violations."

            → Your core operating system files are intact.

            2. "Windows Resource Protection found corrupt files and successfully repaired them."

            → Corrupted system DLLs have been replaced with healthy copies.

            3. "Windows Resource Protection could not perform the requested operation."

            → Windows cannot modify a locked file in live mode. Reboot into Safe Mode and run SFC again.

Step 5: How to Inspect Which Files Were Repaired

SFC logs every single file action to C:\Windows\Logs\CBS\CBS.log. To filter out only the repaired files without reading megabytes of log files, run:

Command Prompt (Admin)

            findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
          

This generates a clean sfcdetails.txt file on your desktop detailing every replaced DLL.

Step 6: Restart Your PC

Always reboot your computer after running both DISM and SFC so the Windows kernel can swap out any locked files during the pre-boot initialization phase.