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: Unable to update Windows - Error code 800B0100


30 Apr 2013   #1

Windows 7 Professional x64
 
 
Unable to update Windows - Error code 800B0100

Hi,
I'm unable to update my Windows - Windows 7 Pro x64. An Error code 800B0100 always appear during update

- Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645)
- Security Update for Windows 7 for x64-based Systems (KB2808735)
- Security Update for Windows 7 for x64-based Systems (KB2813170)

I tried disable the firewall and antivirus before update, but no use. I also tried download the files and update offline. But also failed.

Please help. Thank you.
Man



Attached Files
File Type: zip CBS.zip (6.31 MB, 3 views)
My System SpecsSystem Spec
.

01 May 2013   #2

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

You have a very large number of file problems.
From the CheckSUR log...
Code:
Unavailable repair files:
 winsxs\manifests\msil_system.windows.forms_b77a5c561934e089_6.1.7601.22191_none_ee82d75519cdb09a.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22210_none_6ebd48cf2b868ae6.manifest
 winsxs\manifests\amd64_netfx-system.design_b03f5f7f11d50a3a_6.1.7601.18027_none_8abae60415960968.manifest
 winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_17b2cef2ca377b92.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_14830bbdb30e2246.manifest
 winsxs\manifests\msil_system.design.resources_b03f5f7f11d50a3a_6.1.7601.22191_en-us_fefabb14d4f18b37.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18044_none_6e173b82127da724.manifest
 winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_214c9927e5a07856.manifest
 winsxs\manifests\msil_system.windows.forms_b77a5c561934e089_6.1.7601.18027_none_0548f35f002d38f9.manifest
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_1f92962d0066a978.manifest
 winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_901677de18a58467.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_d139c7943b60a596.manifest
 winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_fcd1e4cbba5cfc7b.manifest
 winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_6971452eab80a50e.manifest
 winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_0d52a9aaf32333d8.manifest
 winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.22191_none_72e0ff71d9629a76.manifest
 winsxs\manifests\amd64_netfx-system.design_b03f5f7f11d50a3a_6.1.7601.22191_none_73f4c9fa2f368109.manifest
 winsxs\manifests\amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.21417_none_e0ca214560fc4c2b.manifest
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_1ed7b60fe76ee441.manifest
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_c6e51d4206ffe39b.manifest
 winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.22209_none_d31b1c8931ca7785.manifest
 winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_f27d3a7985fc3a80.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_153debdacc05e77d.manifest
 winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_85c1cd8be444c26c.manifest
 winsxs\manifests\amd64_netfx-system.windows.forms_b03f5f7f11d50a3a_6.1.7601.18027_none_837258327b605fd2.manifest
 winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_22077944fe983d8d.manifest
 winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.18027_none_89a71b7bbfc222d5.manifest
 winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_16f7eed5b13fb65b.manifest
 winsxs\manifests\amd64_netfx-system.windows.forms_b03f5f7f11d50a3a_6.1.7601.22191_none_6cac3c289500d773.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18044_none_ca35d705cadb185a.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22210_none_cadbe452e3e3fc1c.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18043_none_d07ee7772268e05f.manifest
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Package_1_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2789645~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_2_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2799494~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_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_9_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_9_for_KB2799494~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_for_KB2789645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2789645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Package_1_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2789645~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_2_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2799494~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_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_9_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_9_for_KB2799494~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
 servicing\packages\Package_for_KB2789645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2789645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0.cat
There is surprisingly little amiss in the SFC results, but there a number of errors related to the above in the remainder of the CBS log.

I'll post a fix protocol for the known errors a bit later - it may take some time to hunt them all down.

With any luck, it should fix the system and allow Windows Update to function again.
My System SpecsSystem Spec
01 May 2013   #3

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I've uploaded a file - i13aa.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 i13aa 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
.


01 May 2013   #4

Windows 7 Professional x64
 
 

Based on your instruction, attached two new log files here.


Attached Files
File Type: log CheckSUR.log (23.0 KB, 3 views)
File Type: log CheckSUR.persist.log (195.5 KB, 2 views)
My System SpecsSystem Spec
01 May 2013   #5

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Great! that's fixed all the repairable bits (the two remaining 'errors' are normal for IE10).

Please run another SFC /SCANNOW and post the CBS.log file.
If it tells you 'no problems found', go to Windows Update, and do a Check for Updates, and see what's found, then try installing them.
My System SpecsSystem Spec
01 May 2013   #6

Windows 7 Professional x64
 
 

THANK YOU, Noel. It's work now. All windows update is successfully installed. Here is the CBS.log file.


Attached Files
File Type: log CBS.log (696.0 KB, 2 views)
My System SpecsSystem Spec
01 May 2013   #7

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Great!
The SFC is clear - and at <3 minutes for a full scan, that's fast, even for SSD!


Enjoy.
My System SpecsSystem Spec
Reply

 Unable to update Windows - Error code 800B0100




Thread Tools



Similar help and support threads for2: Unable to update Windows - Error code 800B0100
Thread Forum
Solved Windows update error code 800b0100 Windows Updates & Activation
Windows Update SP1 error code 800B0100 Windows Updates & Activation
Windows Update Error Code 800B0100 Windows Updates & Activation
Windows won't update to SP1, error Code 800B0100 Windows Updates & Activation
Solved Windows Update Error Code 800B0100 Windows Updates & Activation
Windows Update: Error Code 800B0100 Windows Updates & Activation
Windows Update: Error Code 800B0100 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 02:43 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33