Windows 7 Update Error. Can anyone help?

Discussion in 'Windows 7 Help and Support' started by drew carey, Nov 3, 2009.

  1. drew carey

    drew carey New Member

    Joined:
    Nov 3, 2009
    Messages:
    2
    Likes Received:
    0
    Hiya All

    First post.....got a bit of an issue.I have a new netbook which has windows 7 starter installed. Go to do all the initial updates. Firstly it hangs and eventually the laptop restarted of its own accord. When it had all rebooted, most of the updates had installed with the exception of three. Each of these won't install and I get an error.

    The error code is 800B0100 and apparently it relates to the security DLL's not being installed or working correctly. Windows recommend carrying out the system update readiness program, which I have done. I've then gone to carry out the three updates again but they still fail.

    I know I can ignore them and not download, but they are security updates so really want to get this sorted.

    Any suggestions??????
     
  2. MardyQuief

    MardyQuief New Member

    Joined:
    Jun 21, 2011
    Messages:
    4
    Likes Received:
    0
    I have a similar problem to this, I get the following error code Code 800B0100. The updates I am trying to install are the system stack update (KB2476490) and the SP1 update for x64 (KB976932). I have read around and know that I need the system stack update pre SP1 but I cannot get it to install it fails every time.

    I have tried downloading the standalone .exe it also fails. I have tried resetting the windows reg components and resetting the windows update settings. I have tried clearing the SoftwareDistribution folder in the system directory. I have run the system update readiness tool and found that some other unavailable repair files that I do not know. Can anybody tell me what these files are and where I can get these files or a tool to help me repair them. I believe this is what is preventing the first update working.

    here is the System update readiness tools log

    Code:
    
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 12.0
    2011-06-21 10:50
    
    
    Checking Windows Servicing Packages
    
    
    Checking Package Manifests and Catalogs
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat        
    
    
    Checking Package Watchlist
    
    
    Checking Component Watchlist
    
    
    Checking Packages
    
    
    Checking Component Store
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_19905f482e3c30f7.manifest    amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_19905f482e3c30f7    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_2387acc9495dfcbb.manifest    wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_2387acc9495dfcbb    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_23e5099a629cf2f2.manifest    wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_23e5099a629cf2f2    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_1af3213f123f9523.manifest    amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_1af3213f123f9523    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_1933027714fd3ac0.manifest    amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_1933027714fd3ac0    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_2547cb9146a0571e.manifest    wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_2547cb9146a0571e    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_25d368f05fbc2996.manifest    wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_25d368f05fbc2996    
    (f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_1b7ebe9e2b5b679b.manifest    amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_1b7ebe9e2b5b679b    
    
    
    Summary:
    Seconds executed: 144
     Found 22 errors
      CSI Manifest All Zeros Total count: 8
      CBS MUM Corrupt Total count: 7
      CBS Catalog Corrupt Total count: 7
    
    
    Unavailable repair files:
        winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_19905f482e3c30f7.manifest
        winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_2387acc9495dfcbb.manifest
        winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_23e5099a629cf2f2.manifest
        winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_1af3213f123f9523.manifest
        winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_1933027714fd3ac0.manifest
        winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_2547cb9146a0571e.manifest
        winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_25d368f05fbc2996.manifest
        winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_1b7ebe9e2b5b679b.manifest
        servicing\packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.mum
        servicing\packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_2_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_3_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_6_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_7_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
        servicing\packages\Package_for_KB2476490~31bf3856ad364e35~amd64~~6.1.1.0.cat
    
    
    Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the
    winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_19905f482e3c30f7.manifest
    winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_2387acc9495dfcbb.manifest
    winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.20861_none_23e5099a629cf2f2.manifest
    winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_1af3213f123f9523.manifest
    winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7600.16722_none_1933027714fd3ac0.manifest
    winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.17567_none_2547cb9146a0571e.manifest
    winsxs\manifests\wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_25d368f05fbc2996.manifest
    winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.21669_none_1b7ebe9e2b5b679b.manifest

    These are the files I am specifically interested in but I thought it good to show the whole log as well. Any help would be appreciated.

    Thanks
    Mardy
     
  3. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    There are quite a few sites that discuss "CBS Catalog Corrupt". They have different suggestions as to whether you can move/rename the package, or need to run Package Manager to remove it. After doing one or the other possibly Windows Update will try to download the update again.

    It may be easier, if you can, to uninstall the package if it is listed on the Installed Packages page in Windows Update. This is not the same as update history. Your situation may require the use of both methods.

    Windows Update works in some strange ways. There is a regulation reference that allows certain updates to be installed at certain times. All the parts of a package must be downloaded, and verified before it can be installed.

    Also keep in mind a good, unblocked, internet connection is essential. You can download the updates manually if it appears necessary.
     
  4. MardyQuief

    MardyQuief New Member

    Joined:
    Jun 21, 2011
    Messages:
    4
    Likes Received:
    0
    Thanks for your reply Saltgrass, I think I might have it sorted now I just decided to do a full repair of the OS to see if that sorts out the corruption I will post back, to let everyone know if this works. It does seem to be since I have got the service stack update installed now.

    Thanks for your help.
    Mardy

    Edit: The OS repair worked SP1 installed without issue and now windows is up to date :). Again thanks for your help.
     
    #4 MardyQuief, Jun 22, 2011
    Last edited: Jun 23, 2011
  5. spendleb

    spendleb New Member

    Joined:
    Jul 22, 2011
    Messages:
    4
    Likes Received:
    0
    I've got the same errors and MS Support don't seem to be getting to the bottom of resolving them, if the full repair of the OS worked, how do you go about running this?
     
  6. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
  7. spendleb

    spendleb New Member

    Joined:
    Jul 22, 2011
    Messages:
    4
    Likes Received:
    0
    Cheers, problem is I don't have the windows 7 installation disk, my laptop came preinstalled with the OS.
     
  8. Super Sarge

    Super Sarge New Member

    Joined:
    Jun 4, 2009
    Messages:
    1,737
    Likes Received:
    64
    When I had this problem I had to do a repair Install recommended by MS technet moderator, which is a PTA as it is a time consuming operation after it is done you have to run Windows update. I had to re-register some software. It took me 4 hours plus to get it done but it fixed my problem Repair Install - Windows 7 Forums


    • You can only do a repair install with the same edition Windows 7 installation disc for the same edition of Windows 7 that you have installed.
    • You cannot use a OEM Windows 7 "Factory" Restore/Recovery type of installation disc that came with or created from a store bought computer to do a repair install with. These can only be used do a clean install instead.
    • You can use a retail OEM Windows 7 to do a repair install with.
    • You can use a retail Windows 7 to do a repair install with.
    • You cannot do a repair install with a System Repair Disc. A System Repair Disc is not a installation disc, and will only boot to the System Recovery Options screen.
    • If you have a 32-bit (x86) Windows 7 currently installed, then you must use a 32-bit Windows 7 installation disc to be able to do a repair install with.
    • If you have a 64-bit (x64) Windows 7 currently installed, then you must use a 64-bit Windows 7 installation disc to be able to do a repair install with.
    • If you have Windows 7 SP1 installed, then you either must use a "retail" Windows 7 SP1 installation disc to be able to do a repair install, or uninstall SP1 to be able to use a retail Windows 7 installation disc to do a repair install with.
      • You can use a retail Windows 7 SP1 installation disc (ex: Technet (available), MSDN (available), or retail (when available)) to do a repair install with on a currently installed Windows 7 SP1.
      • You can use a Windows 7 SP1 installation disc (ex: Technet (available), MSDN (available), or retail (when available)) to do a repair install with on a currently installed slipstream Windows 7 SP1.
      • You cannot use a slipstream Windows 7 installation disc to do a repair install with on a currently installed Windows 7 SP1.
      • You cannot use a slipstream Windows 7 installation disc to do a repair install with on a currently installed slipstream Windows 7 SP1.
    • You can only do a repair install from within Windows 7.
    • You cannot do a repair install at boot or in Safe Mode.
    • You must be logged into Windows 7 in a administrator account to be able to do a repair install.
    • You must have at least 8.87 GB of free space, more if you have a larger installation, on the hard drive/partition Windows 7 is installed on to do a repair install.
    • If you changed the default location of the Program Files or Programs Files (x86) folder, then you will need to change it back to the C: drive, and change any shortcuts that pointed to the other location to also point to the C: drive before doing a repair install.




     
    #8 Super Sarge, Jul 22, 2011
    Last edited: Jul 22, 2011

Share This Page

Loading...