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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-08-25T13:59:12+00:00

    Processor: Not Available & Installed memory (RAM): Not Available ==> AND  ALL MY DRIVERS LOST.......

    TRY:

    Window + R => msconfig => General => Startup Selection => Normal Startup (Load all device drivers and services).

    Hope to helpful.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2015-09-19T18:51:35+00:00

    That's probably because Windows tries to run the 32bit version of SFC.exe in a 64bit Windows installation.

    I went through the same frustrating error on Win10 x64.

    To make a long story short just use this command line from an Admin prompt (please notice the "sysnative" path...):

    C:\windows\sysnative\sfc /scannow

    Solved.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2015-09-18T15:47:02+00:00

    it appears that you need to run sfc from windows powershell in admin mode to get sfc to work

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments