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 No 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 No 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 No comments

62 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-01-16T16:06:56+00:00

    Thanks to everybody!

    It worked for me too.

    The funny thing is that the "checkhealth" command didn't find any corruption, whereas the "restorehealth" could repair the unseen damage.

    I tried "checkhealth" first. No damage!

    Second try "sfc /scannow". That damn "prncacla.inf" was still there.

    Third try "restorehealth", which did find and repair the file.

    Fourth command "sfc /scannow" once again. No more integrity violation found.

    Sorry for not attaching the entire DOS results. I don't think you would like to study Italian.

    For AlbertRa, who was complaining for slow startups, I would suggest to check his hard disk.

    Some time ago I had a similar experience. My thre-month-old (!!) HD was almost gone and some bad sectors couldn't be read.

    Enjoy yourselves!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-01-16T08:43:36+00:00

    Glad to help!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-01-15T16:52:14+00:00

    That worked for me, too!  Thanks for finding and sharing that link!

    Was this answer helpful?

    0 comments No comments