[SOLVED] SFCFix reports no issues but sfc/scannow reports CNBJ2530.DPB issue

[michaelhigh076]

I'm still getting errors, so I tried running
SFC /Scannow, and get the "corrupt files, but can't repair".

Tried dism /online /cleanup-image /restorehealth

But it fails as well. I'd simply format the computer, and start over, but don't have the time to do that given the amount of software installed on it, (developing for the netmf platform, autocads, ect).

Any help would be appreciated.

 

[Go The Power]

Hello and welcome to the forum :)

The error is with the following file:

2014-12-27 11:26:25, Info                  CSI    00000854 [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-12-27 11:26:28, Info                  CSI    00000855 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:dCazHyZJKLadC6y3nJHVxKDt2Igw8ICkMBZRtc+N/M4=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

Now it is time to repair this file..

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

SFC /SCANNOW

1. Right click on the
   
   button
2. Click on Command prompt (Admin) => Press Yes on the prompt
3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
4. Please wait for this to Finish before continuing with rest of the steps.

Convert CBS.log to CBS.txt

1. Right click on the
   
   button
2. Click on Run => Inside the run box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

3. Press Enter
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

 

[michaelhigh076]

Sorry,, reread the steps, missed the zip part...

 

[michaelhigh076]

Also, as a side note, made sure I fully updated windows,, rebooted several times,, and have ran both the sfc /scannow & dism /online /cleanup-image /restorehealth after clean reboots...

 

[Go The Power]

Did SFC or DISM report any issues?

How did the SFCFix file replacement go?

 

[michaelhigh076]

I apologize, but that seems to fix the specific issue I had. I think I may have gotten a little to sure of myself in disabling items (I think the root cause of this was a rootkit virus that I got out of a questionably sdk (well more accurately sample code),, the risk for the code outways buying a new computer.., and I'm usually pretty good at being careful, but isn't that what she said?).. I am still having the issues I thought this would fix,, but

YES, I really appreciated the help, and will make a donation. THANK YOU,


the issue with cnbj2530 has been resolved, I just haven't had time to run dism yet.... Its been a busy couple of days..



Michael.

 

[Go The Power]

Your welcome Michael, I am glad to hear everything is working now :)