locked
KB3114409 - faulty update is still on WSUS servers RRS feed

  • Question

  • Can someone in the WSUS team expire this faulty update off of the WSUS servers please? This is still causing issues.
    Friday, December 11, 2015 6:02 PM

Answers

  • KB3114409 was eventually "Expired" by MS on January 13th.

    Rolf Lidvall, Swedish Radio (Ltd)

    Friday, January 15, 2016 1:10 PM

All replies

  • DItto
    Saturday, December 12, 2015 3:05 PM
  • AFAIK, if MS has not changed that recently, it is the products teams that are responsible for distributing and expiring updates on WSUS. In this case you should contact the  The Microsoft Office Sustained Engineering Team.

    I just declined the update when they updated the article with the statement "This update is no longer available now":

    December 8, 2015, update for Outlook 2010 (KB3114409)


    Rolf Lidvall, Swedish Radio (Ltd)

    • Proposed as answer by Elton_Ji Tuesday, December 15, 2015 6:32 AM
    • Unproposed as answer by Susan BradleyMVP Tuesday, December 15, 2015 2:51 PM
    Sunday, December 13, 2015 2:22 PM
  • http://blogs.technet.com/b/office_sustained_engineering/archive/2015/12/08/december-2015-office-update-release.aspx

    and how do I do that when their blog doesn't accept comments and there's no way to contact them via that blog that I can see?

    I realize that we can decline the update, but every other time that I can recall before this, an patch removed from MU with known issues was removed from WSUS.  I am under the strong opinion that this should be no different.

    Sunday, December 13, 2015 4:31 PM
  • Hi Sir,

    As that article stated , that update is no longer avaiable now .

    I'm trying to update my wsus server for office 2010   to see if it exists .

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .


    • Edited by Elton_Ji Wednesday, December 16, 2015 10:42 AM
    Wednesday, December 16, 2015 10:11 AM
  • Folks,

    This update keeps coming back to our WSUS installs. Approx 100 networks.

    We manually set it to "Approved for Uninstall" but the next day everyone has it again.

    Usually once there is a bad update the WSUS team expire the update so all we need to do is "approve for uninstall" to remove it and the next time WSUS syncs, the update is then expired so won't get triggered in the auto approve rules. 

    What's different about this update?  Looking back through the WSUS sync logs it looks like the WSUS team still have not expired it for some reason.

    Is anyone from the WSUS team on this forum to explain?





    • Edited by technet usr Wednesday, December 16, 2015 10:56 AM
    Wednesday, December 16, 2015 10:54 AM
  • Is anyone from the WSUS team on this forum to explain?


    maybe ping the WSUS team via their blog?
    http://blogs.technet.com/b/wsus/

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, December 16, 2015 11:33 AM
  • Hi Elton

    Seems all are sound asleep at MSFT. OP is pretty clear, the update is still on WSUS, it has only been pulled from MU.

    Don't you understand this update is causing major havoc for WSUS users, particularly those running WSUS on SBS2008 or SBS2011? On SBS you can approve the update for uninstall (or decline the update and manually uninstall) however SBS reverts these settings within hours unless you set update approval to "LOW" on the SBS console. Setting approval level for updates to LOW makes the changes made in WSUS stick, however it obviously compromises network security.

    PLEASE WAKE UP!!!

    Kind regards,


    Henk Panneman - http://www.homeserverweb.nl


    • Edited by brubber Wednesday, December 16, 2015 12:44 PM
    Wednesday, December 16, 2015 12:35 PM
  • I used the "contact blog author option" on the WSUS blog but got an auto reply email from an old mailbox saying he is no longer with MS and to contact another email address listed. Unfortunately email the address listed in the auto reply bounced back with an NDR (mailbox does not exist).

    No way to contact the WSUS team it seems.

    Wednesday, December 16, 2015 12:52 PM
  • I've send them a message using the contact form at http://blogs.technet.com/b/sus/contact.aspx. Did not receive copy of the message but also no bounce messages.  

    Henk Panneman - http://www.homeserverweb.nl

    Wednesday, December 16, 2015 1:47 PM
  • https://support.microsoft.com/en-us/kb/3114560

    And this update isn't on WSUS either.

    Tuesday, December 22, 2015 5:11 AM
  • Hi,

    we had 76 system affected. Applied approve to remove with deadline 1 month and after 48h only 8 system remaind having ths patch installed. that solved the problem for us, but still will be watching it near deadline, if all system are rid of it.

    Tuesday, December 22, 2015 9:57 AM
  • KB3114409 was eventually "Expired" by MS on January 13th.

    Rolf Lidvall, Swedish Radio (Ltd)

    Friday, January 15, 2016 1:10 PM
  • The amount of time it took and the lack of communication regarding this issue has me deeply concerned.
    Friday, January 15, 2016 6:28 PM