sfc /scannow error - Cannot repair file Amd64\CNBJ2530.DPB

M

mcoad

Member
Joined
Jan 12, 2015
Posts
12
I have a Toshiba S50 Laptop running Windows 8.1, 64-bit. Windows Update has been failing for several weeks on "Windows 8.1 Update for x64-based Systems (KB2919355)", with Error Code 80073712.

I've tried running sfc /scannow several times and the CBS.log shows the corrupted file is "Amd64\CNBJ2350.DPB".

I've tried running "dism /online /cleanup-image /restorehealth" several times as well, and it gets to 40% and stays there for many hours before I kill it (although Task Manager is still showing disk activity even after many hours of running dism). Should I let this run for days, if need be?

I've tried running the updated version (6-30-14) of SFCFix.exe, which runs dism and hangs at 40%, the same as when I run dism myself.

I read something about running dism with the /remove-package option, and then running it again with the /startcomponentcleanup option, but this seems like grasping at straws to me.

So, I decided to start a new thread in hopes someone can help me. I see that others have been helped with this problem through what appears to be customized scripts. I've uploaded my CBS.log and dism.log files here. Thank you for your help.

Mike
 

Attachments

Hello and welcome to the forum.

This is the little file that is giving you so much grief.
Code: 
2015-01-12 14:39:42, Info                  CSI    0000080d 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:UhrohSp1EDPiJik1Op+ff2ylb8Yzx6CgMjTHPLT9t94=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

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
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    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
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    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
 
I cannot get the SFCFix.zip file. When I click the link, it takes me to my "Inbox" (www.sysnative/forums/private.php), but there is no message from you there. I'll wait to hear back from you. And thank you for your help. I really need it.
 
The CBS.log file says there is a hash mismatch, but when I compare the two files below (using WinMerge), it says they are identical (and both were last modified 6-18-2013, about when I got this laptop).

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

and

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

are identical, according to WinMerge.

I realize MANY people have run into this problem, and that people on this web site (thankfully) have come up with a "fix" of sorts. But no one seems to know the cause of this issue, and neither Microsoft nor HP(?) are taking any responsibility or trying to resolve it. In my case, the failure of Windows Update started happening a few months ago (two or three), but had been working fine prior to that point. Since these files have not been modified since I first bought this laptop in June of 2013, I think the root cause of the problem lies somewhere else. Could the hash mismatch itself be in error? That is, could it be a "false positive"? Could the true "bug" be in the Windows Update process itself? Who can "debug" Windows Update other than Microsoft (you guys, probably)? Anyway, I will attempt your solution when I can get the SFCFix.zip file. Thanks, again.

Mike
 
Sorry Mike, I forgot to press send on that PM last night!

The has mismatch is with:
Code: 
2015-01-12 14:39:42, Info                  CSI    0000080d 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:UhrohSp1EDPiJik1Op+ff2ylb8Yzx6CgMjTHPLT9t94=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

SFC doesnt actually compare the has with another file, what it does is compare the SHA256 hash of a file to a manifest file. Inside this manifest file has the correct hash, the one you can see in Expected.

The file you listed above that points to the DriverStore is actually a Hardlink, meaning that both these files are actually the same, they are just appearing in two spots :)

Alex
 
Thank you, Alex. The contents of SFCFix.txt are pasted here below. Also, I have uploaded the CBS.log file, renamed to CBS.txt. Everything seems to have been fixed, but I'll wait for your reply before I attempt to rerun Windows Update. Thanks, again.

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2015-01-15 16:38:49.483
Using .zip script file at C:\Users\Dave\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully  took permissions for file or folder  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB

Line blocked (SFCFix.txt): "C:\Users\Dave\AppData\Local\niemiro\Archive\SFCFix.txt" C:\WINDOWS\SFCFix.txt.
Successfully  copied file  C:\Users\Dave\AppData\Local\niemiro\Archive\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB  to  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB.

Successfully  restored ownership for  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB
Successfully  restored permissions on  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-01-15 16:38:50.155
Script hash: cxuG+fE8U5/0DcZcmw7wSiaRv4DGVQaglN8lvYkT5J4=
----------------------EOF-----------------------
 

Attachments

Thank you very much, Alex! I was able to run Windows Update successfully. I am pretty good at debugging technical issues myself, but this one had me stumped until I found this web site and you resolved it for me. Hard to believe Microsoft hasn't presented a solution to this problem which seems to have affected many people. Thanks, again!
 
Hi, Alex. I'm sorry, but I was mistaken. Windows Update DID fail again as it has been doing all along (other updates were successful). The package KB2919355 failed with Error Code 80073712 as it has been doing for months (I didn't realize it yesterday when I posted my "all clear" comment).

