Windows updates fail, error 800B0100

[alexander2013]

Hi, i need some help. recently i have been getting problems with my computer.
The first problem is that the windowsfeatures.exe is blank and i cannot install all my windows updates.
I have tried numerous things including disabling and shutting down my anti virus etc but to no avail.
I will post the CBS log below that i got from Windows6.1-KB947821-v31-x64.msu.


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2013-12-13 14:30

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16748_none_07ebd26bfd1a9d00.manifest amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16748_none_07ebd26bfd1a9d00
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20888_none_084a2f871658ac8e.manifest amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20888_none_084a2f871658ac8e

Summary:
Seconds executed: 146
Found 12 errors
CSI Manifest All Zeros Total count: 2
CBS MUM Corrupt Total count: 5
CBS Catalog Corrupt Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16748_none_07ebd26bfd1a9d00.manifest
winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20888_none_084a2f871658ac8e.manifest
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat

 

[indianacarnie]

Welcome to the forums!

Have you tried running windows update troubleshooter? We have many excellent tutorials here on the forums, here's how to access troubleshooting, just click on the link, choose "fix problems with windows update". Hope this helps

http://www.sevenforums.com/tutorials/472-troubleshooting.html

http://www.sevenforums.com/tutorials/69152-windows-update-troubleshoot-shortcut-create.html

 

[TanyaC]

In addition to indianacarnie suggestion, you might also like to try the Windows System Update Readiness tool.

I had this problem several times in the early days. Error 800B0100 relates to the Windows updates files. Something is missing or corrupt.If the System Readiness Tool encounters problems it logs them in a file called checksur.log, which you will find in the Windows folder, under c:\windows\logs\cbs

To download the SRT, follow this link..
What is the System Update Readiness Tool?

 

[NoelDP]

Tanya - the CheckSUR log he posted IS the SURT output.

I'll post a fix protocol for the errors in a few minutes.

 

[NoelDP]

I've uploaded a file - a23aa.zip - to my SkyDrive at Noel's SkyDrive
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 a23aa 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.

 

[TanyaC]

Tanya - the CheckSUR log he posted IS the SURT output.

Sorry, I'll stop stepping in where I don't belong..

 

[NoelDP]

Not a problem, Tanya - that probably came across a lot stronger than it was intended.
All assistance gratefully received at this end!