Fix Windows Resource Protection Error (SFC)

That error is a pain—you're just trying to repair corrupted system files, and Windows throws another problem at you. Let's get it fixed.

First Fix: Run DISM to Repair the Component Store

The most common reason SFC fails with this error is that the component store (the backup of system files it checks against) is corrupted. So you have to repair that store first.

Right-click the Start button and select Windows Terminal (Admin) or Command Prompt (Admin). If you're on Windows 11, it might say Windows PowerShell (Admin).
Click Yes when the User Account Control prompt appears.

Type this command and press Enter:

DISM /Online /Cleanup-Image /RestoreHealth

You'll see a progress bar that might stall at 20% or so for a while. That's normal. Let it run—it can take 15 to 30 minutes, sometimes longer on an older system. When it finishes, you'll see a message that says "The restore operation completed successfully" or "The component store corruption was repaired."

After that, run SFC again:

Type sfc /scannow and press Enter.

This time it should run to completion. It'll either find and fix problems, or tell you it didn't find any integrity violations. Either way, you won't see that error again—unless the underlying issue is different.

Why This Works

Think of SFC as a health inspector that checks your system files against a reference copy stored in the Windows component store. If that reference copy is damaged or missing, SFC throws its hands up and gives you that error. DISM is the tool that repairs the component store itself. It uses Windows Update as the source for fresh files. So when you run DISM first, you're fixing the foundation so SFC can do its job.

Variations and Less Common Fixes

Sometimes the DISM command above doesn't work. Here are the next steps to try in order.

If DISM Fails with Error 0x800f0906 or Similar

That means DISM couldn't reach Windows Update to get the files. You'll need to give it a local source:

Download the Windows 10 or 11 ISO matching your version from Microsoft's website. You don't need to install it—just mount it by double-clicking the ISO file, which will assign it a drive letter (like E:).
Note the drive letter and the Windows edition you're running (Home, Pro, etc.).

Run this command, replacing E: with your drive letter:

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

If you have a multi-edition ISO, you might need to specify the index number. For example:
```
DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim:1 /LimitAccess
```
But most home users can skip this unless the command fails.

Wait—I need to tell you something important. If your system is Windows 11, the file might be called install.esd instead of install.wim. In that case, use the .esd extension in the path. The command works the same.

If DISM Succeeds but SFC Still Fails

Rare, but possible. The culprit might be a pending reboot flag or a corrupted SFC cache. Try this:

Restart your computer (yes, a full shutdown and power-on, not just a restart from the Start menu—that closes all processes cleanly).
Boot into Safe Mode. The easiest way: press Windows + R, type msconfig, go to the Boot tab, check Safe boot, and click OK. Restart. (Don't forget to uncheck it later.)
In Safe Mode, open Command Prompt as admin and run sfc /scannow.

Safe Mode loads only the bare minimum drivers and services. That removes most interference from third-party software that could be blocking SFC.

If You're on Windows 10 1903 or Earlier (Unlikely Now, but…)

There was a known issue where SFC failed on systems that had certain updates installed. The fix was to uninstall a specific update (KB4512941 or similar). But if you're running Windows 10 version 2004 or later, skip this—it doesn't apply to you.

Prevention

Now that it's fixed, you want to keep it from happening again. The biggest culprit is corruption in the component store, and that often comes from forced shutdowns or power loss. So:

Use the Shut down option in Windows, not the physical power button, especially after updates.
Keep your system updated. DISM and SFC rely on the latest files from Windows Update, and having an outdated system can cause mismatches.
Run DISM /Online /Cleanup-Image /StartComponentCleanup occasionally (like every few months) to clean up old versions of updated components. That keeps the store from bloating and getting corrupted.

If you see this error again after a major update, just re-run the DISM command first. It's fast if the store is healthy—it'll take less than a minute and say "No component store corruption detected." Then SFC will run fine.

That's the whole fix. It's not glamorous, but it works.