This morning, I ran sfc /scannow and it completed with a message saying there were no errors. Then, I ran Windows Update again, and it failed again with the same error code mentioned above. However, when I checked the CBS.log file, I do NOT see the same "hash mismatch" error message pertaining to the file Amd64\CNBJ2530.DPB as I had been seeing prior to running your fix. I do see a message about "no parent found, go absent" for this package (bottom of CBS.log), but it seems to have installed successfully.

So, the question becomes, "Why is Windows Update telling me this installation failed, and how do I clear this error message so it is not perpetually trying to install this update?". I have uploaded the new CBS.log file here (renamed to CBS.txt and compressed). Please let me know what you think. Thank you for bearing with me.

Mike
 

Attachments

Alex, since my issue now is not specifically related to sfc /scannow (as my original title indicates), should I start a new thread for this? Thank you.
 
We have a few other errors to look at now:

Code: 
2015-01-17 08:11:15, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-01-17 08:11:15, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-01-17 08:11:15, Info                  CBS    WER: Generating failure report for package: Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14, status: 0x80073712, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent

and

Code: 
2015-01-17 08:11:14, Error                 CSI    000006e6 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #8020278# from CFileInstaller::CommitChanges(...)[gle=0xd015001a]
2015-01-17 08:11:14, Error                 CSI    000006e7 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #8020277# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd015001a]
2015-01-17 08:11:14, Info                  CSI    0000036f SMI Primitive Installer [done]

