Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Window 7 Update Error - Code 800B0100 and 80073712

26 Nov 2014   #1
ConBe

Windows 7 Home Premium x64
 
 
Window 7 Update Error - Code 800B0100 and 80073712

Hi,

for around about one month, I have some problems using the Windows Update. I always get the error massages 800B0100, 80073712 and sometimes one or two more - fortunately (or unfortunately) not this time.

I already did the steps from the windows update posting instruction threat. The SURT I already used before without success, the SFC Scan showed "Windows Resource Protection did not find any integrity violations".

I hope I did everything correctly, but I'm not sure about that because my CBS.log is almost 50MB. So I couldn't attach the file but set a dropbox link for it. Hope it's ok:

https://www.dropbox.com/s/2upikylljl83z9o/CBS.zip?dl=0

Thanks a lot for the help.
My System SpecsSystem Spec
.
26 Nov 2014   #2
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

CheckSUR shows the following problems
Code:
Summary:
Seconds executed: 886
 Found 74 errors
  CSI Manifest All Zeros Total count: 26
  CBS MUM Corrupt Total count: 24
  CBS Catalog Corrupt Total count: 24
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22807_de-de_0fd22e029ab0c916.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22807_de-de_3c745e60d76fb970.manifest
 winsxs\manifests\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22807_de-de_1a8be0f9e0a91b7c.manifest
 winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22807_none_607d1a1668f10b7b.manifest
 winsxs\manifests\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18540_none_8d8fa85f1e8abeea.manifest
 winsxs\manifests\x86_microsoft-windows-t..nalservices-runtime_31bf3856ad364e35_6.1.7601.22750_none_df41a0614384c000.manifest
 winsxs\manifests\x86_microsoft-windows-t..nalservices-runtime_31bf3856ad364e35_6.1.7601.18540_none_dec2d19c2a5f071e.manifest
 winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18540_none_21b9af2ab84b972a.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18540_none_c59b13a6ffee25f4.manifest
 winsxs\manifests\x86_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_de-de_cd8fc0f5dd9e738d.manifest
 winsxs\manifests\x86_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.22750_de-de_ce0e8fbaf6c42c6f.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22750_none_c619e26c1913ded6.manifest
 winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22807_none_bc9bb59a214e7cb1.manifest
 winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22807_none_998aab1fac6781d7.manifest
 winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22750_none_22387defd171500c.manifest
 winsxs\manifests\amd64_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.22792_none_cabc39528023cdfa.manifest
 winsxs\manifests\x86_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.22792_none_6e9d9dcec7c65cc4.manifest
 winsxs\manifests\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.1.7601.18540_none_31d0e9f4240657a0.manifest
 winsxs\manifests\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.1.7601.22750_none_324fb8b93d2c1082.manifest
 winsxs\manifests\amd64_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.18584_none_ca3f6b2166fc47c6.manifest
 winsxs\manifests\x86_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.18584_none_6e20cf9dae9ed690.manifest
 winsxs\manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22807_none_363b15846c59f634.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22807_none_0507eaca8c7da644.manifest
 winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22807_none_25ffda56a81fe2ca.manifest
 winsxs\manifests\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.22750_none_8e0e772437b077cc.manifest
 winsxs\manifests\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_6.1.7601.18540_de-de_ccb3bd4ff5fe68e4.manifest
 servicing\packages\Package_121_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_121_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_122_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_122_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_123_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_123_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_124_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_124_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_125_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_125_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_126_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_126_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_128_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_128_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_129_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_129_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_130_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_130_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_131_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_131_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_132_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_132_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_133_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_133_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_210_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_210_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_2_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_49_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_49_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_50_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_50_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_51_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_51_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_53_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_53_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_60_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_60_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_87_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_87_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_for_KB2977292_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977292~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2984972_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_for_KB2984972_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
 servicing\packages\Package_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
