Trying to run sfc/scannow and response is "Windows Resource Protection could not start the repair service"

Anonymous
2010-01-23T17:14:37+00:00

Originally, this started when I was trying to install some statistical software (JMP8) that should be supported by Windows 7.  I kept getting "the application could not start because its side by side configuration is incorrect"

While researching that for Windows 7, I ran across a suggestion to run sfc/scannow in the command prompt.  When I try to do that, I get the error listed above:  Windows Resource Protection could not start the repair service.

Any suggestions?

Windows for home | Windows 10 | Microsoft Store

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-05-20T11:30:12+00:00

I  had  this issue and all the steps described in this and other internet posts led me  to a dead end of errors. 

However, I then discovered that somehow almost all my services had  gotten reset to "disabled". This was causing my original problems (network connectivity among them) and this problems.

Changing the services settings fixed my problems

To get to services type services in the search programs box on the start menu, then right click to run it as administrator.

Was this answer helpful?

300+ people found this answer helpful.
0 comments

72 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-02-15T02:01:38+00:00

    Exactly!

    I found this in AccessProtectionLog.txt

    when I reset it then the cmd

    so I think main cause is TrustedInstaller.exe is stopped ,by System or other software ,all we need is find it out and solve it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-10-30T17:47:48+00:00

    GOOD Reply!

    Sometimes when you make your own Command Prompt icons (DOS prompt) the resulting windows won't, for some reason I have not yet discovered, run SFC /ScanNow.

    What Shodan240z suggests is to let Windows 7 64-bits open the Command Prompt Window, using the Start > Run menu choice. That works for me even though trying to run SFC /ScanNow from my own Command Prompt windows doesn't.

    The fundamental problem is that Microsoft allows Windows to be a mess. There are many, many areas where the programming is not finished. Microsoft CEO Steve Ballmer has been fired and will leave soon, but there is no evidence the Microsoft board of directors will choose someone who actually knows how to run a technology-oriented company.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-10-15T11:00:36+00:00

    Benko75 is right - this is the fix, no need for a complicated Regedit 

    I had a similar issue with a user who was unable to start any MS services including IE (Win7) - I applied this fix and it resolved the issue, immediately:

    • 'run' > services.msc
    • select the 'extended tab'
    • Restart the Windows Module Installer
    • Problem fixed

    Can now run SFC /Scannow (and all other effected MS programs) with  No problems

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments