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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-01-12T06:36:40+00:00

    I have the same problem! I also have Windows 8 Pro 64 bit with media center ... SFC /scannow cannot repair the amd64_prncacla.inf problem.

    This is my CBS.log Error:   Found: {l:32 b:z56JF4bVtovyS1MNnLQtP+KeB93SnGae8rzy7LzYMQ4=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

    2013-01-12 07:31:35, Info                  CSI    00000829 [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-12 07:31:35, Info                  CSI    0000082a 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:z56JF4bVtovyS1MNnLQtP+KeB93SnGae8rzy7LzYMQ4=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

    2013-01-12 07:31:35, Info                  CSI    0000082b [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-12 07:31:35, Info                  CSI    0000082c [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-01-09T16:38:25+00:00

    Hi:

    I'm not sure if this is completely related to your post, however, the file reference is the same.  Yesterday I ran a routine scc /scannow just to check that no system files were corrupt.  Upon completion, I was informed that it found corrupt files that it couldn't fix.  I was able to open the CBS file and found the following error:

    CSI    00000402 [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

    Here is where that file is located.

    C:\Windows\System32\DriverStore\FileRepository\prncacla.inf_amd64_9b92c72816d21e91\Amd64\CNBJ2530.DPB

    My PC (Dell XPS 8100, i5 (3.25 GHz), 6GB (DDR3) Ram Win 8 Pro)) appears to be running fine.  I've run several SFC scans since upgrading to Win 8 because on the first scan, I was notified of corrupt files that were successfully fixed.  On the 3 scan (after installing Media Center), received the same error message indicating successful fix.  I've contined to run SFC on a weekly basis, and until yesterday, everything has been OK.  So I don't know if this is a concern that needs attention or simply ignore.

    Thanks for your help on this.  -Jack

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-01-09T16:32:51+00:00

    Same SFC problem here, on multiple Win8 computers... To be more exact: 1 out of 6 computers doesn't have it (yet)...

    EDIT: but no signs of slow startups btw.

    The error in the CBS.log implies a file hash mismatch:

    "2013-01-09 17:01:25, Info                  CSI    000006cd 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:gSKgtXuoRhmhQwrFs1rUNbjO7QFVr7009W1FWP3KKHI=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}"

    Funny thing is that the file "prncacla.inf" found in the folder "\SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12" only references a stupid Canon printer driver (which, of course, has never been installed and never will be on any of the affected machines).

    My explanation is that Microsoft messed up with some driver update(s) recently. Possibly by update KB2769165? (EDIT: removing and reinstalling did not fix the issue)

    I'm definitely waiting for a (quick, fast and correct!) fix from Microsoft, as reinstalling the affected computers doesn't help: the problem will appear again, eventually.

    I don't think it's a serious error anyway, but it's just a PITA having to search through CBS.log every time: System File Checker should only report nothing's wrong anyway ;-)

    Was this answer helpful?

    0 comments