Windows resource protection could not start the repair service

How to Fix the «Windows Resource Protection could not start the repair service» Error on Windows 10

System File Checker (SFC) is a utility in Windows that allows users to scan for corrupt Windows system files and restore them. Unfortunately, you may get the «Windows Resource Protection could not start the repair service» error when running the «SFC /Scannow» command. This article will show you how to fix this problem.

Windows Resource Protection (WRP) prevents the replacement of essential system files, folders, and registry keys part of the operating system. Permission for full access to modify WRP-protected resources is restricted to TrustedInstaller.

WRP-protected resources can only be changed using the Supported Resource Replacement Mechanisms with the Windows Modules Installer service.

TrustedInstaller is a process belonging to the Windows Modules Installer service in Windows 10, 8, 7, and Vista. Its primary function is to enable installing, removing, and modifying Windows Updates and optional system components.

Sometimes TrustedInstaller.exe may become corrupted, and you may get an error message. In such a case running the System File Checker may help.

However, sometimes, even the Windows Resource Protection service, which runs the System File Checker (SFC), is affected. In such a case, if you try to run the «sfc /scannow» command, you may get the error message saying: «Windows Resource Protection could not start the repair service».

Read the guide below to fix the «Windows Resource Protection could not start the repair service» error while trying to run the System File Checker.

Video Showing How to Fix the «Windows Resource Protection could not start the repair service» Error:

Table of Contents:

• Introduction
• Enable Windows Modules Installer Service
• Run System File Checker in Safe Mode
• Run DISM Scan
• Video Showing How to Fix the»Windows Resource Protection could not start the repair service» Error

Enable Windows Modules Installer Service

Windows Services (also known as services.msc), are used to modify how Windows services run on your system. You can modify a service’s settings for security, troubleshooting, and performance-related reasons.

You will need to access the Windows Installer service, which enables installation, modification, and removal of Windows updates and optional components. If this service is disabled, install or uninstall of Windows updates might fail for your computer.

To access the Windows Modules Installer service type «run» in Search and click the «Run» result.

In the Run dialog box, type «services.msc» and click «OK» to open Windows Services.

Now scroll down through the services list to find the «Windows Modules Installer» service. Right-click it and select «Properties» in the dropdown menu. Or simply double-click the Windows Modules Installer service.

Make sure that «Startup type» is set to «Manual». If it is not set to Manual, then set it this way and click «Apply» to save the changes made.

You can also try to enable the TrustedInstaller using Command Prompt and its commands. Some commands available in Windows require that you run them from an elevated Command Prompt. This means you have to be running it with administrator-level privileges.

To open Command Prompt, type «command prompt» in Search and then right-click on the «Command Prompt», select «Run as administrator» from the dropdown menu to run Command Prompt with administrator privileges.

Now you will need to execute a couple of commands. Type «sc config trustedinstaller start=demand» and press Enter on your keyboard.

Then type «net start trustedinstaller», and press Enter on your keyboard again.

Now try to run the System File Checker and see if you are still getting the «Windows Resource Protection could not start the repair service» error.

[Back to Table of Contents]

Run System File Checker In Safe Mode

Another thing you might want to try is to run the System File Checker in Safe Mode. Safe Mode is a diagnostic start-up mode in Windows operating systems used to obtain limited access to Windows when the operating system does not start or function normally.

If you are not sure how to start your Windows in Safe Mode, read this article.

[Back to Table of Contents]

Run DISM Scan

DISM stands for Deployment Image Servicing and Management, and it can be used to repair and prepare Windows images, including the Windows Recovery Environment, Windows Setup, and Windows PE.

To run DISM scan, you need to open Command Prompt as administrator again and type in this command: «DISM /Online /Cleanup-Image /RestoreHealth». Press Enter on your keyboard to execute it.

See if this fixes the «Windows Resource Protection could not start the repair service» error while trying to run the System File Checker.

We hope this article was helpful in trying to fix the «Windows Resource Protection could not start the repair service» error, and now you can run the System File Checker without any problems. Do not hesitate to write a comment in the comment section below if you found another workaround for this error!

[Back to Top]

The Windows Resource Protection Could Not Start The Repair Service occurs when the system fails to run the System File Checker (SFC) Scan. There could be several causes for this problem, but it is most likely to occur if the Windows Module Installer service fails to function. 

Bugs in the Windows, corrupted system files and issues in the System drive volume also can lead to this problem. On some Windows devices, viruses and malware infections could also trigger this problem while initiating the repair service.

Most Users have reported resolving this issue by restarting the Module Installer service. However, this issue has been reported on some Windows devices after installing Windows updates, and restarting the Windows service may not work in those cases.

