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-11-29T04:02:14+00:00

    I used everything search and entered cbs.log

    One file was produced

    I right clicked on it and attempted to paste into notepad and it produced no visible entry

    Then I right clicked on the cbs.log and renamed it cbs.logtext.  Then i right clicked on the new name and copied and again it faled to produce anything in notepad.

    Then I opened command prompt as an administrator and entered:

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

    It produced a long list.

    I did not know how to copy what it produced.

    There were many repair transactions.

    The very last entry displays repair complete.

    Would you please explain:

    1. how you recommend searching for and finding the cbs.log
    2. each step that you make to rename it to be able to then copy and paste it into notepad and have a viewable result
    3. i was not able to edit the results and search  for [SR].  after following your reply to #2 is that a right click method?

    I run the sfc /scannow daily now

    I also run dism /online /cleanup-image /restorehealth daily

    The two new laptop computers from HP hang multiple times per day and the hangs do not respond to control alt delete.  Then I have to use the power on off and then upon restart there is the keyboard country menu for windows 8.0 or 8.10.  I don't know why these computers keep hanging or failing.   The most recent message on Wednesday 11/27 on this computer was: 

    Kernel_data_impage_error (cdd.dll) 

    your pc ran into a problem and needs to restart.  We're just collecting some error info and then you can restart 0% complete...........boot device not found.  please install an operating system on your hard disk.  hard disk (3F0) 

    I contacted HP and they will send to me a replacement HD.

    I ran the HP diagnostic studies on the two new laptops for just the HD and there were no detected problems with either short or long tests.  Last night I ran both computers with their loop studies where it will stop once an error is found.  This was for all diagnostic studies, not just the HD studies.   It went through 3 loops on each computer and no errors were found.

    In the past I had ran chkdsk /f /r and recently ran chkdsk /spotfix

    I had found no benefit in running the dism commands other than restorehealth and no longer run checkhealth or scanhealth   http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

    Please comment on the questions above and if you have any idea how to troubleshoot the two computers please help too.   (the computers are HP dv7 -7217nr  http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03507437

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-11-27T19:36:28+00:00

    I also just found this page which may be useful to others who find this thread that the dism and sfc commands do not fix the issue -

    http://www.ampercent.com/repair-corrupt-windows-files-system-file-cheker-windows7/7743/

    There is also

    Dism /Online /Cleanup-Image /ScanHealthWhich will scan the image to check for corruption and then you run Dism /Online /Cleanup-Image /RestoreHealthDism /Online /Cleanup-Image /CheckHealth - If I read the documentation correctly, this just seems to see if corruption has already been detected.
    

    -Nyle

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-11-27T19:33:26+00:00

    It might help to look at what files are corrupted. This command should dump into a file just the corrupted files. You may need to change permissions on the cbs.log or copy it to another file to make it accessible. You'll end up with a file called sfcdetails.txt.

       Then you can research the files to find details on them or potentially replace them from backups on the machine.

    findstr /C:”[SR] Cannot repair member file” %windir%\logs\cbs\cbs.log >sfcdetails.txt

    Was this answer helpful?

    0 comments No comments