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: update kb2973112 installation error 800B0100

13 May 2015   #1
cornishlad

windows 7 home premium 64bit
 
 
update kb2973112 installation error 800B0100

I am getting error 800B0100 when running the install for security update kb2973112
(from the normal system update function)

This is on a windows 7 home premium 64 bit laptop

I have tried downloading the update directly via IE from MS
In this case when I run it it says "the following updates were not installed"
(2973112 that is)

I have run sfc /scannow
(it said it found corrupt files but was unable to fix them)

and the System Update Readiness Tool (SURT)

I think I have correctly attached the CBS directory files to this post...

Thanks for any help....


My System SpecsSystem Spec
.
13 May 2015   #2
sml156

Microsoft Windows 7 Ultimate 32-bit 7601
 
 

I did a google search on your error message (error 800B0100 "kb2973112") and found this link on the microsoft website
Quote:
Windows Update error 800B0100
Windows 7 More
If you receive Windows Update error 800B0100, it means that a file needed by Windows Update is corrupted or missing.

The System Update Readiness Tool can help fix problems that might prevent Windows updates from installing. Windows Update error 800B0100 is one of the problems that the tool can check for and repair. To learn how to use this tool, go to What is the System Update Readiness Tool? on the Windows website.

Note

Typically, the scan will take 15 minutes or less, but it can take longer on some computers. The Windows Update progress bar isn't updated during the scan, and progress seems to stop at 60% complete for some time. This behavior is expected. The scan is still running, and you shouldn't cancel the update.

If the System Update Readiness Tool encounters problems while running, it records them in a file called CheckSUR.log, which is located in your Windows folder, under Logs\CBS\. On a default installation of Windows this will be C:\Windows\Logs\CBS.

If you continue to see this error, see this automatic troubleshooter on the Microsoft Support website, or go to the Microsoft Answers website for more assistance.

Error codes this applies to:

WindowsUpdate_800B0100

0x800B0100

WindowsUpdate_dt000
I hope that help's

Windows Update error 800B0100 - Windows Help
My System SpecsSystem Spec
13 May 2015   #3
cornishlad

windows 7 home premium 64bit
 
 

Thanks very much for your help...

Both the system update tool and the sfc /scannow report a whole bunch of corrupt files (around 50 ish)

However I've no idea how to replace/repair them...

I can find things that look similar in the windows install disc install.wim
however the version numbers are different so I don't think they will do

for example one of the corrupt files is:-

winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.22743_none_046c22977b74e62c.manifest

and if I locate this in the windows install image (install.wim on the dvd)
the "6.1.7601" number bit in the file is different,
which I take to mean the install has an earlier version of the file,
and I'm guessing that some other update (SP1?) installed/corrupted a later version...

I have attached a text file of the corrupt manifests
(I think the CBS log files indicate some other things than manifests are also corruption)

Thanks....


Attached Files
File Type: txt error.txt (6.1 KB, 1 views)
My System SpecsSystem Spec
.

14 May 2015   #4
NoelDP

Microsoft Community Contributor Award Recipient

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

Here's the full error list from the CheckSUR log - I'll post a fix protocol later...
Code:
Summary:
Seconds executed: 517
 Found 68 errors
  CSI Manifest All Zeros Total count: 56
  CBS MUM Corrupt Total count: 6
  CBS Catalog Corrupt Total count: 6
