Windows 7 Update errors 800B0100 & 8024200D


  1. Posts : 4
    Windows 7 Ultimate 64bit
       #1

    Windows 7 Update errors 800B0100 & 8024200D


    Hello,

    I'm having some problems with Windows Updates. Updates gives me errors 800B0100 & 8024200D.
    I have just re-installed my Windows 7 (Ultimate 64bit) and never had this problem before.
    Could somebody help me. I have tried everything already.

    Please, see the attachments.

    BR,
    Sukkis
    Last edited by Sukkis; 11 Nov 2013 at 15:10.
      My Computer


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

    You have a number of errors in the CheckSUR scan...
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.1.7601.22296_none_760c8d5fd494972b.manifest
     winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.18203_none_114dcae97cfeb81b.manifest
     winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22378_none_1190b9b296509a2f.manifest
     winsxs\manifests\amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22378_none_b50e1435e537e098.manifest
     winsxs\manifests\x86_wpf-presentationcffrasterizernative_31bf3856ad364e35_6.1.7601.22400_none_cc2d1a0205adc811.manifest
     winsxs\manifests\amd64_wpf-presentationcffrasterizernative_31bf3856ad364e35_6.1.7601.22400_none_284bb585be0b3947.manifest
     winsxs\manifests\wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22378_none_bf62be881998a293.manifest
     winsxs\manifests\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.1.7601.18126_none_75cea008bb3e33ca.manifest
     winsxs\manifests\amd64_microsoft-windows-t..ournalnotewriterqfe_31bf3856ad364e35_6.1.7601.22296_none_abf33f1faea12fec.manifest
     winsxs\manifests\amd64_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_6.1.7601.22296_none_28eb8ce7670bc319.manifest
     winsxs\manifests\x86_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_6.1.7601.22296_none_ccccf163aeae51e3.manifest
     winsxs\manifests\amd64_microsoft-windows-t..ournalnotewriterqfe_31bf3856ad364e35_6.1.7601.18126_none_abb551c8954acc8b.manifest
     winsxs\manifests\amd64_wpf-presentationcffrasterizernative_31bf3856ad364e35_6.1.7601.18219_none_27c04982a4ed9c56.manifest
     winsxs\manifests\x86_wpf-presentationcffrasterizernative_31bf3856ad364e35_6.1.7601.18219_none_cba1adfeec902b20.manifest
     winsxs\manifests\amd64_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_6.1.7601.18126_none_28ad9f904db55fb8.manifest
     winsxs\manifests\x86_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_6.1.7601.18126_none_cc8f040c9557ee82.manifest
     winsxs\manifests\amd64_microsoft-windows-t..c-journalnotewriter_31bf3856ad364e35_6.1.7601.18126_none_a082072163ab7b11.manifest
     winsxs\manifests\amd64_microsoft-windows-t..c-journalnotewriter_31bf3856ad364e35_6.1.7601.22296_none_a0bff4787d01de72.manifest
     servicing\packages\Package_1_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_1_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_3_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2835364_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2861191_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2868623_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_1_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_1_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_2_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_3_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2835364_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2835364~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2861191_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2868623_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2868623~31bf3856ad364e35~amd64~~6.1.1.1.cat
    The SFC log is clear - but there are a lot of background errors caused by the above problems.

    I'll post a fix for them later.
    Last edited by NoelDP; 12 Nov 2013 at 07:39.
      My Computer


  3. Posts : 4
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    Thanks NoelDP!!
      My Computer


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

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

    Then run another SFC /SCANNOW, and post the new CBS.log file - this will tell us if there are any new problems that have been highlighted.
      My Computer


  5. Posts : 4
    Windows 7 Ultimate 64bit
    Thread Starter
       #5

    Hello,

    Thank u NoelDB!

    I copied the files and ran Checksur and sfc /scannow. After that i ran win update.

    Here is the logs BEFORE windows update and AFTER windows update.
    There was one 8024200D error after i ran windows update. But i downloaded and installed the KB file manually and now windows update shows that there is no updates available and every update succeeded.

    Can u still find some errors from the logs that might affect somehow in future.
    Do u need the latest logs after i installed KB manually?

    BR,
    Sukkis
      My Computer


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

    From the look of it your SoftwareDistribution folder was mildly corrupt, and missing a couple of files from the KB2813430 installer. Windows update has now pruned those files out or replaced them - I assume this is the one that you managed to install from download?)
    Check Windows Updates again later today - a few new ones may appear, so see if they install without any problems.
      My Computer


  7. Posts : 4
    Windows 7 Ultimate 64bit
    Thread Starter
       #7

    Yep, that KB2813430 was the one i succesfully updated manually.
    I just updated 10 different updates and everything went well. All the updates succeeded.
    So thank you so much NoelDB for your help!!

    BR,
    Sukkis
      My Computer


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

    You're welcome - good luck!
      My Computer


 

  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 19:20.
Find Us