Windows Resource Protection Could Not Start the Repair Service: 5 Fixes

Have you ever tried to fix a Windows problem using the “sfc /scannow” command — only to get a frustrating error message? Specifically, this one:

“Windows Resource Protection could not start the repair service.”

It’s annoying. Especially when you were trying to fix something else entirely.

The good news? This error is fixable. In fact, most users can resolve it in just a few minutes. In this guide, you’ll find 5 proven fixes — explained in plain English, step by step.

Let’s get into it.

What Does “Windows Resource Protection Could Not Start the Repair Service” Mean?

Before fixing anything, it helps to understand what’s going on.

What Is Windows Resource Protection (WRP)?

Windows Resource Protection is a built-in Windows feature. Its job is to protect critical system files from being changed or corrupted. When something goes wrong, you can run the System File Checker (SFC) tool to scan and repair those files.

Think of WRP as Windows’ own self-healing system.

What Triggers This Error?

This error appears when the SFC tool tries to run — but can’t. The most common reasons include:

• The Windows Modules Installer service is stopped or disabled
• Corrupted system files are blocking the repair process
• A recent Windows Update caused a conflict
• Malware or third-party software interfered with system services
• The Windows image itself is damaged

In short, something is preventing Windows from starting its own repair engine.

Also Check: Why Does My Computer Keep Crashing?

Why You Should Fix This Error Immediately

You might be tempted to ignore this error. After all, your PC still works — right?

But here’s the thing. If Windows can’t run its repair service, your system is more vulnerable. Corrupted files can pile up over time. This leads to crashes, slow performance, and even the dreaded Blue Screen of Death (BSOD).

Additionally, leaving this error unresolved can make future Windows updates fail. That’s a bigger problem than it sounds — especially for security patches.

So yes, it’s worth fixing now rather than later.

Fix 1 — Restart the Windows Modules Installer Service

This is the first thing you should try. It works for most users.

Why This Works

The Windows Modules Installer service (also called “TrustedInstaller”) is what SFC depends on to run repairs. If this service is stopped or set to “Manual,” SFC simply can’t do its job.

Step-by-Step Instructions

1. Press Windows + R to open the Run dialog.
2. Type services.msc and press Enter.
3. Scroll down and find Windows Modules Installer.
4. Right-click it and select Properties.
5. Under Startup type, choose Automatic.
6. Click Start if the service isn’t running.
7. Click Apply, then OK.
8. Now open Command Prompt as Administrator and run sfc /scannow.

That’s it. In many cases, this single fix solves the problem completely.

💡 Practical Tip: While you’re in Services, also check that Windows Update and Cryptographic Services are both set to “Automatic.” These three services often work together.

Fix 2 — Run SFC Scan in Safe Mode

Sometimes, background apps or processes block the SFC tool from running. Safe Mode strips those away — giving SFC a clean environment to work in.

How to Boot Into Safe Mode

1. Press Windows + I to open Settings.
2. Go to System → Recovery.
3. Under Advanced startup, click Restart now.
4. After restart, select Troubleshoot → Advanced options → Startup Settings.
5. Press F4 to boot into Safe Mode.

Running SFC from Safe Mode

Once in Safe Mode:

1. Press Windows + S and search for Command Prompt.
2. Right-click it and choose Run as administrator.
3. Type sfc /scannow and press Enter.
4. Wait for the scan to complete — this can take 10–20 minutes.
5. Restart your PC normally when done.

Safe Mode removes interference from third-party software. So if Fix 1 didn’t work, this one often does.

Fix 3 — Use DISM to Repair Windows Image

If SFC still fails, the problem may be deeper. The Windows image itself might be corrupted. That’s where DISM comes in.

What Is DISM?

DISM stands for Deployment Image Servicing and Management. It’s a powerful command-line tool built into Windows. Unlike SFC, DISM can fix the source files that SFC relies on.

Think of it this way — SFC fixes your files, but DISM fixes SFC’s toolkit.

Step-by-Step DISM Commands

1. Open Command Prompt as Administrator.
2. First, run this command to check for issues:

DISM /Online /Cleanup-Image /CheckHealth

3. Then run this to scan for corruption:

