Windows Update Errors 800B0100 & 8024200D

Page 1 of 2 12 LastLast

  1. Posts : 54
    Windows 7 HP 64 bit
       #1

    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 Computer


  2. Posts : 54
    Windows 7 HP 64 bit
    Thread Starter
       #2

    Here is the CheckSUR log file
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    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 Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    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 Computer


  5. Posts : 54
    Windows 7 HP 64 bit
    Thread Starter
       #5

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


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    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 Computer


  7. Posts : 54
    Windows 7 HP 64 bit
    Thread Starter
       #7

    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)
      My Computer


  8. Posts : 54
    Windows 7 HP 64 bit
    Thread Starter
       #8

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


  9. Posts : 365
    Windows 10 Pro - 64 bit
       #9

    try and do an full shutdown of the computer , not a restart . then try windows update again .. This usually works for me ..
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 16:56.
Find Us