update KB2633952 corrupted, help needed

Discussion in 'Windows 7 Help and Support' started by Thomas211, Dec 17, 2011.

  1. Thomas211

    Thomas211 New Member

    Joined:
    Dec 17, 2011
    Messages:
    14
    Likes Received:
    0
    Ok so installed windows 7 ultimate 64bit on my MacBook Pro with Bootcamp and I had been updating it all day yesterday. I finally got to the SP1 and the daylight savings 2012 update (KB2633952) and tried to install them. Neither will work. I tried just doing the daylights one by itself, SP1 by itself, and neither will work. I did the system readiness check and this is what I got:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 13.0
    2011-12-16 22:57


    Checking Windows Servicing Packages


    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat


    Checking Package Watchlist


    Checking Component Watchlist


    Checking Packages


    Checking Component Store


    Summary:
    Seconds executed: 653
    Found 18 errors
    CBS MUM Corrupt Total count: 9
    CBS Catalog Corrupt Total count: 9


    Unavailable repair files:
    servicing\packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat




    Obviously it means that KB2633952 is corrupted.... But like I said I couldn't get that one to install in the first place... What should I do?? Should I just delete them and try install them or what?
     
    #1 Thomas211, Dec 17, 2011
    Last edited: Dec 17, 2011
  2. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    I would probably delete them (all packages for that update) and then hide that update and try to install SP1. Just hiding it might help without having to delete..

    I have no experience with Apple situations. Maybe something about the system time is different.

    800B0100 seems to mean no signature was present

    800F0900 An unexpected internal XML parser error occurred while attempting to read a manifest file.

    You might try installing in safe mode.

    You can download the updates directly if you have not tried that. Use IE to go to this Microsoft Site.

    Microsoft Update Catalog
     
  3. Thomas211

    Thomas211 New Member

    Joined:
    Dec 17, 2011
    Messages:
    14
    Likes Received:
    0
    I fixed it. I downloaded the savings time update and extracted the files and found all the package number files corresponding to the errors and followed this guide:Advanced guidelines for diagnosing and fixing servicing corruption
    and I fixed it withe the system readiness tool, like it said. It installed the daylight update just fine and I could then install SP1 and everything is updated now.
     
  4. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    That's a good link, thanks.

    Still wondering why your downloads were corrupted.....
     
  5. Thomas211

    Thomas211 New Member

    Joined:
    Dec 17, 2011
    Messages:
    14
    Likes Received:
    0
    Well the only thing I can think of is I was updating within Parallels 7 on my mac and I changed the name of the virtual machine linking to bootcamp and of course, parallels turned off because I wasn't supposed to change the name while running windows and windows was installing an update at the time. The update could of very well been the daylight one so when I rebooted it might of saw that those files were there, but they weren't really 100% there, thus they were basically corrupted. Thats the only thing I could think of causing it, very weird.
     

Share This Page

Loading...