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

As I received some feedback that I should also add the Urls to the KB articles of the different security fixes I added this information to my blog post.

SharePoint 2007 Suite:

  • none

SharePoint 2010 Suite:

  • KB 3213623 - Word Automation Services for SharePoint 2010
  • KB 4011194 - Office Web Apps 2010

SharePoint 2013 Suite:

  • KB 4011180 - SharePoint Foundation 2013
  • KB 4011170 - SharePoint Server 2013 (core components)
  • KB 4011068 - Word Automation Services for SharePoint 2013
  • KB 4011231 - Office Web Apps Server

SharePoint 2016 Suite:

  • KB 4011217 - SharePoint Server 2016 (language independent)
  • KB 3213659 - Office Online Server 2016

See the Security Update Guide below for more details about the relevant fixes:

More information:

Comments (4)

  1. Sajid Ali says:

    Hi Stefan,

    After installing these SharePoint 2013 server PU, do we need to run the configuration wizard?

    Thank You

    1. Hi Sajid,
      as there is not a single SharePoint fix which would not require the config wizard.
      So: yes.

  2. Michael Heuer says:

    Hi Stefan,

    my post is 100% in the wrong category, even it’s the same product. Did you recognize any problems with SharePoint 2013 (version doesn’t matter) after that patch day?
    I got issues when I navigated in the Central Administration on “Create new SiteCollection”.
    The error I got is:
    “Sorry, something went wrong
    Common Language Runtime detected an invalid program.”
    With SharePoint 2010, this issue is not coming up, so i guess it could have something to do with .NET.
    Thanks in advance for your answer.

    1. Hi Michael,
      haven’t seen this. The error indicates that there is a dll with corrupted content.
      Would be important to isolate which dll this is.

Skip to main content