Fixing the Issue: Windows Resource Protection Unable to Start Repair Service – 2025

Fixing the Issue: Windows Resource Protection Unable to Start Repair Service

The System File Checker (SFC) tool in Windows is a built-in utility that scans and repairs missing or corrupted system files. But sometimes, when you try to run the command sfc /scannow, you may receive an error that says:

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

This error stops the scan from proceeding and usually means that a required service — most often the Windows Modules Installer (TrustedInstaller) — isn’t running or something is blocking its execution.

In this article, we’ll walk you through what causes this issue and how to fix it step by step.

What Causes This Error?

Several things can lead to the Windows Resource Protection could not start the repair service error:

• The Windows Modules Installer service is disabled or stopped

• Insufficient user permissions (you’re not running as administrator)

• Corrupt or damaged system files preventing the service from launching

• Conflicts with third-party software or security tools

Now, let’s go through the different methods to resolve this problem.

1. Run Command Prompt as Administrator

You must run Command Prompt with elevated privileges to execute the SFC scan.

Steps:

1. Press Start and type cmd.

2. Right-click Command Prompt and select Run as administrator.

3. Try running the command again:

If this was the issue, the scan should begin immediately. If not, move on to the next method.

2. Start the Windows Modules Installer Service

The Windows Modules Installer is responsible for enabling installation, modification, and removal of Windows updates and optional components. It is also required for SFC to work correctly.

How to Enable It:

1. Press Windows + R, type services.msc, and press Enter.

2. In the Services window, scroll down to Windows Modules Installer.

3. Right-click it and select Properties.

4. Set the Startup type to Manual.

5. Click Start if the service is not already running.

6. Click Apply and then OK.

Try running the sfc /scannow command again.

3. Use the Command Line to Start the Service Manually

If you’re more comfortable with the command line, or if the GUI doesn’t work, you can start the service using this method.

Steps:

1. Open Command Prompt as Administrator.

2. Run this command:

3. Then start the service with:

Now try running:

This should allow the scan to proceed.

4. Check for Corrupt System Files with DISM

Sometimes, system file corruption can prevent the repair service from starting. The DISM tool (Deployment Image Servicing and Management) can help repair the Windows image.

Steps:

1. Open Command Prompt as Administrator.

2. Run the following command:

This process may take several minutes. Once it completes, restart your computer and try sfc /scannow again.

5. Boot into Safe Mode

If third-party software is interfering with the SFC scan or Windows Modules Installer, booting into Safe Mode can help isolate and fix the issue.

How to Boot into Safe Mode:

1. Press Windows + R, type msconfig, and hit Enter.

2. Go to the Boot tab.

3. Check Safe boot and choose Minimal.

4. Click Apply and then OK.

5. Restart your computer.

Once in Safe Mode, open Command Prompt as Administrator and try:

After you’re done, return to msconfig and uncheck Safe boot to start normally.

6. Check for Permission Issues on the System Files

If the system files have incorrect permissions, the SFC scan may be blocked.

Reset System Permissions:

1. Open Command Prompt as Administrator.

2. Run this command:

This gives full permission to administrators on the WinSxS folder, which is critical for system repairs.

Then, try the SFC scan again.

7. Perform a Clean Boot

A clean boot disables all third-party apps and services to help you determine if software is interfering.

Steps:

1. Press Windows + R, type msconfig, and hit Enter.

2. Under the General tab, choose Selective startup and uncheck Load startup items.

3. Go to the Services tab and check Hide all Microsoft services, then click Disable all.

4. Click OK and restart your computer.

Run sfc /scannow again. If it works, you know some third-party software was causing the issue.

8. Consider a System Restore

If the issue only recently started, a System Restore can take your system back to a point when everything was working properly.

Steps:

1. Press Windows + R, type rstrui, and press Enter.

2. Choose a restore point from before the issue began.

3. Follow the on-screen instructions.

After restoring, try running the SFC command again.

Conclusion

The “Windows Resource Protection could not start the repair service” error can prevent essential system repairs from taking place. Fortunately, the issue is usually tied to the Windows Modules Installer service, permissions, or system corruption — all of which can be fixed with the methods above.

By enabling the right services, repairing Windows components with DISM, or simply running as administrator, you can resolve the problem and get back to repairing your system with SFC.

If none of the solutions work, you may consider performing an in-place upgrade using the Windows installation media, which can repair your system without deleting your files.