Today, we’ll discuss how to fix this problem and get the Windows repair service back up and running.

A system restart is recommended before proceeding with the fixes to eliminate the possibility of minor operating system glitches causing this issue.

1. Open the Command prompt with administrative privileges.
2. Type the command SFC /scannow and hit enter. This should start the scan normally. 

If it still shows the  Windows Resource Protection Could Not Start The Repair Service error, try these suggested fixes to solve the problem.  

Change the Startup type of the Windows Module Installer 

Windows module installer is responsible for updating, modifying and removal of different Windows Services. It is also associated with the system files of Windows resource protection. It is seen that if this service fails to startup, the SFC scan fails to run and prompts Windows Resource Protection Could Not Start the Repair Service message. 

1. Press Windows Key + R, type services.msc and hit enter.
2. In the Services list, locate Windows Modules Installer and double-click to open its Properties. 
3. Set the Startup Type to Manual and Click on the Start Button.
4. Click on Apply to save these changes. 

If you cannot start the Module from the Windows Services, you can also force start it using the command line. 

1. Press Windows Key + X, and open Terminal ( Admin).
2. Use this command to set the automatic startup type for the Windows module Installer.
   sc config trustedinstaller start= auto
3. Now, run the following command to restart the service. 
   net start trustedinstaller

Run the Repair service from the Safe Mode

In safe mode, Windows operates with minimal features and drivers. If there are some system processes causing the conflicts while carrying out the SFC scans, you can boot into safe mode and try running the scans.  

1. Go to the Start menu.
2. Click on the power button, and select Restart while holding down the Shift key.
3. The System will restart into recovery environment.
4. Go to Troubleshoot > Advanced options > Startup Settings.
5. Click on Restart Button.
6. After the computer restarts, press F4. The system will now boot into Safe mode. 
7. Finally, try running the SFC scans. 

Copy the Missing Dll to the System Directory

On some early builds of Windows 10 the wrprint.dll module that is used by many Windows applications seems to be missing. This is a common issue encountered in the insider build 14279 and 14291. This issue was later solved by rolling a stable update.

Here’s how to fix this problem without having to update the Windows.

1. Open the notepad and copy the command into it.

   @echo off cls setlocal set root=%SystemRoot%\WinSxS\%PROCESSOR_ARCHITECTURE%_microsoft-windows-servicingstack for /f "delims=" %%A in ('dir /ad /b %root%-onecore*') do set "from=%SystemRoot%\WinSxS\%%A" for /f "delims=" %%A in ('dir /ad /b %root%_*') do set "to=%SystemRoot%\WinSxS\%%A" takeown /F %to%\* /R /A 1>nul icacls %to%\*.* /T /grant administrators:F 1>nul echo on echo F|xcopy /C /R /O /Y %from%\wrpint.dll %to%\wrpint.dll pause

2. Save the file with a name scanfix.cmd ( it’s a batch file, thus avoid naming it as scanfix.cmd.txt)
3. Now, run the file as an administrator.
4. The command line will copy the wrprint.dll to the relevant directory. You will see 1 File(s) message when this happens. 
5. At last open the command prompt with administrative privileges and run the SFC command.

Run SFC Offline 

If you are not able to run the SFC scans from the Recovery environment or the safe mode, you can use a bootable installation media and then run the SFC command offline. 

1. Connect your Windows Installation Media to your Device.
2. Change the Boot Priority and boot the device using the installation media. 
3. Click on Next in the Installation prompt.
4. Select the options to Repair your computer. 
5. Go to Troubleshoot > Advanced Options > Command Prompt.
6. Now, use this command to determine the system partition. 
   BCDEDIT
7. Under the Windows Boot loader section, check for the partition drive letter and system root. 
8. Finally, use this command to perform the SFC scans.
   sfc /scannow /offbootdir=<SysPartition_Drive_Letter>:\ /offwindir=<Windows_Drive_Letter>:\windows

For instance, if the partition drive letter is C: and the system root is \Windows, use the above command as,
sfc /SCANNOW /OFFBOOTDIR=C:\ /OFFWINDIR=C:\windows

Perform DISM scans

When the Windows image file (.WIM) gets corrupted or has some potential issues with it, it can trigger problems with the repair service as well. The system file related to the repair service might get affected because of different reasons. To repair these underlying issues with the service, you can run the DISM scans.

1. Open the Windows terminal with elevated privileges. 
2. Execute this command to run the DISM scan. 
   DISM /Online /Cleanup-Image /RestoreHealth
3. When the process gets completed, try running the SFC scan. 

Run CHKDSK Scans

