Hash mismatch

in the above the sfc /scannow failed

it had failed several times over the past week

running the dism commands fixes each time whatever sfc/scannow failed to correct.

if anyone understands what scannow is not able to fix please explain what that is

if anyone understands what dism commands are able to fix that scannow commands cannot fix please explain

if anyone understands why there are recurrent problems please explain

if anyone knows a direct way to find the cbs.log file when it is not found by going to my computer then windows file then looking for the file which is not there on 2 computers.....only temp found on each was empty...........fortunately i had everything search and was able to find the cbs.log but i prefer a direct look and find method.

what else can i do to work up the problems for the recurrent conflicts or corruption?

the event viewer logs many error, warning, critical.......anything specific here to look for?

again i run chkdsk /f /r , sfc /scannow, defender, defrag, ccleaner etc as routine maintenance

thx

I think this has been answered by others in this forum already, starting with Andrei Vida who gets my kudos.

First of all, you'll find the CBS.log file in C:\Windows\Logs\CBS\CBS.log.

However you wont be able to open it.  There are a couple of options.  Make a copy of the CBS.log and rename the copy to CBS.txt, then open that copy with notepad.  Then search for the string "[SR]" using edit>find.  Everywhere that string comes up identifies a problem that sfc has found that somehow needs to be addressed.  Another easier way is to open a command prompt with administrator privileges and  run "findstr /c:"[SR]" %windir%\logs\cbs\cbs.log".  That will create an output file with only the relevant error portions of the otherwise HUGE CBS.log, which will make your job a whole lot easier.

I hope that answers part of your question.  But that isn't what you should try first if you already know your problem is  CNBJ2530.DPB ....The bigger issue is how to fix the problems with CNBJ2530.DPB that you and others are experiencing.

What worked for me is EXACTLY what Andrei Vida suggested:  run the following two commands from the command prompt (with admin privilege).  The

dism /online /cleanup-image /checkhealth

dism /online /cleanup-image /restorehealth

if you are lucky like I was, a run of sfc /scannow following the execution of these two commands will produce no sfc errors, i.e., DISM fixes the problem. 

IF THAT DOES NOT WORK, then you are left needing to replace the faulty files found by sfc with good versions.  (I did not need to do this, so follow these directions, gleaned from others in this blog, with care.)  Basically, if I understand the previous entries in this blog correctly, what SFC is telling you is essentially the following:

"BAD FILE FOUND BY SFC"

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

SUPPOSED FILE SFC CHECKED AGAINST:

C:\Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB

So you need to replace the bad one with the good one (or, I'd suppose if things are really bad, both from downloaded versions if things are really bad, but don't try that first). 

And before replacing any files, you should look around some more and DOUBLE CHECK that I have the 'sense' of the last two file locations correct (they may be reversed).  That is, the bad file might be the one in \Windows\WinSxS and the good one might be in \Windows\System32.  So make sure you get that right before you go about replacing anything. 

And there also are other entries in this blog about needing to worry about Genuine Windows Software issues when you replace the bad file.  I recommend you read through those entries (I didn't have to since DISM worked for me) to see if there is anything further you need to do.

Hope this helps

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