Windows Resource Protection Could Not Start The Repair Service

Windows Resource Protection Could Not Start The Repair Service

This is a particularly infuriating problem because it keeps you from correcting other errors on your PC and displays whenever you try to launch services that are used to fix your computer, such as the SFC (System File Scanner).

Windows Resource Protection Could Not Start The Repair Service

Causes of “Windows Resource Protection Could Not Start The Repair Service” Issue

Several factors can contribute to this error message:

  1. Missing or Corrupt System Files: If the core system files required for the SFC tool to run are missing or corrupted, it can prevent the repair service from starting.
  2. Service Dependencies: The Windows Modules Installer (TrustedInstaller) service, which the SFC tool relies on, has dependencies that must be correctly configured.
  3. Service Not Started: If the Windows Modules Installer service is not running, the SFC tool cannot function properly.

Read Also:

  1. Discord Emoji
  2. Steam Won’t Open
  3. Voice Changer for Discord

Method 1: To Activate Windows Installer, Press The “Start” Button (Sometimes Called TrustedInstaller)

To add, remove, or alter Windows features, use the TrustedInstaller service, also known as the Windows Modules Installer. The inability to deploy Windows updates or repair utilities on this PC depends on this service being running.

In order for the Repair Service to function, this service must be running, as it has complete access to the Windows Resource Protection files and registry keys.

  1. By pressing the Windows key plus R, you may bring up the Run window. To access the Services Management Console, open the Run dialogue box, type “services.msc” (without the quotes), and then press OK.
  2. Right-click on either the Windows Installer Service or the TrustedInstaller service, and then select Properties.
  3. Windows Store Services’ Startup type should be set to Automatic in the program’s settings.
  4. A service can be quickly restarted by clicking the Start button if it has been stopped (its state can be viewed directly next to the message “Service status”).

If you try to launch the programme by pressing the Start button, you may see the following error message:

The error message read, “Windows could not start the Windows Installed Service on Local Computer. The account used to operate this service does not match the account used to run other services in the same process, resulting in error 1079.

If this happens to you, please proceed as described below.

  1. To access the Windows Installer Service settings, simply repeat steps 1-3 from the preceding section.
  2. On the Log On screen, hit the Browse… button.
  3. Simply enter your computer’s name in the “Enter the object name to pick” box, then click the Check Names button.
  4. Once you’ve finished, click OK and enter the administrator’s password in the Password box.

Method 2: Put Windows Up to Date!

Users have stated that the issue was nearly impossible to fix using any method they found on the Internet, but that applying the most recent update fixed the issue for them. Keeping your PC up-to-date is crucial, as newer versions address different issues that can emerge on older models of specific computer brands.

By default, Windows 10 is set to automatically download and instal security patches and other important updates as they become available. Settings >> Update & Security >> Update >> Check for Updates is where you should go to see if there are any new versions available.

Learn what’s new. However, if you’ve discovered that Windows isn’t updating as it should, you can remedy this by following the steps outlined below.

  1. To bring up this contextual menu, press and hold the Windows key, and then press the letter X. The Start menu also has a right-click option. Pick Windows Powershell (Admin).
  2. Simply typing cmd into the Powershell console will bring up a command prompt that is very similar to the familiar command prompt.
  3. To do this, open the “cmd” console and enter the following command, followed by the Enter key:

wuauclt.exe /updatenow

  1. After at least an hour, check back to see if any updates were identified and installed.

Method 3: In Version 14279

Until a fresh version of Windows 10 was launched, people complained that the SFC programme didn’t perform properly. However, if you’re still on this version of Windows and need to utilise SFC, you can do so with the workaround provided below.

To get ready, you’ll need to claim ownership of the two folders listed below, so just repeat the steps above for both of them. You may find the first one here:

%SystemRoot%\winsxs ; and its name is amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d

  1. To access the TrustedInstaller.exe file, launch File Explorer and navigate to:

C:\WINDOWS\servicing\TrustedInstaller.exe

  1. To change the file’s security settings, you can right-click on it, select Properties, and then select the Security tab. To access further features, select the Advanced tab. The window labelled “Advanced Security Settings” will show up. There, you’ll have to alter the key’s Owner.
  2. The “Owner:” label can be updated by clicking the corresponding link. A dialogue labelled Select User or Group will pop up.
  3. You can either use the drop-down menu under “Pick the object name to select” or the “Advanced” option to find your user account, then click “OK.” Admin should be added.
  4. Select the “Replace owner on subcontainers and objects” checkbox in the “Advanced Security Settings” window to also replace the owner of any files and folders included within the selected folder. To finish the ownership transfer, click OK.

