Windows Resource Protection Could Not Start The Repair Service Windows 10- How to Fix

Did you just come across the “Windows Resource Protection could not start the repair service” error message while you were trying to run the System File Checker? We know that it is one of the most disappointing things to face these kinds of messages. So here to help with your problem, windows resource protection could not start the repair service windows 10.

Is there any file that is causing issues with your computer? Millions of users use Windows 10, the successor to Windows 8.1, and the System File Checker solves many issues. It restores the files that have been damaged and corrupted, and thus you can see why it is this widely used. It can detect and fix the files. But isn’t it the end of the world when the thing that is supposed to resolve your issues itself gets broken? We are here to help you fix the issue of windows resource protection that could not start the repair service.

When you were trying to execute the “SFC /scannow” command, were you greeted with the message Windows Resource Protection could not start the repair service? We will help you step by step through what you can do to get your System File Checker running again.

Why Is the SFC Scan Not Working?

We can tell you the reason that your SFC is not working. It is because of the TrustedInstaller (Windows Modules Installer). This is a necessary evil. It is vital for installing, modifying, and removing various applications. It also has control over your system files to prevent other external sources from modifying or deleting the files you have. TrustedInstaller can fully access your Windows Resource Protection (WRP) files and the registry keys. These are necessary for the SFC scan to work.

If you try to execute the “SFC /scannow” command, this service will start on its own. You can think of disabling this service, but that would stop you from restoring the damaged files. Keeping this in mind, this article will cover all about windows 10 SFC scannow could not perform the requested operation.

Also, this issue is most common in the almost outdated Windows 7; it can also happen in windows 8 and windows 10.

Fix Windows Resource Protection Could Not Start the Repair Service Error

Here we will list all possible solutions for SFC scannow windows resource protection that could not start the repair service.

Enable Windows Modules Installer Service

The most straightforward way to do it is to search manually. You must configure the Windows Modules Installer such that it is allowed to start whenever you try to run the SFC scan. Here are the detailed ways on how to do it.

• On your keyboard, press the Windows + R keys. This will open the Run utility box.

• Type services.msc and click on the OK button. This will be launching the Services window. If it doesn’t readily load, wait for it.
• After the window opens, you have to right-click on the Windows Modules Installer service and choose Properties.

• Set the Startup type to Manual. If the service is not running, click on the Start button. Click on Apply, then click on OK. You should be back again at the list of services.
• Close the Services window and then try running the “SFC /scannow” command again on your computer.

Is the command still not working? Well, don’t worry, there is more than one solution.

Use the Command Prompt

This method essentially follows the same steps as the last one. But this will be done in the Command Prompt. You will need administrative permissions to make the modifications needed. So now try this for the issue of resource protection could not start the repair service.

• You can either use the search bar beside the magnifying glass icon in your taskbar, or you may use the Windows + S shortcut.
• In the search bar, type cmd or Command Prompt. When you see it in the results, you will have to right-click on it and choose Run as Administrator.

• You will be prompted by the User Account Control (UAC), and when prompted, click Yes to allow the app to launch with administrative permissions.
• Once the Command Prompt window opens, type the command given below and then press
  • Enter to execute it: sc config trusted installer start= auto.
• If the command worked, you should see the SUCCESS message.
• After you have executed the previous command, run this command:
  • net start trusted installer.
• You should get a message about the Windows Modules Installer service starting successfully.

By now, you should be successful; if not, there are other methods you can try.

Run System File Checker In Safe Mode

A background application may be interfering with the System File Checker, which can cause it not to work correctly. In that case, you can try executing the scan command in Safe mode. Safe mode is known for booting your system keeping only the most necessary Windows components enabled.

Once again, check if the SFC scan is working.

Run DISM Scan

It is not a myth. It is true that sometimes running the DISM command can fix the System File Checker. The Deployment Image Servicing and Management or the DISM tool is known for re-deploying your system image to fix the directly related issues. We will be giving you a step by step instructions on how to do this.

Now try running the SFC scan and check if it works fine now.

Conclusion

I hope the article was hopeful on windows resource protection could not start the repair service windows 10, and now you can successfully run the SFC scan. We have listed more than the number of trials it should take to sort out the issue, and one of these is bound to work. I hope you won’t ever have to face again that windows resource protection could not start.

Share on Facebook

Tweet

Follow us