Windows 7 SP1 Update Unknown Error 800B0100

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 Home Premium x64 SP1
       #1

    Windows 7 SP1 Update Unknown Error 800B0100


    Hi guys,

    I'm having a problem with Windows Update. There are about 6 Security Updates which just will not install.
    I've run Fixit and the SUR Tool, but nothing seems to work.
    Tried installing one at a time to no avail.

    I keep getting: Code 800B0100 Windows Update encountered an Unknown Error.

    I've attached the CheckSUR files to help. Let me know if I need to provide anything else?

    Thanks so much!
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    Code:
    Checking Package Manifests and Catalogs
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat		
    (f)	CBS MUM Corrupt	0x800F0900	servicing\Packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum		Line 1: 
    (f)	CBS Catalog Corrupt	0x800B0100	servicing\Packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
    As you can see they are corrupt i have only highlighted a few for you.

    I suggest you try the following:

    1. Use SFC to scan whole system files
    How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

    2. Reset the windows update components
    How do I reset Windows Update components?

    Try these and post back! :)
      My Computer


  3. Posts : 5
    Windows 7 Home Premium x64 SP1
    Thread Starter
       #3

    Hi there,

    Thanks for the reply.
    I've tried the 2 steps.

    1) After running sfc, I got the message: Windows Resource Protection did not find any integrity violations.

    2) After running the Reset, I got this message (see attached pic), which says that the Windows Update Error could not be automatically fixed.

    Anything else I should be trying?
      My Computer


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

    Here's the full list of problem files from your CheckSUR
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.22640_none_e6f95b20c6af545f.manifest
     winsxs\manifests\wow64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.22640_none_f14e0572fb10165a.manifest
     winsxs\manifests\x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22743_none_a2686eb6b6ccf3c7.manifest
     winsxs\manifests\amd64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.18431_none_e67b8ca5ad88b4d4.manifest
     winsxs\manifests\wow64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.18431_none_f0d036f7e1e976cf.manifest
     winsxs\manifests\amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.18532_none_1208ed525bc5f875.manifest
     winsxs\manifests\wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.18532_none_1c5d97a49026ba70.manifest
     winsxs\manifests\amd64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.22640_none_e6f916c8c6afa142.manifest
     winsxs\manifests\wow64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.22640_none_f14dc11afb10633d.manifest
     winsxs\manifests\amd64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.18431_none_e67b484dad8901b7.manifest
     winsxs\manifests\wow64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.18431_none_f0cff29fe1e9c3b2.manifest
     winsxs\manifests\amd64_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22743_none_fe870a3a6f2a64fd.manifest
     winsxs\manifests\amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22743_none_1288bc6174eacaae.manifest
     winsxs\manifests\wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22743_none_1cdd66b3a94b8ca9.manifest
     servicing\packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_2_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
     servicing\packages\Package_for_KB2922229_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
     servicing\packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2939576_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2939576~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.cat
    I'll post a fix protocol a little later.
      My Computer


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

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


  6. Posts : 5
    Windows 7 Home Premium x64 SP1
    Thread Starter
       #6

    Hi there,

    Thanks for your reply.
    I've done as you requested. Here are the files after I ran the SUR tool.

    Appreciate the help!
      My Computer


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

    Woops! - musta missed one...
    Code:
    Unavailable repair files:
     winsxs\manifests\wow64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.22640_none_f14e0572fb10165a.manifest
    I'll post another fix for that in a few minutes.
      My Computer


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

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


  9. Posts : 5
    Windows 7 Home Premium x64 SP1
    Thread Starter
       #9

    Heya,

    Thanks for the fixes. After reading the log, it said that the errors were fixed, so I decided to run the Windows Update again.

    Previously there were 7 updates which did not install. Now 4 have successfully installed, 3 have errors.
    (I've tried updating them individually, to no avail)

    The error code I'm getting now is 8024200D.
    The 3 error updates are: KB2832414, KB2564958 and KB2676562

    I ran the sfc and Update reset (and got the same results as I did before).
    Not sure what else I can do. Thanks again for your patience!
      My Computer

  10.   My Computer


 
Page 1 of 2 12 LastLast

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