Hi James,
Can you run the following command?
DISM /Online /Cleanup-Image /RestoreHealth
If it fails, please upload the following log files in your next reply.
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\DISM.log
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Windows Resource Protection could not start the repair service
Hi James,
Can you run the following command?
DISM /Online /Cleanup-Image /RestoreHealth
If it fails, please upload the following log files in your next reply.
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\DISM.log
The message “Windows Resource Protection could not start the repair service” appears when running sfc /scannow and the underlying Windows Resource Protection (WRP) infrastructure cannot start its required service (Windows Modules Installer/TrustedInstaller).
WRP is the mechanism that protects and repairs essential system files, folders, and registry keys. It only allows changes through the Windows Modules Installer service using supported replacement mechanisms. When sfc /scannow runs, it relies on this infrastructure to scan and repair protected files. If the repair service cannot start, SFC cannot complete and shows that error.
To address this situation, use the System File Checker as documented and pay attention to the result messages:
sfc /scannow
PendingDeletes and PendingRenames exist under %WinDir%\WinSxS\Temp.Because WRP strictly controls access to protected resources, applications and installers must not attempt to modify WRP-protected files or registry keys directly. All repairs must go through SFC/WRP and the Windows Modules Installer service.
References: