Update error 800B0100 when installing Windows 7 SP1


  1. Posts : 4
    win 7 64bit
       #1

    Update error 800B0100 when installing Windows 7 SP1


    Tried all the usual Fixit steps found while searching for 800B0100 error.
    Here are the CBS logs.
    Thanks for the help.
      My Computer


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

    There are a number of corrupt files, according to CheckSUR -
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.17578_none_098c4a392817e693.manifest
     winsxs\manifests\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.17578_none_ad6daeb56fba755d.manifest
     winsxs\manifests\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.20923_none_ac41fe8a8b8d9bfa.manifest
     winsxs\manifests\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.21682_none_0a05155c41430a44.manifest
     winsxs\manifests\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.21682_none_ade679d888e5990e.manifest
     winsxs\manifests\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.20923_none_08609a0e43eb0d30.manifest
     winsxs\manifests\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.16779_none_07a6ed7d2af093fe.manifest
     winsxs\manifests\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.16779_none_ab8851f9729322c8.manifest
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
    SFC appears to be clear at the moment.

    I'll post a fix later.
      My Computer


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

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


  4. Posts : 4
    win 7 64bit
    Thread Starter
       #4

    Thanks, the CheckSUR log looks hopeful.
      My Computer


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

    Great - CheckSUR is now clear.

    Please run another SFC /SCANNOW and post the new CBS.log - let's have another look just in case that's brought anything out of the woodwork.
    If it says 'nothing found', then go ahead and do a new Check for Updates, and see what happens.
      My Computer


  6. Posts : 4
    win 7 64bit
    Thread Starter
       #6

    I did get SP1 to update and several others. However I am still getting an error on KB2522422 code 8024200d. That was the one that was missing in the CheckSUR log. Should I ignore that update?
      My Computer


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

    Run a manual Check for Updates - if it still appears, post the CBS folder (entire) again, and I'll take another look.
      My Computer


  8. Posts : 4
    win 7 64bit
    Thread Starter
       #8

    OK this time it said kb2522422 wasn't necessary. So it looks like I'm back on track with the updates.
    Many thanks to you and your team.
      My Computer


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

    Great!

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