Logical errors in the disk and problems with the file system metadata can result in different system-related issues. If the system partition gets affected by such logical errors, different Windows services can face functional hitches. This might also be the case that is causing the Windows repair service (SFC in specific) not to function as intended. 

You can perform the CHKDSK scans to fix such drive-related problems and then see if the SFC scans work. 

1. Open Command Prompt with administrative privileges.
2. Now, run the following command to start the chkdsk scan. 
   chkdsk /r
3. Type Y and hit enter. The scans will start after a system restart. 
4. Run the SFC scans after the disk check process gets completed. 

Uninstall Windows Update

Some of the rolled-out Windows Update builds are reported to have issues with the System File Checker. For instance,  packages like the KB2821895 are said to bring problems to the repair service. 

If you have encountered a similar problem after the windows update, then it is recommended to uninstall it to get a resolve. 

1. Press Windows Key + I to open the Settings apps.  
2. Go to Windows Update > Update History. 
3. Scroll down and locate Uninstall updates options. 
4. Find the most recently installed update that you suspect is causing this error. 
5. Click on the Uninstall button 

Perform System Restore 

If the issue with the Windows repair service has suddenly popped up, system restore also becomes a viable option to fix this issue. System restore takes your system back to the point where the problem exists.

However, you must have created a restore point before the occurrence of this problem.

1. Press Windows Key + R, type rstrui.exe and hit enter. This will open the System restore utility. 
2. Select the Choose a different restore point option and click on Next. 
3. Choose the restore point that was created prior to the occurrence of the issue.
4. Click on Next and follow the prompt. 
5. Verify if the issue has been solved after the restoration process is complete.  

Windows Reset 

If the system restore does not work, you can reset the whole Windows operating system to default using the Windows Reset service. Here’s how to do it. 

1. Press Windows Key + R, type systemreset –factoryreset and hit enter to launch the Windows Reset utility.
2. Choose the option  Keep my files.
3. Now, select the Local reinstall option. 
4. Follow the prompt and complete the reset process. 
5. When the reset is complete, open the command prompt and run the SFC command. 

It is best to perform a clean Windows installation to resolve this issue altogether. However, you must back up your files before doing it. We have a comprehensive guide for you on performing a clean Windows installation.

Означает ли это, что всё так плохо, что даже SFC не работает? Не всегда, просто во время проверки в системе происходит сбой или инструмент не может получить доступ к каталогу WinSxS, в коем расположены важные файлы. Вероятны и другие причины — повреждение файловой системы, наличие физически нечитаемых секторов на диске, отсутствие у пользователя соответствующих прав доступа. Что делать и с чего начинать поиск причин неполадки?

Причиной ошибки сканирования может быть ограничение доступа SFC к каталогу WinSxS. Попробуйте снять их, выполнив в консоли CMD команду

и перезагрузив компьютер.

sfc /scannow /offbootdir=D:\ /offwindir=C:\Windows

• Примечание: определить буквы томов в загрузочной среде проще всего с помощью Блокнота, запустив его командой notepad и выбрав Файл → Сохранить как.

Если приведенные выше способы не дали результатов, высока вероятность, что отказ защиты ресурсов Windows вызван повреждением самого хранилища системных компонентов, то есть содержимого папки WinSxS. Проверить его состояние можно командой

если она выдает сообщение о необходимости восстановление хранилища, выполняем в консоли такую команду:

Компьютер при этом должен быть подключен к интернету, поскольку Windows может потребоваться подключиться к серверу Microsoft и скачать недостающие файлы. По завершении процедуры перезагружаемся. Теперь, когда хранилище восстановлено, sfc/scannow должна заработать как надо.

---

In this guide, we will show you quick ways to fix this issue and restore normalcy on your PC.

How to fix the Windows resource protection SFC error?

1. Run SFC in Safe Mode

If you are getting the Windows resource protection could not start the repair service error while trying to run the SFC scan on normal boot, you might need to run the scan in Safe Mode.
If the scan works normally, the problem could be due to a third-party app or process.

2. Make some security changes

SFC might be interrupted if the winsxs folder cannot be accessed for some reason. The might be why you are getting the Windows resource protection could not start the repair service error.
You can fix this by modifying security descriptors for that folder.

3. Run CHKDSK from Command Prompt

Another reason for the Windows resource protection could not start the repair service is related to hard disk errors. The easiest way to fix this is to run the CHKDSK command.
The three methods detailed in this tutorial should help you solve the Windows resource protection could not start the repair service error on Windows 10. It means that now you can run the SFC scan without any sort of problems.
If the SFC scan is still not working on your PC, check our detailed guide to fix it quickly.
Let us know which of the methods worked best for you by leaving us a message in the comments below.

Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment

Δ