Amd64 microsoft-windows-servicingstack-onecore 31bf3856ad364e35 10.0.14279.1000 none 5a92ee0dd788e433 is a folder in %SystemRoot%winsxs that requires the same attention.

  1. Proceed to the following subfolder. Verify that you are logged in as an administrator and that you have chosen to show hidden files and folders. Select the “Hidden objects” checkbox in the Show/hide section of File Explorer’s “View” tab menu. Until you update it again, File Explorer will continue to display the hidden files.

%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d

  1. See if a file with the name wrpint.dll exists. If the file isn’t already in that location, you’ll need to go get it so you may copy and paste it. The wrpint.dll file can be found in this directory. Click the right mouse button and select “copy” to copy it.

%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_5a92ee0dd788e433

  1. To determine if SFC will begin functioning again, copy the wrpint.dll file and paste it into the first folder where it was missing.

Method 4: Register a Discrepant Key

There is an issue with some Windows OS versions where a registry key is missing that is tied to the ID of the TrustedInstaller service. This issue requires some advanced troubleshooting skills; please refer to the instructions below.

Closing any open programmes and making a copy of the registry in case something goes wrong when you alter it are both good ideas before attempting this fix. To safely save your registry, please refer to our page for further steps.

  1. To verify, open the directory down below and look for a folder with the name 6.1.7600.16385. Be sure to jot down the name of this directory, as it contains the TrustedInstaller ID.

C:\Windows\Servicing\Version

  1. Locate the folder whose name begins with the following at C:WindowsWinSxS:

x86_microsoft-windows-servicingstack_31bf3856ad364e35_{TrustedInstaller ID} (32bit Windows)

amd64_microsoft-windows-servicingstack_31bf3856ad364e35_{TrustedInstaller ID} (64bit Windows)

  1. Make a note of these folder names and save a copy of them.

How to Bypass “Windows Resource Protection Could Not Start The Repair Service” Issue

If you encounter the “Windows Resource Protection Could Not Start The Repair Service” error, consider the following solutions to bypass it and successfully run the SFC tool:

  1. Run SFC in Safe Mode:
    • Boot your computer into Safe Mode and then run the SFC scan. Safe Mode may minimize conflicts that could be preventing the repair service from starting.
  2. Check Service Dependencies:
    • Ensure that the Windows Modules Installer service and its dependencies are configured correctly. You can use the “Services” application (services.msc) to check and configure these settings.
  3. Repair Missing or Corrupt System Files Manually:
    • If the SFC tool is unable to run, you can attempt to repair missing or corrupt system files manually. This involves replacing problematic files with known good copies from a Windows installation media or another computer with the same Windows version.
  4. Use DISM (Deployment Image Service and Management Tool):
    • The DISM tool can be used to repair the Windows image. Open Command Prompt as an administrator and run the following command:
      DISM /Online /Cleanup-Image /RestoreHealth

      After DISM completes, try running the SFC scan again.

  5. Check for System File Corruption:
    • Sometimes, the error may be due to significant system file corruption that requires advanced repair steps. In such cases, consider seeking assistance from Microsoft Support or a qualified technician.

How to Check SFC Scannow Status

To check the status of an ongoing SFC scan or view its results, follow these steps:

  1. Open Command Prompt as an administrator.
  2. Type the following command and press Enter:
    sfc /scanfile=C:\windows\system32\file_name.extension

    Replace file_name.extension with the specific file you want to scan. This command allows you to scan individual files.

  3. Review the scan results:
    • The results will indicate whether the file is corrupted or has integrity violations. Follow any instructions provided to resolve the issues.

Read Also:

  1. DX11 Feature Level 10.0
  2. Can’t Connect To This Network
  3. Windows Explorer Keeps Crashing

Conclusion

The “Windows Resource Protection Could Not Start The Repair Service” error can be frustrating when you’re trying to use the SFC tool to repair your Windows system.

By understanding its causes and implementing the bypass solutions mentioned in this article, you can increase your chances of successfully running the SFC scan and resolving any corrupted or missing system files.