Solved Errors 80073212 & 800F0900 when updating windows windows 7

[tarasdi]

Hi all,

I'm getting the referenced errors when trying to update windows. My machine BSOD before I started noticing this error (not sure if I had this issue before the BSOD). I have tried a number of things:

* Removing and redownloading the files
* Doing a clean reboot and:
** Running SFC with /scannow (as administrator) - no errors found
** Running fix it with all programs shut down - no errors found
** Trying to run the critical updates one by one. Each one gives one of the referenced errors
** Running the SUR exe

The SUR tool says "Installing Hotfix for Windows (KB8947821) (update 1 of 1).." and then seems to stall (?!). I have attached the last few lines of Windows Update Log.

I have also attached the last few lines of the Windows Update Log when trying to install all updates through the "Windows Update" tool. The "update history" and "list of updates" are attached as images. When running Windows Update, the screen stays on "downloading updates" for a few minutes, then creates a system restore point, then looks like it installs a hotfix (windows_update.png), then shows the failure screen.

The only error that I can see in the event viewer is something to do with VSS failing.

Not sure what to try next?

Thanks

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[tarasdi]

Hi,

I've zipped the contents & split into parts of 5MB each (I've had to append .zip onto the filenames for the zip parts) - let me know if this won't work.

Thanks!

Taras

 

[NoelDP]

You have some major problems in the CheckSUR report...

Seconds executed: 1703
 Found 230 errors
  CSI Manifest All Zeros Total count: 216
  CBS MUM Corrupt Total count: 14

You appear to have run the tool a number of times - and it did not complete, for whatever reason, the last two times?

However, your SFC scan is surprisingly clear, although the background CBS logs are full of errors relating to the CheckSUR data.

I'll give it a go at fixing this - it'll take a while for me to get the files together, so it may not be until tomorrow or Tuesday even.
If you need a quicker solution, then a repair install is the way to go (and we may end up having to go that way anyhow, if fixing the known corruptions doesn't work) Look here for details... http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[NoelDP]

Wasn't as difficult as I thought it may be!

I've uploaded a file - tsdaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder tsdaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[tarasdi]

Nice.

I've transferred the files across and am re-running check sur now.

Previous runs of checksur didn't complete because I forcibly killed it (it looked like it had stalled!). I'll let this one run out and post up the results.

Thanks

Taras

 

[tarasdi]

CheckSUR ran until completion that time - I've attached the logs from this run.

Cheers!

Taras

 

[NoelDP]

That brings the error-level down to much more manageable proportions...

Unavailable repair files:
 servicing\packages\Package_25_for_KB2966583~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2962872_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2962872~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2966583~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2973201_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2973201~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_25_for_KB2966583~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2962872_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2962872~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2966583~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2973201_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2973201~31bf3856ad364e35~amd64~~6.1.1.2.cat

Summary:
Seconds executed: 930
Found 230 errors
Fixed 224 errors
CSI Manifest All Zeros Total count: 216
Fixed: CSI Manifest All Zeros. Total count: 216
CBS MUM Corrupt Total count: 14
Fixed: CBS MUM Corrupt. Total count: 8
Fixed: CBS Paired File. Total count: 8

Now I have to work out why the other failed!

 

[tarasdi]

Nice work

 

[NoelDP]

- it looks like I simply picked the wrong run of CheckSUR to get the filenames from...

I'll post a second fix for them in a few minutes

 

[NoelDP]

I've uploaded a file - tsdab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder tsdab in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[tarasdi]

Hey Noel,

I downloaded the file but it only had a packages directory inside...?

 

[NoelDP]

That's OK - I forgot to amend the boilerplate to omit the Manifest instructions.
Continue without a problem.

 

[tarasdi]

Thanks - attached!

 

[NoelDP]

Great - CheckSUR is now happy.

Do a new Check for Updates - then try and install ONLY the oldest one found - what happens?
If it fails, post the new CBS.log, and the C:\Windows\windowsupdate.log file together with the exact error message.

If it installs OK, try the rest

 

[tarasdi]

Hi,

Finally some progress. I did the following:

* installed the oldest update - this worked
* installed remaining updates - reported 4 failed
* retried installing failed updates - all failed
* installed the oldest failed update - this failed
* installed the second oldest update - this failed

I've attached:

* CBS logs
* screenshots showing the failed updates

It seems to be stuck on the KB296xx update...

 

[NoelDP]

The 0x800736cc error implies corruption somewhere - possibly caused by hard drive problems.

Let's try the easy/quick fix first...



Open an Elevated Command Prompt
Run the following commands

NET STOP WUAUSERV
REN C:\WINDOWS\SoftwareDistribution SDOLD
NET START WUAUSERV

reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.
If the installs still fail - what error message do you get?

 

[tarasdi]

Hi Noel,

Another step closer:

* ran your above steps, ran update, 2 were installed, 2 failed (first screenshot)
* rebooted, re-ran update, 2 failed (second screenshot)

 

[NoelDP]

Those should install from the standalone updates.
Check the KB numbers of these updates, then Google
KBnumber x64 download

that should put the link to the download close to the top of the list - download it and run it reboot and download and run the other.