CBS log still reporting errors after SFC.exe fix

[jonathan1173]

I have a Toshiba netbook running Windows 8 32 bit. The CBS log is still showing unrepairable errors after I ran SFC/scannow, SFCFix.exe, and DISM Restore Health. Here is a line from CBS log, and I have attached the entire log as well. Any thoughts on this?

CSI 0000038a [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

 

[Tekno Venus]

Hi,

Please see: https://www.sysnative.com/forums/wi...prncacla-inf-corruptions-windows-8-8-1-a.html

Stephen

 

[niemiro]

Hello, and welcome to Sysnative!

Does sfc /scannow now come up clean (no corruptions detected)? The reason I ask is that CBS.log stores not only the current run of SFC/Windows Update, but all past runs too. Therefore, if you have ever had a problem, which you have since fixed, it will still show in the historic records of CBS.log, despite your PC being in fine working order.

Therefore, if your sfc /scannow comes up clean, all is well. If your sfc /scannow doesn't come up clean, then we have a problem we need to fix.

Richard