Error 0x800b0100 when running windows update for KB2813430 and KB28086


  1. 139947
    Posts : 2
    Windows 7 Ultimate x64
       New #1

    Error 0x800b0100 when running windows update for KB2813430 and KB28086


    Hi,
    some of you may already be familiar about this problem. Though i tried to follow the fixes provided on this forum but I cant seem to have any luck on getting this resolved.
    I am attaching the logs created upon running SURT, I'll be honest, I attempted to run SURT quite a few times in an attempt to fix the problem.
    Thanks in advance!
      My Computer
    Quote Quote

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

    Please don't save the files as .doc Word files - they are already in readable format as .log files if you want to read them (use Notepad)

    Your problems are the following files.... and possibly others, since you failed to also post the CBS.log after running SFC /SCANNOW.

    Code:
    Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22311_none_a27469edd50ac61f.manifest
 winsxs\manifests\amd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.18142_none_9776b17087a3d45d.manifest
 winsxs\manifests\amd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.22311_none_981fbf9ba0aa0424.manifest
 winsxs\manifests\wow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.18142_none_a1cb5bc2bc049658.manifest
 servicing\packages\Package_112_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_112_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_113_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_113_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_114_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_114_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_115_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_115_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_45_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_45_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_59_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_59_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_75_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_75_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_76_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_76_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_83_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_83_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2808679_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2808679_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_112_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_112_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_113_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_113_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_114_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_114_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_115_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_115_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_45_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_45_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_59_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_59_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_75_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_75_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_76_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_76_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_83_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_83_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2808679_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2808679_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2808679~31bf3856ad364e35~amd64~~6.1.1.2.cat
    I'll post a fix protocol for the errand Package files later - please run SFC and upload the CBS.log file as below....


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

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

    Here's the fix for the known errors so far....

    I've uploaded a file - 139aa.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 139aa 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. 139947
    Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       New #4

    thanks for your help. I will follow these steps and will let you know wether it's fixed or not.
      My Computer
    Quote Quote

 

  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,...
Windows Update Error 0x800B0100
in Windows Updates & Activation

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...
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 05:30.
Find Us