Solved Windows Update Failures: Code 80070BC9 and 9C57

[nfullington]

Hi,

I am trying to update my Dell T1650 with some Windows Updates using Windows Update. 2 updates keep failing: KB971033 and IE 10 for Windows 7 x64 base system. I have tried Microsoft Fix It and other potential problem solving scenarios and when my PC reboots the fixes try to install but fail and the reverts back to its previous state. I have run sfc/scannow and no errors popup. I have also run SURT and even though the PC reboots I still run into the same failures. When the updates fail I get Code 80070BC9 and Code 9C57. I have attached the output from the CheckSur log but it shows there are corruptions in two KB packages: KB2522422 and KB2778344. This is a new PC and I am hoping these issues will resolve the issues I have installing iTunes 11 on it. Thank you for your help!

 

[tom982]

Hello nfullington and welcome to the forums

Your CheckSUR log is showing a few corrupt files which we will need to fix:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-11 15:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 98
 Found 16 errors
  CBS MUM Corrupt Total count: 8
  CBS Catalog Corrupt Total count: 8

Unavailable repair files:
    servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat

Windows Update Package Replacement

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. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link. It must be downloaded using Internet Explorer.

Download Security Update for Windows 7 for x64-based Systems (KB2778344) from Official Microsoft Download Centre
Download Update for Windows 7 for x64-based Systems (KB2522422) from Official Microsoft Download Center

Tom

 

[nfullington]

Thank you for your response! I did what you posted above and attached is the output from CheckSUR. It looks like the corrupted files are fixed. I did not get the error you said I may get. I ran Windows Update and the updates still failed citing codes: 8007054F and 9C57. Also, every time I reboot the PC it says I need to install some updates. When they try to install they end up failing and it reverts back to before the attempted installation. So I ran CheckSUR one more time to see what the deal was and the issues were fixed. However, I wonder if CheckSUR is trying to fix some other issues and it can't which is why I get the failed installations.

 

[tom982]

Hi nfullington,

We've done all we can with the System Update Readiness Tool and a CheckSUR log so now it's time to change tack slightly. Can you zip up and attach your CBS log to your next post please? It contains a lot more detail and should shed some light on your problem:

C:\Windows\Logs\CBS\CBS.log

Tom

 

[nfullington]

When I try to zip it, it says File not found or no read permission. Also, when I try to open the document in notepad it says access denied. According to my profile I am the administrator for the computer so it is strange that I wouldn't have permission.

 

[tom982]

Hi nfullington,

Sorry for the confusion, you posted your CBS log in your first post but I missed it the first time round. It's getting late here now so I'll take a good look in the morning, I've had a quick glance and it doesn't look very nice at all!

Tom

P.S. For future reference, if we ever need to get the CBS log, copy it to your Desktop first. This will bypass the permissions in place

 

[nfullington]

No problem. Have a great night! I have attached the latest CBS log file in this post. I really appreciate all the help!

 

[nfullington]

Just to let you know, I was able to get my hands on the recovery discs that came with machine including the Operating System disc. Don't know if it helps but it may make things easier.

 

[nfullington]

So I went ahead and used the O/S cd to do a Windows 7 "upgrade" and it appears to have fixed the issues. I was able to install all of the updates so far including the two I couldn't before. I was even able to successfully install iTunes. I really appreciate all your help and will definitely come back to use this forum if I run into anymore trouble. Thank you again for all your help!

 

[Layback Bear]

I'm glad your fixed nfullington. You do not have to have a problem to come and visit the Forum. Just visit anytime you want to.