2015-01-17 08:11:14, Error                 CSI    000006e8 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #6518349# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd015001a]
2015-01-17 08:11:14, Error                 CSI    000006e9 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #6518348# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd015001a]
2015-01-17 08:11:14, Error                 CSI    000006ea (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #6518347# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd015001a]
2015-01-17 08:11:14, Error                 CSI    000006eb (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #6518346# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd015001a]
2015-01-17 08:11:14, Error                 CSI    000006ec (F) HRESULT_FROM_WIN32(14098) #2255705# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80073712]
2015-01-17 08:11:15, Error                 CSI    000006ed (F) HRESULT_FROM_WIN32(14098) #2104379# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80073712]
2015-01-17 08:11:15, Error                 CSI    000006ee (F) HRESULT_FROM_WIN32(14098) #2104378# 47654366 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x80073712]

This error code (80073712) normally always refers to a corruption inside the registry hive called COMPONENTS.

The fun part is trying to find where the corruption is.

DISM Scan

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command DISM /Online /Cleanup-Image /RestoreHealth
  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
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    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

Please download the Freeware RegBak from here: Acelogix Software - Download products

Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.

Now right click on it > Send to > Compressed (zipped) folder.


Then please upload it to your favourite file sharing website (it will be too big to upload here). If you have a Microsoft Account, OneDrive could be a good choice: https://onedrive.live.com/, but any other will do just fine. Make sure to set the file as publicly accessible.
 
Hi, Alex. I've tried running "DISM /online /cleanup-image /restorehealth" several times, and it always gets to 40% and stays there for many hours before I kill it (although Task Manager is still showing disk activity even after many hours of running DISM). I let it run for more than 9 hours once before I killed it. Today, I let it run for about 2 hours, then killed it, and I am uploading the CBS.log and dism.log files here. As noted, there is still disk activity even after many hours of running the DISM command. Should I let this run for several days, if need be? Thank you.

Mike
 

Attachments

Hi Mike,

These are some files that DISM detected as corrupt:
Code: 
amd64_microsoft-windows-appx-deployment-client_31bf3856ad364e35_6.3.9600.17031_none_a6d321bbae27c0c9\AppXDeploymentClient.dll
amd64_microsoft-windows-a..audiocore.resources_31bf3856ad364e35_6.3.9600.17031_en-us_157fe5c8ee2ee80d\AudioSes.dll.mui
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\boxed-correct.avi
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\boxed-delete.avi
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\delete.avi
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\correct.avi
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\boxed-split.avi
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04\split.avi

As you have mentioned this high disc I/O from the HDD, and not looking at the above files (they are all from the same folder) this could be an indication of Hardware Failure.

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.

Warning:: Before doing anything it is a good idea to back up any data/files that are important to you, in case your hard drive is dying. Please see Here

Before we go any further, lets test the HDD.

What I recommend from here is to run some HDD diagnostics. Please follow the steps here for SeaTools HDD Diagnostics. Run a Long test and a Short test, then report back the results to this thread.

chkdsk /f scan

  1. Right click on the Start button and select Run as administrator
  2. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f
  3. Reboot
  4. Download ListChkdskResult.exe (by SleepyDude) from Here
  5. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Hi, Alex. Here is the log file from my running of chkdsk. It doesn't look like there were any problems, although some security descriptors (index entries) were cleaned up during the process. I have not been having trouble with my hard drive, but I did have to perform a "cold shutdown" a while back, which necessitated my resetting the motherboard (small pinhole on the bottom of the laptop). I don't think this has anything to do with my current issues, but I thought I'd mention it just in case.

I was thinking about running DISM and just letting it run for two or three days, if need be, but I will wait to hear from you and follow your advice instead. I owe you a pizza, at least, if you are ever in Florida. Thank you.


Code: 
ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 1/20/2015 10:25:53 AM >------
Category: 0
Computer Name: S50
Event Code: 1001
Record Number: 88240
Source Name: Microsoft-Windows-Wininit
Time Written: 01-20-2015 @ 15:01:13
Event Type: Information
User: 
Message: 

Checking file system on C:
The type of the file system is NTFS.
Volume label is TI10671000C.


A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  777216 file records processed.                                                        

File verification completed.
  4424 large file records processed.                                   

  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
  903238 index entries processed.                                                       

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      


Stage 3: Examining security descriptors ...
Cleaning up 4840 unused index entries from index $SII of file 0x9.
Cleaning up 4840 unused index entries from index $SDH of file 0x9.
Cleaning up 4840 unused security descriptors.
Security descriptor verification completed.
  63012 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36577064 USN bytes processed.                                                           

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 694812671 KB total disk space.
 416038312 KB in 524074 files.
    282440 KB in 63013 indexes.
         0 KB in bad sectors.
    906211 KB in use by the system.
     65536 KB occupied by the log file.
 277585708 KB available on disk.

      4096 bytes in each allocation unit.
 173703167 total allocation units on disk.
  69396427 allocation units available on disk.

Internal Info:
00 dc 0b 00 56 f5 08 00 d1 f7 10 00 00 00 00 00  ....V...........
dd 0a 00 00 48 00 00 00 00 00 00 00 00 00 00 00  ....H...........

Windows has finished checking your disk.
Please wait while your computer restarts.

-----------------------------------------------------------------------
 
Hi Mike,

That log looks fine. Your HDD should hopefully be OK. INstead of running DISM for a few days what I think we should do first is repair the current corruptions.

I dont have a lot of free time to track down this update were some of these corruptions are, instead I will get SFCFix to find it for me :)

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. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    Trace::
amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. 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.
 
Okay, Alex, here is the result from the Trace command, which processed instantly. Does it tell you anything? I'm trying to learn myself as we go along here. Thank you.

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2015-01-21 08:42:29.246
Using .txt script file at C:\Users\Dave\Desktop\SFCFixScript.txt [0]




Trace::
Successfully traced component amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04.
    Package_5736_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14.2919355-11934_neutral_GDR5
Trace:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-01-21 08:42:29.777
Script hash: D9LWcYWY+eT4uQi8EiI/2Q5HfnbeFJrOQ8Z5JqTmdPU=
----------------------EOF-----------------------
 
Hi, Alex. I was looking around on Microsoft's support site and I found this article entitled, "Error 0x80073712 when you install update 2919355 in Windows 8.1". Here is the link:

Error 0x80073712 when you install update 2919355 in Windows 8.1 or Windows Server 2012 R2

The article states the following as the "cause" of the error:

"This issue occurs because a new component in update 2919355 contains a file version that is later than the file version that was already installed on the computer."

It sounds like MS is admitting this bug belongs to them. Please let me know what you think. Thanks.

Mike
 
The trace done by SFCFix, tells me what I was expecting. I did think that this file was from the 8.1 upgrade, but I wanted to confirm first.

Code: 
Successfully traced component [COLOR="#FF0000"]amd64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.17031_none_028068154b539e04[/COLOR].
    Package_5736_for_[COLOR="#008080"]KB2919355[/COLOR]~31bf3856ad364e35~amd64~~6.3.1.14.2919355-11934_neutral_GDR5
Trace:: directive completed successfully.

SFCfix can do a scan of any Component and source which update the file originated from, well most Components can be resolved using this method. Any questions or if you would like me to be more specific let me know :)

Is this machine an RT device?

That article is interesting, I will have to compare their findings with mine.

ALex
 
Hi, Alex. I successfully removed the whole package for update KB2919355 with this command:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

(I had first tried removing the package "Package_5736_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14.2919355-11934_neutral_GDR5", but it failed with error number 8007007a).

Then I ran the standalone update for KB2919355. After two reboots, Windows Update is showing that KB2919355 was installed successfully, but at the same time it is telling me that four important updates are available, one of which is KB2919355. I am hesitant to let Windows Update attempt to install this again. Should I just uncheck the box and continue with the other updates?

I had considered removing the package early on, but I thought I'd better ask someone with more knowledge before I did that. In any case, thank you very much for your diligence and persistence in resolving this issue.

Mike
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top