Windows Update Error 0x800B0100

Page 1 of 2 12 LastLast

  1. aphughes
    Posts : 7
    Windows 7 Home Premium x64
       New #1

    Windows Update Error 0x800B0100


    When I installed the MS Tuesday updates for Feb. I got error 0x800B0100 for kb2901112, kb2911501, and kb2843630. When the updates for March came out, they all installed but these three still got the same error. I have tried several 'fixes': reset the update history; rename SoftwareDistribution\Download; went back to a previous checkpoint; manually installed from MS downloads; run Windows Update Troubleshooter; run System Update Readiness Tool; run sfc.exe (per this site); uninstalled and reinstalled .net framework (two of the problem updates are for an older version, I have 4.5.1, they are for 3.5.1). Still the same problem.

    Thanks for any help.

    CBS.zip attached
      My Computer
    Quote Quote

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

    You have some significant problems!

    Here's the CheckSUR report summary...
    Code:
    Summary:
Seconds executed: 938
 Found 50 errors
  CSI Manifest Missing Total count: 4
  CSI Manifest All Zeros Total count: 22
  CBS MUM Corrupt Total count: 12
  CBS Catalog Corrupt Total count: 12
Unavailable repair files:
 winsxs\manifests\x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.22515_none_8277774b629404e6.manifest
 winsxs\manifests\x86_netfx-_vsavb7rt_b03f5f7f11d50a3a_6.1.7601.22553_none_3ca3033c8f1a4ab2.manifest
 winsxs\manifests\msil_system.web.resources_b03f5f7f11d50a3a_6.1.7601.18320_en-us_53dd4f2356138a68.manifest
 winsxs\manifests\amd64_netfx-system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.18320_none_7e1d06775ff8f8a9.manifest
 winsxs\manifests\x86_netfx-_vsavb7rt_b03f5f7f11d50a3a_6.1.7601.18354_none_53709358757303fc.manifest
 winsxs\manifests\amd64_system.web_b03f5f7f11d50a3a_6.1.7601.22515_none_6d0915a6d8526a13.manifest
 winsxs\manifests\amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.18320_none_c34fc404e0119b41.manifest
 winsxs\manifests\amd64_netfx-_vsavb7rtui_b03f5f7f11d50a3a_6.1.7601.22553_none_c644f371ed042100.manifest
 winsxs\manifests\amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.18320_none_5199598a346f14bb.manifest
 winsxs\manifests\amd64_system.web_b03f5f7f11d50a3a_6.1.7601.18320_none_83d82ebcbea9a2ee.manifest
 winsxs\manifests\msil_microsoft.vsa.vb.codedomprocessor_b03f5f7f11d50a3a_6.1.7601.18354_none_18dc5c35af3891ba.manifest
 winsxs\manifests\msil_system.web.resources_b03f5f7f11d50a3a_6.1.7601.22515_en-us_3d0e360d6fbc518d.manifest
 winsxs\manifests\x86_system.web_b03f5f7f11d50a3a_6.1.7601.22515_none_b4b64c7decce9319.manifest
 winsxs\manifests\x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.18320_none_9946906148eb3dc1.manifest
 winsxs\manifests\msil_system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.22515_none_0b196e0ef4cad6cb.manifest
 winsxs\manifests\x86_system.web_b03f5f7f11d50a3a_6.1.7601.18320_none_cb856593d325cbf4.manifest
 winsxs\manifests\amd64_netfx-system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.22515_none_674ded6179a1bfce.manifest
 winsxs\manifests\msil_microsoft.vsa.vb.codedomprocessor_b03f5f7f11d50a3a_6.1.7601.22553_none_020ecc19c8dfd870.manifest
 winsxs\manifests\x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.22515_none_f42de1c60e368b6c.manifest
 winsxs\manifests\amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.22515_none_ac80aaeef9ba6266.manifest
 winsxs\manifests\x86_netfx-_vsavb7rtui_b03f5f7f11d50a3a_6.1.7601.22553_none_0df22a4901804a06.manifest
 winsxs\manifests\amd64_netfx-_vsavb7rtui_b03f5f7f11d50a3a_6.1.7601.18354_none_dd12838dd35cda4a.manifest
 winsxs\manifests\x86_netfx-_vsavb7rtui_b03f5f7f11d50a3a_6.1.7601.18354_none_24bfba64e7d90350.manifest
 winsxs\manifests\x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.18320_none_0afcfadbf48dc447.manifest
 winsxs\manifests\msil_system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.18320_none_21e88724db220fa6.manifest
 winsxs\manifests\amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.22515_none_3aca40744e17dbe0.manifest
 servicing\packages\Package_1_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_1_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_2_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_2_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_3_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_5_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_5_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
 servicing\packages\Package_for_KB2843630~31bf3856ad364e35~amd64~~6.1.3.1.mum
 servicing\packages\Package_for_KB2843630~31bf3856ad364e35~amd64~~6.1.3.1.mum
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_1_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_1_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_2_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_2_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_3_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_5_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_5_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
 servicing\packages\Package_for_KB2843630~31bf3856ad364e35~amd64~~6.1.3.1.cat
 servicing\packages\Package_for_KB2843630~31bf3856ad364e35~amd64~~6.1.3.1.cat
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2901112~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2911501~31bf3856ad364e35~amd64~~6.1.1.2.cat
    I'll post a fix protocol when I can - tomorrow evening probably.
      My Computer
    Quote Quote

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

    I've uploaded a file - aphaa.zip - to my OneDrive at Noel's OneDrive
    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 aphaa 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
    Quote Quote

  6. aphughes
    Posts : 7
    Windows 7 Home Premium x64
    Thread Starter
       New #4

    I did as you asked. Afterwards I checked for updates using Windows Update. It now shows the three original problem updates plus SUR kb947821. I did not attempt to install anything yet. Logs attached.
      My Computer
    Quote Quote

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

    It looks like you miss-read part of my instructions
    Code:
    Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages
    - all the Manifests were fixed, but none of the Packages.

    Please try that part again, and run another CheckSUR scan - post the new CheckSUR.log file
      My Computer
    Quote Quote

  8. aphughes
    Posts : 7
    Windows 7 Home Premium x64
    Thread Starter
       New #6

    mea culpa. I may be old but I remember being sharp.
      My Computer
    Quote Quote

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

    :)
    I know the feeling!

    there's still a few left for us to fix...
    Code:
    Unavailable repair files:
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2843630_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
 servicing\packages\Package_for_KB2901112_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2911501_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
    I'll work on them when I can - back soon, I hope!
      My Computer
    Quote Quote

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

    I've uploaded a file - aphab.zip - to my OneDrive at Noel's OneDrive
    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 aphab in the same place.
    Open this folder - there should be one folders insid it (Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    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
    Quote Quote

  12. aphughes
    Posts : 7
    Windows 7 Home Premium x64
    Thread Starter
       New #9

    Should I try to install the updates?
      My Computer
    Quote Quote

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

    Go for it! :)

    DO a Check for Updates first, and then attempt the install of any found updates - if they fail, note the error shown, and post back with it.
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
Windows Update error message 0x800B0100
in Windows Updates & Activation

