Hash mismatch

Anonymous
2013-01-07T10:37:18+00:00

Does anybody know how to fix this problem? It is related to a Windows 8 64-bit platform and seems to be rather common (see Web results for "Amd64\CNBJ2530.DPB" of prncacla.inf*"*).

No apparent malfunctions, but very slow startup, especially the first one at morning.

Below what appears in the CBS.log after multiple sfc /scannow(s) that say it is impossible to repair some damaged files.

2013-01-07 08:31:12, Info                  CSI    000006fc [SR] Beginning Verify and Repair transaction

2013-01-07 08:31:12, Info                  CSI    000006fd Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :

Found: {l:32 b:YCyRZUKsIhOc05lCRHw+OKYmzq2wt2CJT7Rixym+Hs4=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

2013-01-07 08:31:12, Info                  CSI    000006fe [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-07 08:31:12, Info                  CSI    000006ff Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :

Found: {l:32 b:YCyRZUKsIhOc05lCRHw+OKYmzq2wt2CJT7Rixym+Hs4=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

2013-01-07 08:31:12, Info                  CSI    00000700 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-07 08:31:12, Info                  CSI    00000701 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"

I have tried to fix by uninstalling  and re-installing KB2769165, with no result. Any other ideas?

Windows for home | Previous Windows versions | Performance and system failures

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
2013-01-15T07:08:36+00:00

I found something very interesting here:

http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/26f35def-6f55-4c07-9ba8-73e2d402e6cc

I am going to try the dism /online /cleanup-image /checkhealth command and see how it goes.

L.E. Actually, there are 2 commands to run:

dism /online /cleanup-image /checkhealth

dism /online /cleanup-image /restorehealth

I will be back with the results.

Very Late Edit:

There is also a tool I found recently that helped me solve this issue in Windows Server 2012 R2.

The above commands didn't work so I ran this tools and it solved the problem. You can download the tool here:

http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/

Was this answer helpful?

80+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2013-01-12T08:08:11+00:00

I have been checking this issue through other Microsoft Communities (England, France, Italy). According to many experts the problem is not significant. Moreover, looks like sfc often reports false errors. Both my PCs (1 laptop Windows 8 Pro 64-bit and 1 desktop Windows 8 32-bit with Media Center) report the same "hash mismatch" but don't seem to show any malfunction. No Canon printers installed! I hope that Microsoft will solve this mystery ... sooner or later.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

62 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-01-12T15:43:05+00:00

    i have this error too, but i does not have any Canon devices! so i think it's not related to Canon or the Drivers.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-01-12T20:45:37+00:00

    Same issue with my PC.  I have been on the phone and online with several Microsoft Technicians and no success.  In my situation, the PC hangs right at the Windows logo screen.  I have to do a a hard shut down and restart the PC.  It normally starts after that but the fact that I had to do a hard shutdown triggers a RAID verification by the Intel RAID software.  Fortunately, I can cancel the scan as 99% of the time no errors are found.  I'm not even sure if the two errors are related.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-01-13T07:20:26+00:00

    As said by Evert CFIT, that prncacla.inf file is referred to a printer driver (exactly a Canon Pixma iP90.

    The C:\Windows folder also contains drivers for all kinds of hardware for possible future use.

    The "hash mismatch" therefore seems not significant. This is my conclusion.

    As to AlbertRa's problems, I suggest him to take a look at the Event Viewer (right click at the left/lower corner of the screen). Once opened the Viewer, go to Custom Viewer and then to Administrative Events. By selecting the various Errors it is possible to find what blocks his PC at the logo screen.

    Was this answer helpful?

    0 comments