Win Update error codes 800B0100 and 80246007


  1. Posts : 3
    Windows 7 Home Premium 32bit
       #1

    Win Update error codes 800B0100


    I recently retired my XP OS on me desktop last week and Clean Installed Win7 Ultimate with SP1 x86 build 7601 then updated using win update, all updates were running smoothly then updated to IE11 manually by downloading the installer, then run win update all updates were installed ok, except for these 4 updates that keeps on failing;
    KB2585542
    KB2785220
    KB2655992
    KB2506928
    I have error code 800B0100

    Here my CBS.
    Last edited by jstevens16; 14 Feb 2014 at 01:18. Reason: Needed to follow posting instructions.
      My Computer


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

    From the looks of it you had an update which got interrupted mid-way through an install.
    Here's the error-list from the CheckSUR scan.
    Code:
    Unavailable repair files:
     winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22465_none_603a326269238bd7.manifest
     winsxs\manifests\x86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18270_none_23d8b7cfb3b95442.manifest
     winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18270_none_5fa0c25350128c24.manifest
     winsxs\manifests\x86_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18270_none_a80cf783bb41b5b7.manifest
     winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.18270_en-us_886a4112f511d4a8.manifest
     winsxs\manifests\x86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22465_none_247227deccca53f5.manifest
     winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22465_en-us_8903b1220e22d45b.manifest
     winsxs\manifests\x86_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22465_none_a8a66792d452b56a.manifest
     servicing\packages\Package_30_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_30_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_32_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_32_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_55_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_55_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_56_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_56_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_57_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_57_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_58_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_58_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2868725_SP1~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2868725_SP1~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_30_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_30_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_32_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_32_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_55_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_55_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_56_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_56_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_57_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_57_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_58_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_58_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2868725_SP1~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2868725_SP1~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2868725~31bf3856ad364e35~x86~~6.1.1.1.cat
    I'll post a fix protocol later, when I have time.
      My Computer


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

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


 

  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 02:14.
Find Us