Windows can't repair even with sfc /scannow

24

7

I did a clean install of Windows 8, then installed the Windows 8.1 update (after all other updates).

enter image description here

CBS Log: CBS Log on Google Drive

Important pieces of the log:

Found: {l:32 b:LrOXAtJDCCTN+z+D1bKj7ogYIrX7sfCCDh+wVBfsrCQ=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-05-17 21:35:38, Info                  CSI    00000505 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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
2014-05-17 21:35:40, Info                  CSI    00000506 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:LrOXAtJDCCTN+z+D1bKj7ogYIrX7sfCCDh+wVBfsrCQ=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-05-17 21:35:40, Info                  CSI    00000507 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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
2014-05-17 21:35:40, Info                  CSI    00000508 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
2014-05-17 21:35:43, Info                  CSI    00000509 [DIRSD OWNER WARNING] Directory [ml:520{260},l:138{69}]"\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\NetSecurity\en" is not owned but specifies SDDL in component Networking-MPSSVC-WMI.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

And:

Found: {l:32 b:LrOXAtJDCCTN+z+D1bKj7ogYIrX7sfCCDh+wVBfsrCQ=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-05-17 21:42:12, Info                  CSI    00000888 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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
2014-05-17 21:42:13, Info                  CSI    00000889 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:LrOXAtJDCCTN+z+D1bKj7ogYIrX7sfCCDh+wVBfsrCQ=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-05-17 21:42:13, Info                  CSI    0000088a [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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
2014-05-17 21:42:13, Info                  CSI    0000088b [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
2014-05-17 21:42:13, Info                  CSI    0000088c [SR] Repair complete

GeekyDewd

Posted 2014-05-18T06:03:32.813

Reputation: 827

2btw, Microsoft is now investigating why this file gets corrupted so often. They also found the issue internally on their systems. – magicandre1981 – 2014-08-17T06:09:52.760

@magicandre1981, So how is the investigation coming along? – Pacerier – 2015-04-21T21:38:14.930

@Pacerier They saw it internally on several systems, but never found the cause and stopped the investigation – magicandre1981 – 2015-04-22T04:24:54.757

1@magicandre1981, So is the conclusion "due to hardware problems", or is the conclusion there's a bug somewhere in there but they didn't managed to find it? – Pacerier – 2015-04-24T02:36:19.143

1@Pacerier there is a bug, but they have no idea where the bug is. – magicandre1981 – 2015-04-24T04:08:38.100

Answers

-1

The problem seems to be caused by using a third party theme, after setting it back to default, it's fine.

GeekyDewd

Posted 2014-05-18T06:03:32.813

Reputation: 827

2no, the CNBJ2530.DPB is part of a printer driver and was a known issue in Windows 8.1 that the file corrupts itself. – magicandre1981 – 2016-10-09T06:52:05.877

Do you feel good saying that while thinking you're right? I never had a printer on that machine. Also problem went away after removing my third party theme and switching back to the default. – GeekyDewd – 2016-11-11T06:06:28.003

1this printer file is part of Windows, no matter if you use a printer or not. I had the same issue and submitted it to Microsoft 2 years ago. They confirmed that the file gets corrupted randomly (also on devices inside Microsoft), but they never found a cause. For Windows 10 I haven't seen this – magicandre1981 – 2016-11-11T15:36:18.723

24

In Windows 8.x run this new DISM command to repair corrupted files from a cmd.exe, started as admin:

DISM /Online /Cleanup-Image /RestoreHealth

It can download the corrupted files if needed.

magicandre1981

Posted 2014-05-18T06:03:32.813

Reputation: 86 560

1

Comments are not for extended discussion; this conversation has been moved to chat.

– Journeyman Geek – 2016-08-18T07:26:57.257

Asked: 2014-05-18T06:03:32.813

Viewed: 14 282 times

Active: 2017-06-14T20:05:13.920