SharePoint security fixes released with October 2016 PU and offered through Microsoft Update


SharePoint 2007 Suite:

  • none

SharePoint 2010 Suite:

  • Word Automation Services for SharePoint 2010
  • Office Web Apps 2010

SharePoint 2013 Suite:

  • Word Automation Services for SharePoint 2013
  • Office Web Apps 2013

SharePoint 2016 Suite:

  • Office Online Server 2016

See the security bulletin below for more details and KB number for the relevant fixes:

Comments (6)

  1. David says:

    These updates are coming through as regular updates in SCCM as opposed to Farm-Deployment updates. Does that mean that psconfig doesn’t need to be run after they’re installed?

    1. Hi David, no that is not the Case.
      There is not a single SharePoint fix which does not require PSConfig.
      Also SCCM deployed fixes require PSConfig. Always.
      See here for detail:
      https://blogs.technet.microsoft.com/stefan_gossner/2015/09/09/why-we-recommend-require-to-run-the-configuration-wizard-also-for-security-fixes/
      Cheers,
      Stefan

      1. David says:

        Thanks for the clarification.

  2. Dominick says:

    Is there any truth to MS making all patches for windows and SharePoint one .exe with no way to separate them?
    We are being told by our patch guys its all one package and we can no longer stop SP patches unless we stop all

    1. No that is not the case.

      1. Dominick says:

        When we installed MS16-121 and check under control panel /installed products/installed updates I see 2 patches for the corresponding KB#3118352
        Seems like all security updates for SP do this, any reason why?

        I ended up with one server that had only 1 and I think its preventing the wizard from running due to software mismatch

        thanks

Skip to main content