Fixed: Windows Resource Protection Could Not Start The Repair Service


Have you encountered with Windows Resource Protection error? Windows operating system is no stranger to errors and corruption to the files. However, a simple change in the settings can cause plenty of problems. The Windows Resource Protection error is not a big deal, and anyone can solve it with minimum CMD knowledge.

However, technical & command knowledge should not pose a problem. But you’ve to learn what caused the “Windows Resource Protection could not start the repair service” error. Many Windows users do not read the error causes, and they end up finding the making the same again. We do not want you to make the same mistake again, so allow us to tell you the reasons behind “Windows Resource Protection could not start the repair service” error.

What Triggers This Error?

There is a service called “Windows Modules Installer (TrustedInstaller),” and it has full-control over registry keys and Windows Resource Protection (WRP). The Microsoft added System File Checker (SFC) on your copy so that you can identify & fix the corrupted files.

The (SFC) System File Checker interrupted because the Windows Modules Installer is disabled. If the WMS is disabled, then it causes the Windows Resource Protection could not start the repair service. In short, you have to enable the Windows Modules Installer, and the problem gets fixed.

How to Fix Window Resource Protection Error:

1. It Works On 64-Bit Windows PC

By following simple steps, you can fix the problem in a few clicks without any issues. Make sure you have administrator rights and access to the password of lockscreen.

Step 1: Press Windows key + S and type “CMD” and click on the first result.

Step 2: Make sure to run the CMD (command prompt) as administrator.

Step 3: Now, you have to type “sc config trustedinstaller start= auto” and hit enter.

fix Windows Resource Protection

Step 4: Wait for a few seconds, and the notification shows up with “success” in the message.

Step 5: Again, you have to type “net start trustedinstaller” and hit enter.

Step 6: Wait for a moment, and type “sfc /scannow” to begin the scanning because the problem is fixed.

It works with 64-bit computers, but you can try the solution on a 32-bit machine as well.

2. Enable Windows Modules Installer Service

The first solution should have fixed the issue, but it seems like we have done things manually. Windows comes in several builds version so that it might not have worked for you. However, it is not the end of the solution because we have more than can enable Windows Modules Installer service. Now, we are going to you a manual solution, and it is very easy to follow compared to the command prompt.

Step 1: Press Windows key + S and type “services” and click on the first step.

Step 2: The services window takes a few moments to launch, and if your Windows machine is slow, then it consumes more time.

Step 3: Scroll down until you reach “Windows Module Installer.” Remember, the services page is in numerical order and scroll down to the bottom of the page. I have pointed out the start-up type “manual” because it’s the default option. If you find the start-up on your machine as “disabled”, then you have to enable it.

Step 4: Click to select the service, and right-click the mouse to view more options. You can view the “properties” and click on it to open more options.

Step 5: Click on the “start-up type” and select manual.

In the end, click on Apply > OK and close the window.

Now, restart your computer to fix the issue because we have selected manual, and the Windows must recheck the changes.

3. System Restore

The iconic feature added in Windows XP continued to this day because it’s a simple feature with an effective solution. The Microsoft knows that System Restore can resolve half of the computer issues. The problem may resolve, or it remains the same because it depends on the restore point. If the restore points old, then you can hope that it gets fixed. However, the restore point is new, and the chances of getting the problem fixed are very little.

However, it is a good option and its worth to give it a shot even if the chances are thin.

Step 1: Press Windows key + S and search for “create a system restore” or “system resto” and click the first result. Do not worry; we are not going to create a new restore point because we are focusing on using it to access existing points.

Step 2: A window pop-up on your screen and click on the system restore to begin the process.

Step 3: The Windows suggest you the best restore point and continue. However, we want to select the oldest available restore point because it can fix the issue. Click on “choose a different restore point” for more options and click “next” to proceed.

Step 4: Now, select the oldest restore point depending on the date. You can also click on “show more restore points” to view the additional points, and click on “next.”

Step 5: The system restore process begins and be patient throughout the process.

It’s a long process after completing the steps. You have to give the Windows time to restore the system to an earlier point without any issues.

Do not unplug the power cord of the desktop and make sure that you don’t force shutdown because it can ruin your computer further.

Did this article help?

In case, if the problem does not get fixed, then what is next? Turn off your computer and take it an authorized Windows engineer because of only they the necessary tools to fix the in-depth problems. Let us know what do you think about the “Windows Resource Protection could not start the repair service” solutions in the comment section below.


Please enter your comment!
Please enter your name here