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: Windows Update Errors 800B0100 & 8024200D


01 Jan 2014   #1

Windows 7 HP 64 bit
 
 
Windows Update Errors 800B0100 & 8024200D

Happy New Year!

I have been experiencing some annoying errors with Windows Update in which 8 important updates will not install.

-I have tried using the System Update Readiness Tool about 3 times with no success.

-I have tried manually installing the updates from Microsoft Download Center with no success.

These are the updates in question:

Security Update for Windows 7 for x64-based Systems (KB2676562)
Security Update for Windows 7 for x64-based Systems (KB2690533)
Security Update for Windows 7 for x64-based Systems (KB2743555)
Security Update for Windows 7 for x64-based Systems (KB2758857)
Security Update for Windows 7 for x64-based Systems (KB2872339)

Update for Windows 7 for x64-based Systems (KB2699779)
Update for Windows 7 for x64-based Systems (KB2726535)
Update for Windows 7 for x64-based Systems (KB2882822)

The error codes are 800B0100 & 8024200D

Thanks in advance for your time and help!

My System SpecsSystem Spec
.

01 Jan 2014   #2

Windows 7 HP 64 bit
 
 

Here is the CheckSUR log file


Attached Files
File Type: log CheckSUR.log (16.0 KB, 2 views)
My System SpecsSystem Spec
02 Jan 2014   #3

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I've seen worse
Here's the file error list...
Code:
Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22436_none_1f6f29570081ab94.manifest
 winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22436_none_8ff30b0818c08683.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22436_none_d1165abe3b7ba7b2.manifest
 winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22436_none_fcae77f5ba77fe97.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18247_none_d082ec6b22654009.manifest
 winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22436_none_694dd858ab9ba72a.manifest
 winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22436_none_0d2f3cd4f33e35f4.manifest
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18247_none_c62e4218ee047e0e.manifest
 winsxs\manifests\wow64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22436_none_c03ca3001653c1ef.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22436_none_6eadae7f2b915520.manifest
 winsxs\manifests\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22436_none_b5e7f8ade1f2fff4.manifest
 winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18247_none_b6df585112e2f85b.manifest
 winsxs\manifests\amd64_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.18247_none_4150cbb99d3704f5.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18247_none_ca38dbafcad85ead.manifest
 winsxs\manifests\amd64_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.18247_none_5a6b4a71e8e39408.manifest
 winsxs\manifests\x86_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.18247_none_fe4caeee308622d2.manifest
 winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18247_none_c13402a34743ba56.manifest
 winsxs\manifests\x86_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.18247_none_e5323035e4d993bf.manifest
 winsxs\manifests\wow64_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22436_none_3277c9ba098a17b2.manifest
 winsxs\manifests\x86_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.22436_none_fee01d41499c8a7b.manifest
 winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.22436_none_c1c770f6605a21ff.manifest
 winsxs\manifests\x86_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.22436_none_e5c59e88fdeffb68.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18247_none_6e1a402c127aed77.manifest
 winsxs\manifests\amd64_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.22436_none_5afeb8c501f9fbb1.manifest
 winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.22436_none_b772c6a42bf96004.manifest
 winsxs\manifests\amd64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22436_none_0ad6905f48fd53a8.manifest
 winsxs\manifests\wow64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22436_none_152b3ab17d5e15a3.manifest
 winsxs\manifests\amd64_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.22436_none_41e43a0cb64d6c9e.manifest
 winsxs\manifests\amd64_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22436_none_28231f67d52955b7.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22436_none_cacc4a02e3eec656.manifest
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22436_none_c6c1b06c071ae5b7.manifest
 winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.22436_none_d2f7afb331e579a1.manifest
 winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22436_none_f259cda386173c9c.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22436_none_151a7f04cc20e999.manifest
 winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22436_none_859e60b5e45fc488.manifest
 servicing\packages\Package_2_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_2_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_3_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_3_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_4_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_4_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_5_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_5_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2882822_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2882822_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_2_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_2_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_3_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_3_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_4_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_4_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_5_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_5_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2882822_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2882822_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2882822~31bf3856ad364e35~amd64~~6.1.1.2.cat
I'll post a fix protocol a bit later.
My System SpecsSystem Spec
.


02 Jan 2014   #4

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I've uploaded a file - cgnaa.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 cgnaa 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
02 Jan 2014   #5

Windows 7 HP 64 bit
 
 

Here is the CheckSUR & CheckSUR.persist logs, thanks again!


Attached Files
File Type: log CheckSUR.log (19.0 KB, 1 views)
File Type: log CheckSUR.persist.log (130.8 KB, 0 views)
My System SpecsSystem Spec
02 Jan 2014   #6

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

So far, so good - CheckSUR is now clear.

Please run an SFC scan and post the results....


SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your reply so that I can take a look.
My System SpecsSystem Spec
02 Jan 2014   #7

Windows 7 HP 64 bit
 
 

Ran the SFC scan, "Windows Resource Protection did not find any integrity violations."

Attached CBS log to reply.

Now there are only 4 important updates that have failed!

Error code: 8024200D

Security Update for Windows 7 for x64-based Systems (KB2690533)

Security Update for Windows 7 for x64-based Systems (KB2743555)

Update for Windows 7 for x64-based Systems (KB2699779)

Update for Windows 7 for x64-based Systems (KB2726535)


Attached Files
File Type: zip CBS.zip (7.04 MB, 2 views)
My System SpecsSystem Spec
02 Jan 2014   #8

Windows 7 HP 64 bit
 
 

And here is the CheckSUR and CheckSUR.persist after running again


Attached Files
File Type: log CheckSUR.log (393 Bytes, 2 views)
File Type: log CheckSUR.persist.log (131.2 KB, 0 views)
My System SpecsSystem Spec
03 Jan 2014   #9

Windows 7 Pro - 64 bit
 
 

try and do an full shutdown of the computer , not a restart . then try windows update again .. This usually works for me ..
My System SpecsSystem Spec
03 Jan 2014   #10

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

My System SpecsSystem Spec
Reply

 Windows Update Errors 800B0100 & 8024200D




Thread Tools



Similar help and support threads for2: Windows Update Errors 800B0100 & 8024200D
Thread Forum
Solved Windows Update error 800B0100 abd 8024200D Windows Updates & Activation
Updates fail to install, errors: 800B0100 and 8024200D Windows Updates & Activation
Solved Windows 7 Update errors 800B0100 & 8024200D Windows Updates & Activation
Solved 800B0100 & 8024200D errors installing Win 7 SP1 on Samsung X64 laptop Windows Updates & Activation
Solved Windows Update error 800B0100,8024200D and 800737712 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 03:11 PM.
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