I'll post a fix when I can - it may not be until tomorrow sometime.
My System SpecsSystem Spec
26 Nov 2014   #3
ConBe

Windows 7 Home Premium x64
 
 

Thanks a lot, but no rush, I have the probs for already one month - what's a day more or less then :)
My System SpecsSystem Spec
.

26 Nov 2014   #4
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

I've uploaded a file - cbeaa.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 cbeaa 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.
My System SpecsSystem Spec
27 Nov 2014   #5
ConBe

Windows 7 Home Premium x64
 
 

Oh wow, thanks a lot - that was a fast response. I did everything as described and the log files are way smaller now, hope thats a good sign :) Though I didn't try the update yet again. Shall I?

CheckSUR Log files 11272014.zip


My System SpecsSystem Spec
27 Nov 2014   #6
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

All fixed
Code:
Summary:
Seconds executed: 370
 Found 50 errors
 Fixed 50 errors
  CSI Manifest All Zeros Total count: 26
  Fixed: CSI Manifest All Zeros.  Total count: 26
  CBS MUM Corrupt Total count: 24
  Fixed: CBS MUM Corrupt.  Total count: 24
  Fixed: CBS Paired File.  Total count: 24
Please run another SFC /SCANNOW and post the new CBS.log file
If the SFC scan return 'no errors found', then try Windows Updates again...

Do a Check for Updates, then attempt to install ONLY the oldest update found.
What happens?
If it installs OK, try the rest.
If not, post the C:\Windows\windowsupdate.log file
My System SpecsSystem Spec
27 Nov 2014   #7
ConBe

Windows 7 Home Premium x64
 
 

Amazing! I have no idea what you did or how I could thank you for it, but its all working. No errors after the sfc scan and all updates worked afterwards. Thank you so much! Really appreciate your help :)

Attached the CBS file - again as dropbox link, cause its way to big for uploading it here.

https://www.dropbox.com/s/gwp7qjhmrb5kjye/CBS.zip?dl=0
My System SpecsSystem Spec
.
27 Nov 2014   #8
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

The SFC result is clean, as expected - but there are a couple of minor errors in the background data, which may (but only may!) cause problems later. I think they can be ignored for the moment at least
feel free to come back and moan if you get more update problems at a later date!
My System SpecsSystem Spec
28 Nov 2014   #9
ConBe

Windows 7 Home Premium x64
 
 

OK, cool. Thanks again 1000 times. I'll mark the thread then :)
My System SpecsSystem Spec
28 Nov 2014   #10
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Good luck!
My System SpecsSystem Spec
Reply

Thread Tools




Similar help and support threads
Thread Forum
Update Error Code 800B0100 and 80073712
Hi, I can't install 11 updates on my computer because those errors keep coming up. I have tried the SURT but nothing changed. Here is my CBS files. Please Help. Thank you
Windows Updates & Activation
Frequent BSOD, Update error 800B0100 & 80073712
Hi. I would greatly appreciate the help with resolving this update issue, which I think may be related to the BSODs I keep getting. Here's the CBS file. https://dl.dropboxusercontent.com/u/324863/CBS.zip Thanks! - Ben
Windows Updates & Activation
Win7 home 64bits, Update crash error code 800B0100, 80073712, 8024200D
Hello, For few week, i can't update my windows 7, each try : crash error code 800B0100, 80073712, 8024200D. At each shut down i have 2 very fast update. It's weird :huh: I did try : - install System Update Readiness Tool - Sfcscann: 100% verification Windows Resource Protection did not...
Windows Updates & Activation
Update error codes 800B0100 and 80073712... Tried EVERYTHING, HELP!
Ok so I have been trying to fix these error codes 80073712 and 800B0100 for days and days on end now... I have tried pretty much everything I can think of and everything that I have read on numerous different forums and nothing at all seems to work for me... I have deleted all anti virus...
Windows Updates & Activation


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:52.
Twitter Facebook