September 2015 CU for SharePoint 2013 is available for download

[Update: this article has been superseeded by the following: "Uber" packages for September 2015 CU for SharePoint 2013 have been released]

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


Be aware that all Update 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).

September 2015 CU has been released without so called "Server" or "Uber" packages. Instead only fix packages for individual components of SharePoint have been released.

That means: if you are not in an urgent need for a fix included in September 2015 CU you should consider waiting for a CU release that includes "Server" or "Uber" packages.

As September 2015 CU does not include Uber packages you need to install August 2015 CU before installing the below listed September 2015 CU fixes to guarantee that your system is on the latest patch level.
So it is highly recommended to install August 2015 CU before installing September 2015 CU!

See SharePoint Patching Demystified for details.

This CU does NOT(!) include all SharePoint 2013 fixes previously released! It is recommended to install August 2015 CU before installing September 2015 CU.

The CU does not include SP1! You have to install SP1 before installing this CU.

The KB articles for September 2015 CU relevant for the different products are available at the following locations:

To simplify the installation I have collected the required September 2015 CU fixes for each product:

After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.


Related Info:


p style=”padding:0;margin:0;”>


  1. Ya tenemos disponibles las actualizaciones acumuladas tanto de SharePoint 2010 como de SharePoint 2013


  2. This month we cannot yet provide you the Full-Server Packages and before I use the same content with


  3. Buenas, Ya podemos descargarnos la Actualización Pública para Project 2013 y Project Server 2013 , correspondiente


  4. Hi Brad,
    the product group does a code freeze for a CU usually around one month before the CU is released. So assuming that the next CU already contains a fix for an issue introduced in the previous CU is very unlikely.
    The issue you mentioned above is currently scheduled for October CU but that can change if problems show up during testing.
    I would always recommend to open a support case if you are waiting for a fix to ensure that you get notified when running into an issue as only issues reported through a support case will be fixed. The other benefit is that you will get notified if a fix is


  5. hi Stefan,
    could you tell more about the "code freeze"? Does that mean that if I report a bug which needs a really small change (e.g. a typo in a hardcoded /_layouts/ path), I would still need to wait months for the change to be applied and then some more for it to be


  6. Hi Piotr,
    not exactly. The code for the CU is frozen – means a fork is done for the code used in the CU. Future fixes can be checked in at the same time into the non forked code tree. The fork for the CU is used to test and stabilize the code.
    Later when the next CU is about the be created the next fork happens using the meanwhile checked in changes to the other fork of the tree.


  7. What to do when we missed installing August CU before September CU?


  8. Hi Jessica,
    just install it afterwards. Only those parts which are not updated in September CU will be updated with August CU.


    1. Hi Stefan,
      That’s not correct, when you install a CU you could not longer install previous CUs, it tells that the patch is not required.
      Anyway I wonder why there is no check since SP1, june and august CUs are required that SharePoint let’s you setup September CU anyway, that’s bad!
      How could you install August CU then ? any special instructions ?


      1. Hi Chris,
        sorry – but your statement is wrong.
        If you are installing September CU from above (and not the Uber package) you can install August CU Uber packages on top.
        If you installed the September CU Uber packages from my later post you cannot install August CU on top – but that is expected as all fixes from August CU are included in the September CU Uber packages.


  9. Hi, it's me again 🙂

    Can you confirm these are the same fixes that are pushed via Windows Update?

    Customer IT did install these, and now Publishing Pages refuse to open, and display generic "unexpected error has occurred". Not yet 100% sure what's the root cause, but just one more example why I really dislike ANY SharePoint updates being pushed via WU.

    It might get sorted out with Config Wizard, or it might be some issue with September 2015 CU having issues with the baseline CU that was on the system, requiring August 2015 CU to be installed, which is quite a major task.

    Windows Server admins just don't understand the implications of installing security updates from WU, i.e., hours/days of downtime when config wizard or additional surprise CU install is needed to make things work again.

    Sure, it makes me want to move all customers to SharePoint Online, which may be the ultimate business goal here. 🙁


  10. Hi Jussi,
    some of these fixes are pushed through windows update but not all.
    I don’t think that the issue you describe is related to September CU as that would have affected a large amount of customers and we would have received a significant amount of support cases already.
    If the issue cannot be resolved I would recommend to open a support case for this.


  11. Hi Stefan, where can I found a link to download sharepoint 2013 CU September 2015?


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.