Hi all, I had this error on my two laptops and desktop at the same time! I was able to get one laptop and the desktop working by repeatedly running the WindowsUpdateDiagnostic.diagcab until all the errors were gone and updates would work. Can't get seem to get it to work on the other laptop. I...
Windows update error 0x800B0100
in Windows Updates & Activation

Windows update worked fine for the first 100 updates but then stopped working and now just hangs on searching for updates. I have installed SURT and also ran sfc /scannow which showed no problems. When i run the windows update diagnostics tool it shows; Windows update error 0x800B0100 ...
Windows Update Error 0x800b0100
in Windows Updates & Activation

Can anyone help with this please ? Its actually got me beat ! Noticed that MSE failed to start. Then a box appeared stating that it was repairing .Net 4.5 ! The repair completed with no change. A restart starts the whole procedure again. I then noted that Windows Update will not run,...
Noel ... I received "again" the “Windows Not Genuine” message screen! System Properties show me “Windows 7 Home Premium”, Windows activation: “Windows is activated, Product ID: 00359-OEM-8882432-58635, The MGADiagnostics tool responds my version is “Genuine” (see below!) Today I received...
Windows 7 Update error 0x800B0100
in Windows Updates & Activation

I've got a user that has been having the Windows 7 SP1 update fail after multiple install attempts. You can probably guess that I've browsed the web several times over and can find no resolution to the issue. The error code is the rather bland 0x800B0100 - the least helpful error code since the...
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 03:42.
Find Us