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
    2017-09-06T02:23:06+00:00

    I solved the issue by resetting dirty flag on component store.

    I have the same issue with my Windows10 Home (1607), and it doesn't allow me to sfc /scannow, even on safe mode. I tried many thing like recovery  mode command prompt but no avail.

    I found that my component store has dirty flag, when I looking C:\Windows\Logs\CBS\CBS.log .

    2017-09-06 04:57:32, Info                  CSI    00000006 Component store has dirty flag; cannot create transactions against it at this time.

    2017-09-06 04:57:32, Error                 CSI    00000007@2017/9/5:19:57:32.365 (F) onecore\base\wcp\componentstore\csd_transact.cpp(3531): Store corruption detected in function CCSDirect::CreateTransaction expression: 0

      RegistryCorruption on resource '\Registry\Machine\COMPONENTS\StoreDirty'[gle=0x80004005]

    Then, I searched a bit and found the way to reset the flag here:

    https://www.sevenforums.com/windows-updates-activation/362706-windows-update-error-80073712-a.html

      NoelDP wrote:

    Try this..

    Open an Elevated Command Prompt, and run the following commands...

    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

    REG DELETE /v HKLM\COMPONENTS\StoreDirty

    reboot and try SFC again.

    What I've actually done is to launch regedit and do backup registry via export all, click File -> "Load hive" to open C:\Windows\System32\config\COMPONENTS and input "comp" as attach point,

    and renamed HKEY_LOCAL_MACHINE\COMPONENTS\StoreDirty to StoreDirty_backup via context menu, and unloaded the "comp".

    After that, sfc /scannow worked successfully.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-07-13T11:34:16+00:00

    In this scenario i would prefer to perform this command in safe mode and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more