DISM /Online /Cleanup-Image /ScanHealth

4. Finally, run this to repair the image:

DISM /Online /Cleanup-Image /RestoreHealth

This process can take 15–30 minutes. Don’t close the window while it runs.

1. Once complete, restart your PC and run sfc /scannow again.

💡 Practical Tip: Make sure you’re connected to the internet before running DISM. It sometimes downloads repair files directly from Windows Update servers.

Fix 4 — Check and Fix Windows Update Components

Sometimes, broken Windows Update components cause this error. Resetting them can clear the blockage quickly.

Why Windows Update Matters Here

The SFC repair service is closely tied to Windows Update infrastructure. If update components are corrupted or stuck, they can prevent the repair service from starting.

Step-by-Step Instructions

1. Open Command Prompt as Administrator.
2. Stop the relevant services by running these commands one by one:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

3. Rename the corrupted update folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

4. Restart the services:

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. Restart your PC and try running sfc /scannow again.

This fix essentially gives Windows Update a fresh start. It’s a common solution for several Windows repair-related errors.

Fix 5 — Perform a System Restore or Repair Install

If none of the above fixes work, it’s time for a more powerful approach.

When to Use This Fix

Use this fix when:

• Your system files are severely corrupted
• The error appeared after a major Windows update or software installation
• All previous fixes have failed

Option A: System Restore

If you have a restore point saved:

1. Press Windows + S and search for Create a restore point.
2. Click System Restore.
3. Choose a restore point from before the error started.
4. Follow the on-screen instructions.

This rolls back your system without deleting personal files.

Option B: Windows Repair Install (In-Place Upgrade)

This reinstalls Windows while keeping your files and apps intact.

1. Download the Windows Media Creation Tool from Microsoft’s official website.
2. Run the tool and select Upgrade this PC now.
3. Follow the prompts and choose Keep personal files and apps.
4. Let Windows reinstall itself over the existing installation.

This is one of the most effective fixes for deep system corruption. And importantly, you won’t lose your data.

SFC vs DISM — Which One Should You Use First?

Many users wonder which tool to run first. Here’s a simple breakdown:

Feature	SFC	DISM
Purpose	Repairs individual system files	Repairs the Windows image
Internet needed?	No	Sometimes yes
Speed	Faster (10–20 min)	Slower (15–30 min)
Use first?	✅ Yes	Only if SFC fails
Works offline?	Yes	Partially

The recommended order:

1. Try SFC first
2. If SFC fails, run DISM
3. Then run SFC again after DISM completes

This combination solves the vast majority of system file issues on Windows.

Frequently Asked Questions (FAQs)

What is the repair service in Windows?

The repair service refers to the Windows Modules Installer (TrustedInstaller). It’s the background service that allows SFC and Windows Update to install, modify, or repair system files.

Can I ignore this error?

Technically yes — but it’s not recommended. Over time, unrepaired system file corruption can cause crashes, performance issues, and failed updates. It’s better to fix it early.

Does this error mean my Windows is corrupted?

Not necessarily. In many cases, it simply means a required service is stopped. However, it can also indicate file corruption. Running the fixes above will clarify the situation.

How long does an SFC scan take?

Typically between 10 and 20 minutes. However, it can take longer on older or slower machines. Don’t interrupt the scan once it starts.

Will fixing this delete my files?

No — not with any of the first four fixes. Even Fix 5 (Repair Install) is designed to keep your personal files and apps intact. Always back up your data as a precaution, though.

Conclusion

The “Windows Resource Protection could not start the repair service” error sounds scary — but it’s almost always fixable. Here’s a quick recap of the 5 fixes:

1. Restart the Windows Modules Installer service — the most common fix
2. Run SFC in Safe Mode — removes software interference
3. Use DISM to repair the Windows image — fixes deeper corruption
4. Reset Windows Update components — clears update-related blockages
5. Perform a System Restore or Repair Install — the nuclear option

Start with Fix 1 and work your way down. Most users find their solution within the first two or three fixes.

If you found this guide helpful, share it with someone who’s dealing with the same error. And if you’re still stuck after trying all five fixes, consider reaching out to Microsoft Support directly.