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

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>

Please run the new DISM command instead:

DISM /Online /Cleanup-Image /RestoreHealth

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>

Andre,

Thanks from me too :)  This worked perfectly!

• 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

• 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

Please run the new DISM command instead:

DISM /Online /Cleanup-Image /RestoreHealth

it can download missing files.

Please run the new DISM command instead:

DISM /Online /Cleanup-Image /RestoreHealth

it can download missing files.

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

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

got the same error with dism

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

                                     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!

Please run the new DISM command instead:

DISM /Online /Cleanup-Image /RestoreHealth

it can download missing files.

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.

It worked for me as well -- amazing!   I scoured the web and this solution worked perfectly for the exact same error.

Very awesome! 

Worked

Mr_Wilber

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.