Unavailable repair files:
 winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.22743_none_046c22977b74e62c.manifest
 winsxs\manifests\msil_smsvchost_b03f5f7f11d50a3a_6.1.7601.22743_none_cfeb95652ab9a380.manifest
 winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.18532_none_f5ef1e68c06b0983.manifest
 winsxs\manifests\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.22743_none_a84d8713c31774f6.manifest
 winsxs\manifests\msil_system.runtime.serialization.ref_b77a5c561934e089_6.1.7601.18532_none_a681522274d87bdf.manifest
 winsxs\manifests\x86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.18532_none_db9f3389dd561754.manifest
 winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.22743_none_424e32868e888704.manifest
 winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.22743_none_df226106da119cd2.manifest
 winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.22743_none_7d253f50e280819d.manifest
 winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.18532_none_03ec5388625013f3.manifest
 winsxs\manifests\msil_system.servicemodel.ref_b77a5c561934e089_6.1.7601.22743_none_29f7a0b6e8fbe8a4.manifest
 winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.18532_none_b259b569e8a367e7.manifest
 winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.18532_none_c7c878850b1cbe6b.manifest
 winsxs\manifests\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7601.22743_en-us_787c558fd9767a5a.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel.ref_b03f5f7f11d50a3a_6.1.7601.22743_none_5ec02bad339e1184.manifest
 winsxs\manifests\msil_smdiagnostics_b77a5c561934e089_6.1.7601.18532_none_72f0e00b6ca38779.manifest
 winsxs\manifests\msil_system.identitymodel_b77a5c561934e089_6.1.7601.22743_none_daec3d651a56707a.manifest
 winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.18532_none_591aefe874e1f3b5.manifest
 winsxs\manifests\msil_system.runtime.serialization_b77a5c561934e089_6.1.7601.22743_none_bff7ca5ab6261061.manifest
 winsxs\manifests\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.18532_none_a7cdb804a9f2a2bd.manifest
 winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.18532_none_93f1fcb2c8d9ee4e.manifest
 winsxs\manifests\msil_system.servicemodel_b77a5c561934e089_6.1.7601.22743_none_627c1e8360ed619d.manifest
 winsxs\manifests\x86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.22743_none_c4d27627f6fcaaa3.manifest
 winsxs\manifests\msil_system.servicemodel_b77a5c561934e089_6.1.7601.18532_none_7948dbe54746ce4e.manifest
 winsxs\manifests\msil_smsvchost_b03f5f7f11d50a3a_6.1.7601.18532_none_e6b852c711131031.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel.washosting_b03f5f7f11d50a3a_6.1.7601.22743_none_eb769f0f609f0962.manifest
 winsxs\manifests\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.18532_none_c6617fc7de79418f.manifest
 winsxs\manifests\msil_smdiagnostics_b77a5c561934e089_6.1.7601.22743_none_5c2422a9864a1ac8.manifest
 winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.22743_none_b0fbbb2324c351ba.manifest
 winsxs\manifests\msil_system.servicemodel.resources_b77a5c561934e089_6.1.7601.18532_en-us_2619090fb6acdd9f.manifest
 winsxs\manifests\msil_system.servicemodel.washosting_b77a5c561934e089_6.1.7601.18532_none_926d9ec39dfff67f.manifest
 winsxs\manifests\msil_smsvchost.resources_b03f5f7f11d50a3a_6.1.7601.22743_en-us_b2b37b6fe3787c73.manifest
 winsxs\manifests\msil_system.runtime.serialization_b77a5c561934e089_6.1.7601.18532_none_d6c487bc9c7f7d12.manifest
 winsxs\manifests\x86_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.22743_none_d28a8613c1bc6855.manifest
 winsxs\manifests\x86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.22743_none_e33a2edf16c6243c.manifest
 winsxs\manifests\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7601.18532_en-us_8f4912f1bfcfe70b.manifest
 winsxs\manifests\msil_smdiagnostics.resources_b77a5c561934e089_6.1.7601.22743_en-us_3299804758c3fbf7.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel.washosting_b03f5f7f11d50a3a_6.1.7601.18532_none_02435c7146f87613.manifest
 winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.22743_none_22ffea5aaffb84fe.manifest
 winsxs\manifests\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.22743_none_c6e14ed6f79e13c8.manifest
 winsxs\manifests\msil_system.identitymodel.resources_b77a5c561934e089_6.1.7601.22743_en-us_c1692126028e525f.manifest
 winsxs\manifests\msil_system.identitymodel.resources_b77a5c561934e089_6.1.7601.18532_en-us_d835de87e8e7bf10.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.22743_none_8add4f3cad403f4f.manifest
 winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.18532_none_22801b4b96d6b2c5.manifest
 winsxs\manifests\msil_system.identitymodel_b77a5c561934e089_6.1.7601.18532_none_f1b8fac700afdd2b.manifest
 winsxs\manifests\msil_system.servicemodel.resources_b77a5c561934e089_6.1.7601.22743_en-us_0f4c4badd05370ee.manifest
 winsxs\manifests\x86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.18532_none_fa06ec40fd1f90ed.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.18532_none_a1aa0c9e9399ac00.manifest
 winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.22743_none_9b8cf8080249fb36.manifest
 winsxs\manifests\msil_smdiagnostics.resources_b77a5c561934e089_6.1.7601.18532_en-us_49663da93f1d68a8.manifest
 winsxs\manifests\msil_smsvchost.resources_b03f5f7f11d50a3a_6.1.7601.18532_en-us_c98038d1c9d1e924.manifest
 winsxs\manifests\msil_system.runtime.serialization.ref_b77a5c561934e089_6.1.7601.22743_none_8fb494c08e7f0f2e.manifest
 winsxs\manifests\amd64_wcf-system.servicemodel.ref_b03f5f7f11d50a3a_6.1.7601.18532_none_758ce90f19f77e35.manifest
 winsxs\manifests\msil_system.servicemodel.ref_b77a5c561934e089_6.1.7601.18532_none_40c45e18cf555555.manifest
 winsxs\manifests\x86_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.18532_none_e9574375a815d506.manifest
 winsxs\manifests\msil_system.servicemodel.washosting_b77a5c561934e089_6.1.7601.22743_none_7ba0e161b7a689ce.manifest
 servicing\packages\Package_25_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_25_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_26_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_26_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_27_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_27_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2973112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2973112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2973112~31bf3856ad364e35~amd64~~6.1.1.0.mum
