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


With February 2016 PU we have released security fixes for SharePoint which are offered through Microsoft Update.

For the following SharePoint products and components fixes have been released:

SharePoint 2007 Suite:

  • Excel Services

SharePoint 2010 Suite:

  • Excel Services
  • Office Web Apps 2010

SharePoint 2013 Suite:

  • Excel Services
  • Word Automation Services
  • Office Web Apps 2013
  • SharePoint Foundation 2013

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


Comments (14)

  1. Kaylex11 says:

    Good Afternoon,

    I am not sure if this has been discussed previously but does installing the security updates through windows update require running psconfig after? I have see from some users it is like a PU and is required and some that it is not.

    Thanks

  2. Kaylex11 says:

    Thank you Stefan, I should have searched longer. :).

  3. Syed says:

    Hi Stefan,

    First of all, Thank You for all your blogs. It has helped me countless times!
    Do you recommend to keep the Windows Auto Update enabled, so that the SP Security Updates can get installed automatically?
    When I read the below link, I’m scared to keep this enabled
    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=523

    Thanks,
    Syed

    1. Hi Syed,
      Windows Update does not install SharePoint updates. Only if you enabled Microsoft Update it will install SharePoint fixes.
      On a production system I would never allow either Windows Update or Microsoft Update to automatically install fixes as hotfix installation should be done in a planned manner by first evaluation all fixes (SharePoint and non-SharePoint fixes) in an identical configured test environment to ensure that the fixes do not introduce any problems to the existing system.
      On a test environment or a developer environment it is a different story and depends on your recovery plans.
      Cheers,
      Stefan

  4. Jeff says:

    Is the issue with the list view issue from MS16-004 still present in the MS16-015? Currently, our DEV/ACPT environments are running at the Jan 2016 PU level with the hotfix installed (KB 3114508). However, due to various reasons, we held off in installing the Jan PU updates to PROD. We are not comfortable applying the Jan 2016 CU yet. Can that hotfix be installed after the Feb 2016 PUs? if not what would be your recommended approach?
    1st)Jan 2016 PUs
    2nd) Hotfix for list view
    3rd) Feb 2016 PUs?
    Thanks

    1. MS16-015 also resolves the list view issue.

      1. Jeff says:

        Got it, Thanks! Also, if we wanted to get our environments back at the same patch level…can KB3114508 be installed after MS16-015 or would we be looking at installing a future CU?

        1. yes, 3114508 can be installed after MS16-015

  5. Andrej says:

    Hello guys,
    Sorry for off topic, but I have one simple question about CU and LP update installation process:
    We have 4 servers SP2013 farm (2WFE + 2APP servers). Is it will be OK if I will run LP or CU installation (not psconfig ) on all farm servers in parallel or I should do it one by one?
    Thanks for help.

    1. Hi Andrej,
      yes – that is fine.
      Cheers,
      Stefan

      1. Andrej says:

        Hi Stefan,
        Thank you for quick response.

  6. TD says:

    For SP 2013 PU:

    We have AlwaysOn configured and want to know if WSS Logging database is to be removed before running psconfig?

    1. Piotr Siódmak says:

      Hi,
      Here’s an article on that matter from the support team: http://blogs.msdn.com/b/spses/archive/2016/02/10/sharepoint-2013-upgrading-usage-db-in-sharepoint-farm-with-sql-always-on-availability.aspx

      In short – yes, you have to remove WSS_Logging from Always On before running psconfig.

Skip to main content