none
sfc /scannow - Cannot repair member file RRS feed

  • Question

  • I ran sfc /scannow and then filtered the results to a file. There are several errors that were flagged that could not be repaired.  They seem to be related to an update "Package_83_for_KB2769165".

    What can I do to fix the files?  

    2013-01-14 15:42:22, Info                  CSI    0000030d [SR] Verifying 100 (0x00000064) components
    2013-01-14 15:42:22, Info                  CSI    0000030e [SR] Beginning Verify and Repair transaction
    2013-01-14 15:42:27, Info                  CSI    0000030f Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
      Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
    2013-01-14 15:42:27, Info                  CSI    00000310 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2013-01-14 15:42:46, Info                  CSI    00000311 Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
      Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
    2013-01-14 15:42:46, Info                  CSI    00000312 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2013-01-14 15:42:46, Info                  CSI    00000313 [SR] This component was referenced by [l:160{80}]"Package_83_for_KB2769165~31bf3856ad364e35~x86~~6.2.1.0.2769165-10628_neutral_GDR"
    2013-01-14 15:42:48, Info                  CSI    00000314 [SR] Verify complete
    2013-01-14 15:42:48, Info                  CSI    00000315 [SR] Verifying 100 (0x00000064) components
    2013-01-14 15:42:48, Info                  CSI    00000316 [SR] Beginning Verify and Repair transaction
    2013-01-14 15:42:52, Info                  CSI    00000317 [SR] Verify complete
    2013-01-14 15:42:52, Info                  CSI    00000318 [SR] Verifying 100 (0x00000064) components
    2013-01-14 15:42:52, Info                  CSI    00000319 [SR] Beginning Verify and Repair transaction
    2013-01-14 15:42:57, Info                  CSI    0000031a [SR] Verify complete
    2013-01-14 15:42:57, Info                  CSI    0000031b [SR] Verifying 100 (0x00000064) components
    2013-01-14 15:42:57, Info                  CSI    0000031c [SR] Beginning Verify and Repair transaction
    2013-01-14 15:43:03, Info                  CSI    0000031d [SR] Verify complete
    2013-01-14 15:43:03, Info                  CSI    0000031e [SR] Verifying 100 (0x00000064) components
    2013-01-14 15:43:03, Info                  CSI    0000031f [SR] Beginning Verify and Repair transaction
    2013-01-14 15:43:17, Info                  CSI    00000323 [SR] Verify complete
    2013-01-14 15:43:17, Info                  CSI    00000324 [SR] Verifying 67 (0x00000043) components
    2013-01-14 15:43:17, Info                  CSI    00000325 [SR] Beginning Verify and Repair transaction
    2013-01-14 15:43:21, Info                  CSI    00000326 [SR] Verify complete
    2013-01-14 15:43:21, Info                  CSI    00000327 [SR] Repairing 1 components
    2013-01-14 15:43:21, Info                  CSI    00000328 [SR] Beginning Verify and Repair transaction
    2013-01-14 15:43:22, Info                  CSI    00000329 Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
      Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
    2013-01-14 15:43:22, Info                  CSI    0000032a [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2013-01-14 15:43:22, Info                  CSI    0000032b Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
      Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
    2013-01-14 15:43:22, Info                  CSI    0000032c [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2013-01-14 15:43:22, Info                  CSI    0000032d [SR] This component was referenced by [l:160{80}]"Package_83_for_KB2769165~31bf3856ad364e35~x86~~6.2.1.0.2769165-10628_neutral_GDR"
    2013-01-14 15:43:22, Info                  CSI    0000032e [SR] Repair complete
    2013-01-14 15:43:22, Info                  CSI    0000032f [SR] Committing transaction
    2013-01-14 15:43:23, Info                  CSI    00000334 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    Monday, January 14, 2013 4:07 PM

Answers

  • Please run the new DISM command instead:

    DISM /Online /Cleanup-Image /RestoreHealth

    it can download missing files.


    "A programmer is just a tool which converts caffeine into code"

    • Marked as answer by dghtpc Monday, January 14, 2013 10:43 PM
    Monday, January 14, 2013 8:08 PM
    Answerer

All replies

  • sfc /scannow returns 

     Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    C:\WINDOWS\system32>

    Monday, January 14, 2013 5:35 PM
  • Please run the new DISM command instead:

    DISM /Online /Cleanup-Image /RestoreHealth

    it can download missing files.


    "A programmer is just a tool which converts caffeine into code"

    • Marked as answer by dghtpc Monday, January 14, 2013 10:43 PM
    Monday, January 14, 2013 8:08 PM
    Answerer
  • Andre,

    Thanks - what an interesting command. I had also tried autorepair (or whatever it's called) without success.

    But your DISM suggestion fixed it!

    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
    
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    
    Image Version: 6.2.9200.16384
    
    No component store corruption detected.
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    
    Image Version: 6.2.9200.16384
    
    [==========================100.0%==========================]
    The restore operation completed successfully. The component store corruption was
     repaired.
    The operation completed successfully.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>

    Monday, January 14, 2013 10:42 PM
  • Andre,

    Thanks from me too :)  This worked perfectly!

    Sunday, September 29, 2013 9:57 PM
  • Thanks! On Windows 8-64 no errors.
    • Proposed as answer by V-Dub Thursday, January 30, 2014 12:05 PM
    • Unproposed as answer by V-Dub Thursday, January 30, 2014 12:05 PM
    Friday, December 6, 2013 11:42 AM
  • Please run the new DISM command instead:

    DISM /Online /Cleanup-Image /RestoreHealth

    it can download missing files.


    "A programmer is just a tool which converts caffeine into code"

    The DISM command doesn't work in an environment that runs Windows Server Update Services, unless you configure the Specify settings for optional component installation and component repair setting:

    http://technet.microsoft.com/en-us/library/hh825020.aspx#BKMK_SetGPO

    The default source location is Windows Update. Before configuring this, the output is displayed as below:

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.16384

    Image Version: 6.3.9600.16384

    [==========================100.0%==========================]

    Error: 0x800f0906

    The source files could not be downloaded.
    Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    When configuring Specify settings for optional component installation and component repair, select Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).

    Run the DISM command again and the operation will complete successfully.

    Thursday, January 30, 2014 12:19 PM
  • Please run the new DISM command instead:

    DISM /Online /Cleanup-Image /RestoreHealth

    it can download missing files.


    "A programmer is just a tool which converts caffeine into code"

    The DISM command doesn't work in an environment that runs Windows Server Update Services, unless you configure the Specify settings for optional component installation and component repair setting:

    http://technet.microsoft.com/en-us/library/hh825020.aspx#BKMK_SetGPO

    The default source location is Windows Update. Before configuring this, the output is displayed as below:

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.16384

    Image Version: 6.3.9600.16384

    [==========================100.0%==========================]

    Error: 0x800f0906

    The source files could not be downloaded.
    Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    When configuring Specify settings for optional component installation and component repair, select Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).

    Run the DISM command again and the operation will complete successfully.

    or use note pad create a repair.bat file, copy and paste the text, run as admin.

    net stop wuauserv

    cd %systemroot%\SoftwareDistribution

    ren Download Download.old

    net start wuauserv

    net stop bits

    net start bits

    net stop cryptsvc

    cd %systemroot%\system32

    ren catroot2 catroot2old

    net start cryptsvc

    Then  try this again

    DISM /Online /Cleanup-Image /RestoreHealth

    http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/dismexe-online-cleanup-image-restore-health-failed/668ef107-5f4c-4959-ba93-76d052452315

    Edit: I had the same error code as you not to long ago, the above repairbat fixed that problem.

    Little easier then configuring paths and running dism. I have fixed the error doing it that way too. Below is the link how to my how to. check my post

    http://social.technet.microsoft.com/Forums/windows/en-US/d126a392-1491-4371-962c-1d1269806aff/win-81-pro-dism-online-cleanupimage-restorehealth-returns-error-14098?forum=w8itprogeneral#f2ae2d58-aad6-446a-a648-b709ec87b5d2



    • Edited by colakid Thursday, January 30, 2014 1:10 PM
    • Proposed as answer by DTM450 Wednesday, July 10, 2019 3:19 AM
    • Unproposed as answer by DTM450 Wednesday, July 10, 2019 3:20 AM
    Thursday, January 30, 2014 12:51 PM
  • If  I run dism /online /cleanup-image /restorehealth   it has the same message as some ... the component store corruption was repaired .... operation completed successfully.

    But if run the command again right after ... it says the same thing.  and again.

    Well, if the thing was repaired successfully why does it keep finding corruption and promising it is fixed?

    It is the same with the other recommended ultilities for finding store issues.

    one does not get much faith  when a program  keeps saying it fixed something only to discover it all overagain every time run same command  just to see if it really was fixed :(

    My issue is that no store APP updates ever appear in the upper right corner of the store anymore in windows 8.1 pro.

    But i'm actually only trying out new ways to check for corruption to see if I can find if there really is any corruption.  And so far, all I am finding are sugar pills.   corruption found and fixed ..just don't run me right away again to find out I am lying to you. heh.




    • Edited by RedStarSQD Wednesday, February 12, 2014 9:59 PM
    Wednesday, February 12, 2014 9:55 PM
  • got the same error with dism

    bit in win 8.1 there is no group policy edit so how to fix it ?

    Wednesday, February 26, 2014 12:12 PM
  •   

                                         Win8.1

    My Image Version is: 6.3.9600.16384 & after running the DSIM.exe commands ;

      First," dism /online /cleanup-Image /checkhealth"

                                               &

      Second,"dism /online /cleanup-Image /restorehealth" 

     I was then able to successfully run the SFC /SCANNOW command & repair corrupted system files!

                                                            THANK YOU!

    Monday, March 10, 2014 9:53 PM
  • Please run the new DISM command instead:

    DISM /Online /Cleanup-Image /RestoreHealth

    it can download missing files.


    "A programmer is just a tool which converts caffeine into code"

    WOW!

    I can't thank you enough for this answer.

    Been struggling to try and get this error fixed when running 'sfc /scannow'

    And you suggestion of running the command line suggested by you, worked perfectly.

    DISM /Online /Cleanup-Image /RestoreHealth

    Once again. Many thanks.

    Tuesday, April 15, 2014 1:37 PM
  • Thanks for this information. Very helpful, and resolved.
    Wednesday, August 13, 2014 10:34 PM
  • Thanks broThank you verry much, you saved me from reinstalling windows.

    It should also forwarded to AMD cause it can fix some of "Display driver stopped responding and has recovered" errors as it is my case.

    Wednesday, August 20, 2014 3:05 PM
  • It worked for me as well -- amazing!   I scoured the web and this solution worked perfectly for the exact same error.

    Saturday, January 24, 2015 4:09 AM
  • Very awesome! 

    Worked

    Mr_Wilber

    Friday, March 13, 2015 9:54 PM
  • Hello, 

    I tried using this an I am getting an error as follows;

    The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

    Error: 0x800f081f

    DISM failed. No Operation was performed.

    Please kindly help.

    I cannot open most settings in my Control Panel. This is the original problem. I have been searching for solutions and have also tried sfc /scannow.

    Thanks in Advance.

    Monday, June 8, 2015 2:39 AM
  • Thanks a bunch Andre  /bows to the master  I was /face-to-keyboard for a couple hours trying to work out this problem and then I came across this post of yours and I had it fixed in about 10 minutes. You are AWESOME!
    Monday, July 6, 2015 10:07 PM
  • When running the DISM commands they create a CBS log.

    If interested you can view this file to see corruptions that it found.

    And you can see corruptions that it repaired.

    Before using DISM commands you may have used administrative command prompt and entered sfc /scannow.

    When running a sfc /scannow you can also view a CBS.log.  This log though is much harder to interpret.  When clicking on edit there is a find menu and there you can enter the word "corrupt" and then advance one at a time to view the files that it found corrupt.

    For windows 7 the dism checkhealth and restorehealth produce error messages.  The restore health is unfortunately unavailable for windows 7.  But for windows 7 you can use scanhealth and check the cbs.log for corruption.

    To view CBS.logs you can open notepad as an administrator.

    Then open the appropriate file:

    C:\windows\logs\cbs\cbs.log

    C:\windows\logs\cbs\checksur.log

    etc.

    In summary when attempting to scan and fix windows cbs logs are created.  They can be viewed to get some insight into the corruption and fixes.  To view them one method is to open notepad as an administrator.  Then open the appropriate CBS file.


    Monday, October 5, 2015 5:45 AM
  • Help. Run DISM /Online /..    . Error: 87 :(
    Wednesday, May 11, 2016 5:08 AM
  • Error: 87
    Capture the full message.  You made a typo (or weren't in the right state for the Administrator Command Prompt).


    Robert Aldwinckle
    ---

    Wednesday, May 11, 2016 2:36 PM