Fixing an error in a Windows operating system (OS) can be an exhausting task, especially since most Blue Screen of Death (BSoD) windows lack a definitive cause. Some users have even reported facing new issues while resolving old ones. The Windows resource protection could not start the repair service error, for example, has been known to occur in such circumstances.
A scan of your system files is often the most efficient method to resolve errors. Unfortunately, the Windows resource protection could not start the repair service issue prevents users from accessing scan services, complicating the issue even further.
What causes SFC scannow errors?
Like all efficient operating systems, Microsoft offers several services designed to prevent file corruption. The Windows Resource Protection (WRP) mechanism, for example, safeguards essential folders, files, and registry keys. It is one of the last defense systems on a computer.
Even the TrustedInstaller lacks full access to the WRP files. There are further restrictions on WRP files, meaning you can only change them using the supported resource replacement service with the Windows Module Installer.
If the files and folders under WRP are opened, the system will become vulnerable to attacks, and likely face catastrophic failure. To understand the “Windows resource protection could not start the repair service” error that ensues, we must first learn what an installer is.
The role of TrustedInstaller
Every Windows system comes with a module installer. As the name suggests, this installs various apps and software to your device. Upon doing so, you will see a dialog box asking you to confirm the installation. This dialog box marks the beginning of the process.
The module installer deploys TrustedInstaller to ease the installation process. TrustedInstaller has been available since Windows Vista and can be accessed in the latest system version. Besides enabling the installation and uninstallation processes, TrustedInstaller further modifies the system updates.
Despite its many benefits, the program can create errors in the Windows OS. They are often the result of corruption within the system files. To restore these items, you must run a scan, and since this is directly connected to WRP, the files affecting it may also be corrupted. Therefore, you cannot proceed to scan the system again and look for more corrupted files. The Windows resource protection could not start the repair service error is shown in these situations.
This article will describe various potential fixes for this issue that you can perform at home with zero cost.
How to fix the “Windows resource protection could not start the repair service” SFC scannow error
Method 1: Restart your computer
In a list of solutions for issues you might face while using a computer, a system restart would likely take first place. Well, at least where the Windows resource protection could not start the repair service error is concerned.
This method is especially important for those who have never tried to diagnose an issue since it is completely risk-free and takes just a few minutes.
If the Windows resource protection error remains, try the method explained below.
Method 2: Enable the Windows Module Installer
As mentioned above, TrustedInstaller is a process that runs within the Windows Module Installer. It dictates how various services operate within the system, so if the module is disabled, many features will cease to work or do so in a limited capacity. One of the primary fixes for the Windows resource protection could not start the repair service error is turning on the Windows Module installer.
To turn the service one, follow the below steps:
- First, type “run” in the Windows search bar. The run command will allow you to access all Windows services without opening the Command Prompt.
- In the dialog box, type “services.msc”
- Now, you will see a list of services in your system. Not all of these are necessarily active.
- Scroll down, locate the Windows Module Installer service, and right-click on Properties.
- Simply switch the Startup type to Manual and hit Apply.
- Restart your system and try to perform a system scan. If the error still occurs, proceed to the next method.
You may also perform the process above from the Command Prompt, though this is not recommended if you lack experience with that tool.
If you use the Command Prompt often, this method might be much easier for you.
- Type “Command Prompt” in the Windows search bar.
- Open the Command Prompt as administrator.
- A box will pop up asking if you want to permit the command prompt. Select “Yes”.
- Now, the Command Prompt will look something like this.
- Type “sc config trustedinstaller start=demand”. Press Enter.
- Type “net start trustedinstaller”, and hit Enter again.
- Now, try running the SFC /scannow command again.
If the windows resource protection could not start the repair service error persist, try the steps below.
Method 3: Run your system in Safe Mode
Running Windows in Safe Mode will prevent applications from interfering with its commands, disabling all features besides those that are essential. If any external app prevents the SFC scannow command, this method will resolve it.
Turn off the system and press F4 when it restarts to enter Safe Mode. An options screen will appear, and you will need to select Troubleshooting. In the menu, you will find the Safe Mode option. We have published a dedicated article with more details about how to boot into Safe Mode and how you can turn it off once you have finished.
The Windows resource protection could not start the repair service error requires users to open the Command Prompt as administrator. Only then can you run the SFC /scannow system scan. A successful scan in Safe Mode suggests the presence of an external application that is preventing the process. You must then run the system in normal mode and uninstall 3rd party apps until you find the one that conflicts with SFC.
If this method doesn’t work, it means the error comes from a fault in your system. Follow the subsequent methods to resolve the issue.
Method 4: Run a DISM scan
The Deployment Image Servicing and Management (DISM) scan ensures that all Windows images are correctly loaded. It includes the Windows Recovery Environment, Windows PE, and Windows setup. All of which are key to resolving the dreaded Windows resource protection could not start the repair service error.
To run a DISM Scan, follow the below steps:
- Type “command prompt” in the Windows search bar.
- Open the Command Prompt as an administrator.
- Type, “DISM /Online /Cleanup-Image /RestoreHealth”.
- Now, press Enter.
This command has a high chance of fixing the error. However, we have included one more alternative solution for those of you who are still struggling.
Method 5: Run a full malware scan
Windows Defender is a built-in Microsoft malware scanning feature that constantly protects your system from all known viruses. To scan your OS using Windows Defender, follow the steps below.
- Type “Windows Security” in your system’s search bar.
- The home page of the security application will appear, displaying all the features of the Windows Defender.
- The screen will present you with various security options. We recommend turning on the auto-scan feature to protect your system’s health.
- To do so, click on Virus & threat protection.
- You’ll be taken to the page shown below. Click on Scan options.
- Click on the Full Scan Radio button and select Scan now.
- Microsoft Defender will automatically scan and remove any known malware from the system.
The only real restriction of Windows Defender is that it only scans and compares known malware. Therefore, if a new virus was to enter your system, there is a chance it will develop into a Windows resource protection could not start the repair service error.
For holistic protection, you must also scan your system for vulnerabilities. Many paid anti-malware solutions offer these services. It might be worth the price if you are yet to solve the SFC scannow error.
We hope the methods listed above helped you solve the Windows resource protection could not start the repair service error with as little effort as possible. Let us know in the comments which method worked for you.