Results 1 to 4 of 4
  1. #1
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Tacoma, Washington, USA
    Posts
    431
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Automating Removal of Bad Outlook 2010 Patch KB2956128

    We are one of those who has a problem with Outlook 2010 update KB2956128 which was pushed out last week. Specifically, our Outlook 2010/Exchange 2010 users cannot search shared folders. They get the error, "The attempted operation failed. An object could not be found." Woody tweeted last Friday about it but didn't see that until I did some looking today after receiving phone calls. More information found here on infoworld [http://www.infoworld.com/article/288...failures.html].

    I didn't realize it was installed twice for the same KB. The first time I uninstall this patch, reboot, and checked it was still there. Next computer I realized there are two instances for this same KB to be uninstalled. Hoping this save someone a little frustration. After uninstalling both and reboot, I checked Windows Update and hide the update so it won't automatically install again in the future.

    In the above article's comments a couple of users posted some code for removing the bad patch. Specifically:

    Code:
    msiexec /I {90140000-0012-0000-0000-0000000FF1CE}MSIPATCHREMOVE={DEFF916D-4268-49CF-8FF3-E26253582E13}
    msiexec /i {90140000-001A-0409-0000-0000000FF1CE}MSIPATCHREMOVE={DEFF916D-4268-49CF-8FF3-E26253582E13}
    We used Desktop Authority for handling log in and log out settings. I can add a pre-engine or post-engine script in .kix, .ps1, or .vbs format. I'm a script newb so need a little help. These are all Windows 7 Professional 64bit computers with Office 2010 64bit installed. Will this code work or something like it? How would I add the code from the above article's comments into one of these scripts? Is there also a way to add code to hide the KB to avoid it being installed again? If it's possible, would I want to run it pre or post?
    Daisy

  2. #2
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Tacoma, Washington, USA
    Posts
    431
    Thanks
    0
    Thanked 3 Times in 3 Posts
    Never find a way to do this with a login script. I manually uninstalled KB2956128 one workstation at a time. Still have more than half of them left to do.

    Here we are now in March and Microsoft update has pushed out more updates, and once again has caused this problem with a new patch. I haven't figured out which one it is yet. Has someone had this same problem and figured out what patch it is so I can get started, again, to uninstall and block the new one?
    Daisy

  3. #3
    New Lounger
    Join Date
    Mar 2015
    Posts
    1
    Thanks
    0
    Thanked 2 Times in 1 Post
    Quote Originally Posted by ailios View Post
    Never find a way to do this with a login script. I manually uninstalled KB2956128 one workstation at a time. Still have more than half of them left to do.

    Here we are now in March and Microsoft update has pushed out more updates, and once again has caused this problem with a new patch. I haven't figured out which one it is yet. Has someone had this same problem and figured out what patch it is so I can get started, again, to uninstall and block the new one?
    The culprit ist Update KB2956203, also installed in two instances, both have to be removed. https://support.microsoft.com/en-us/kb/2956203

  4. The Following 2 Users Say Thank You to fub4r For This Useful Post:

    chubbers (2015-04-20),Plimba Fernandez (2015-03-27)

  5. #4
    New Lounger
    Join Date
    Apr 2015
    Posts
    1
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by fub4r View Post
    The culprit ist Update KB2956203, also installed in two instances, both have to be removed. https://support.microsoft.com/en-us/kb/2956203
    I am desperately trying to figure out how to uninstall the "multiple instances" of this update silently. (Specifically with a script deployed via SCCM). Any help would be GREATLY appreicated!!!

    Thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •