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 No 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 No comments

72 additional answers

Sort by: Oldest
  1. Anonymous
    2015-01-18T00:01:34+00:00

    When I tried to run sfc with the offline option I had no luck at all until I switched from the system drive [C:] to my cd/rom drive [d:] That made the command

    sfc /scannow /offbootdir=d:\ /offwindir=d:\windows .

    Just to be on the safe side I first ran  

    net start trustedinstaller

    to make sure the windows module installer was running. Worked like a charm. No tinkering with the registry or winsxs, which is nice. Your results may differ, but it does no harm if it doesn't work for you. 

    Dave

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-15T18:34:13+00:00

    Worked perfectly on Win 8.1 x64. Thanks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-16T18:18:35+00:00

    I'm glad to hear it helped. BTW, thanks for replying. It is good to know that it works on Windows 8.1, too.

    Dave

    Was this answer helpful?

    0 comments No comments