September 2017 CU for SharePoint 2013 product family is available for download

The product group released the September 2017 Cumulative Update for the SharePoint 2013 product family.

For September 2017 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

As this is a common question: Yes, September 2017 CU includes all fixes from September 2017 PU.


Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.

The KB articles for September 2017 CU should be available at the following locations in a couple of hours:

  • KB 4011132 - SharePoint Foundation 2013 September 2017 CU
  • KB 4011116 - SharePoint Server 2013 September 2017 CU
  • KB 4011115 - SharePoint Server 2013 with Project Server September 2017 CU
  • KB 3213562 - Office Web Apps Server 2013 June 2017 CU – this is also a security update!

The Full Server Packages for September 2017 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don't run PSCONFIG after installing this CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work - so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.
See here for detail:

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.

Related Info:

Comments (20)

  1. Dean Gross says:

    If SharePoint Security Updates, such as KB 3213560, 4011113 and 4011117 are installed separately from the SP CU, is it necessary to run psconfigui?
    is it necessary to install the SP CU also?

    1. Hi Dean,
      all SharePoint fixes require PSConfig. No exceptions.
      The CU is only required if you need a specific fix from the CU.

      1. Dean Gross says:

        Thanks for the confirmation. That is what I thought.

  2. Uzma says:

    Very quick question – for a brand new SP VM, can I install SP1 then jump straight to this CU?

  3. Yamashita says:

    I would like to install SP1 and CU to withour SP1 farm. Is it necessary to run PSConfig before install CU? Is it enough to run PSConfig after continuous install SP1 and CU?

    1. It is sufficient to run it once at the very end.

      1. Yamashita says:

        Sounds good! Thank you for your confirmation.

  4. E Veal says:

    In reference to this page:

    Why does it state that PSConfig is required for SharePoint 2010/2016 but not for 2013?

    Thank you for your assistance. Your blog has proven to be the most helpful thing on the Internet (at least for me)!

    1. Seems to be a bug in this KB article.


  5. Giorgos A says:

    Hi Stefan,
    I installed the September 2017 CU (from your link above) in our farm, run the psconfig, all OK. Except, the Configuration db version number after the install is now 15.0.4957.1000. I checked Todd Klindt’s list of build numbers and this number does not exist anywhere. There is it referenced that for the September CU the build number should be 15.0.4963.1000. Which is the correct build number?
    Many thanks

  6. Mohanghimire says:

    Hi Stefan,
    When checking September monthly security update for SharePoint 2013 we have three updates :
    Are we supposed to install all three ? my concern is if we install server updates we don’t necessarily need to update Foundation since that already included in server ?

    1. Hi Mohanghimire,
      the SharePoint server security fixes do not include the SharePoint foundation fixes. You need to install all of them.
      For the CUs we have server or “uber” packages – which I reference in this article. The “Uber” packages for SharePoint Server include the SharePoint Foundation fixes.

      1. Mohanghimire says:

        Thanks Stefan for making this point clear. we also have SharePoint 2016 environment , every monthly patch in SharePoint is CU (This basically implies if I update my environment with October Patch , it includes everything before October ? don’t need to go back and apply any earlier patch, correct ?)

          1. Mohanghimire says:

            Thanks for Confirmation , I used to see SharePoint 2013 CU Also called Uber/server package, However I didn’t see 2016 CU never mentioned Uber/Server update So were confused , Thanks

          2. There are no uber or server packages for SP2016.
            The reason that we shipped the uber packages is that before SP2016 we had 30+ packages that could be patched independently.
            With SP2016 there are only two.


  7. Hi Stefan,
    are any known issues reported to Microsoft support connected to Sept 17 CU (SPS2013)?
    Todd has reported nothing yet:
    We plan to install this on 2 farms used by 3000 customers.
    BR Daniel

    1. Hi Daniel,
      no known regressions introduced in September 2017 CU. But that info is only relevant if you are coming from August 2017 CU. If you are currently on an older patch level, also all regressions in other CUs between your current CU level and September CU would be relevant which have not been fixed till Sept CU.
      On the other hand most regressions only affect certain configurations or features – so they only affect a small number of customers. Thats one of the reasons why we highly recommend to evaluate each CU first in a test environment before applying to production to see if your specific environment is impacted or not.

Skip to main content