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:


  1. 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. 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.


    2. We are encountering the same issue after applying the security updates. The createsite.aspx page throws “Sorry Something Went Wrong” and “Common Language Runtime detected an invalid program” error. This is on a SharePoint 2013 Foundation farm that previously worked fine.


      1. Hi Ken,
        in this case I would recommend to open a support case with Microsoft to get this analyzed.


    3. Same issue after Oct 2017 CU cannot create site collection!


  3. Hi Stefan
    Any advice on what to install to stay “supported”
    Based on this I would need to install the April 2017 PU at a minimum
    What would MS be looking for when a user calls premier support?
    Would not having the April 2017 PU keep new patches from being installed


    1. Hi Dominick,
      after April 2017 only security fixes will created – no regular CUs as regular CUs are only created during mainstream support.
      Newer security fixes should also install on older CUs but if you are in a need to get support from Microsoft and you are on an older CU you will have to apply one of the supported CUs first.


  4. Hi ,
    Can someone please confirm do we need to run the ps.config after installing •KB 3213623 – Word Automation Services for SharePoint 2010
    •KB 4011194


    1. Hi Manoj,
      there is not a single SharePoint fix which would not require psconfig.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.