My System SpecsSystem Spec
15 May 2015   #5
NoelDP

Microsoft Community Contributor Award Recipient

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

I've uploaded a file - csdaa.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 csdaa 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
15 May 2015   #6
cornishlad

windows 7 home premium 64bit
 
 

Thank you very, very much for your help.

I have copied the fix and run the CheckSur tool again
(I also ran scannow /fix)

I am attaching the CheckSur and CheckSur.persist log files
(as well as CBS.log)

Thanks again for your help
My System SpecsSystem Spec
16 May 2015   #7
NoelDP

Microsoft Community Contributor Award Recipient

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

Drat! missed one
Code:
 Fixed 61 errors
  CSI Manifest All Zeros Total count: 56
  Fixed: CSI Manifest All Zeros.  Total count: 55
  CBS MUM Corrupt Total count: 6
  Fixed: CBS MUM Corrupt.  Total count: 6
  Fixed: CBS Paired File.  Total count: 6
 
Unavailable repair files:
 winsxs\manifests\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.18532_none_a7cdb804a9f2a2bd.manifest
Back later with another fix.
My System SpecsSystem Spec
16 May 2015   #8
NoelDP

Microsoft Community Contributor Award Recipient

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

I've uploaded a file - csdab.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 csdab 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
16 May 2015   #9
cornishlad

windows 7 home premium 64bit
 
 

Thanks again for the fix...

I have run the tools and attached the log to this post...
This seems to have fixed the problem, in as much as the update (kb2973112) that failed before installed properly...

Is there any way of sending you a beer voucher by way of thanks for all your efforts?
My System SpecsSystem Spec
16 May 2015   #10
NoelDP

Microsoft Community Contributor Award Recipient

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

CheckSUR is happy as well.... If you happen around the Chester area, you can buy me a drink in person!
My System SpecsSystem Spec
Reply

 update kb2973112 installation error 800B0100




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
update error 800b0100 for updates kb2943357 kb2973112
Win 7 Pro, 64-bit, Dell Latitude 6430, I5 Can't run the updates listed in the subject line. All other updates are fine. Tried running updates one at a time - no good. Tried sfc scannow with no results Reset windows update components - no good Ran the System Update Readiness Tool - didn't...
Windows Updates & Activation
Windows 7 Update kb2943357 & kb2973112 Fails with error 800B0100
Hello Noel, I've the same problem too and found this post. Can you help me too? Find attached the logs. Thx Michael
Windows Updates & Activation
Windows 7 Update kb2943357 & kb2973112 Fails with error 800B0100
Im bringing a clean install of Win7Prox64 up to speed with updates and getting the same problem as these users Windows 7 Update kb2943357 & kb2973112 Fails with error 800B0100 error code 800B0100 when updating dot net kb2943357 Basically, cant get kb2943357 & kb2973112 to install. Ive...
Windows Updates & Activation
Win 7 Home Prem. 64 bit, Code 800B0100, Update KB2943357 & KB2973112
Had to use recovery disks for laptop that crashed. Was able to reinstall all software, files, folders and updates except for the two Security Updates for Microsoft.NET Framework 3.5.1(KB2943357) and (KB2973112). The error code I'm getting is 800B0100. Have already tried troubleshooting, doing a...
Windows Updates & Activation
windows update kb2973112 failed code 800b0100
Windows 7 Pro. i7 4790. MSI Gaming 7 board. Corsair SSD for booting Win7. Tried update. Tried SURT. Ran SFC scan with no errors. Crazy frustrated. Wondering if it has to do with the new fandangled msi boot stuff. Even went as far as to DL AVG tune up to see about repairing reg keys, that didn't...
Windows Updates & Activation
Windows 7 Update kb2943357 & kb2973112 Fails with error 800B0100
OS: Windows 7 Professional 64 bit SP1 http://www.sevenforums.com/windows-updates-activation/351563-error-code-800b0100-when-updating-dot-net-kb2943357.html I have faced exactly same error code 800B0100 when installing updates for exactly same packages kb2943357 & kb2973112. I have also run...
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 23:49.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App