“Uber” packages for September 2015 CU for SharePoint 2013 have been released

The product group released the delayed September 2015 Cumulative Update for the SharePoint 2013 product family. No other CU is required to fully patch SharePoint when using these "Uber packages".

As this is a common question: Yes, September 2015 CU includes all fixes from September 2015 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 CU should be available at the following locations in a couple of hours:

  • KB 2975894 – SharePoint Foundation 2013 September 2015 CU
  • KB 2986213 – SharePoint Server 2013 September 2015 CU
  • KB 2986195 – SharePoint Server 2013 with Project Server September 2015 CU
  • KB 3085487 – Office Web Apps Server 2013 September 2015 CU – This is also a security fix!

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

Important: If your farm has been on a patch level lower than July 2015 CU: Unlike other CUs – after installing the September 2015 CU you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
If you don't run PSCONFIG after installing September 2015 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: http://blogs.technet.com/b/stefan_gossner/archive/2015/07/15/important-psconfig-is-mandatory-for-July-2015-cu-for-sharepoint-2013.aspx

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:


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


  1. So I've now executed the September 2015 CU for SharePoint 2013 3 times on a server with SP1 and May 2015 CU and it has failed each time. It appears to have the same issue as the August 2015 CU. I am now attempting to execute the August 2015 CU 3 times
    in a row to see if it installs.


  2. Hi Russell,
    it does not sound like the same issue. Because the issue in August only fails twice and succeeds on the third attempt.
    If it fails 3 times, then it sounds like a permanent problem.
    A failing installation can have various different reasons. Starting at disk space, corrupt package download, …
    I would recommend to enable MSI logging and verify the exact error that occurs.


  3. Hello Stefan, I'm always using your blog and Todd's list of regressions to identify updates I wanna install into my environment. For september he stats that it's not an uber package, but you say so. Am I correct in assuming, that he missed the later release
    of the uber package?


  4. Hi Andreas,
    sound as if he did not yet update the info on his site.


  5. Hi Stefan,

    There is something I may be missing, but I’m a bit confused.
    This article states that "Unlike other CUs – after installing the September 2015 CU you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm". Since CUs contain security fixes released on security bulletins since the previous
    CU, and according to your previous post "Why we recommend / require to run the Configuration Wizard also for Security fixes", shouldn’t this always be the case on a CU deployment (i.e.running the config wizard)?

    Thanks in advance


  6. Hi Marco,
    you are correct – in general you always need to run it. But in most cases you can wait a week or two before doing it. Here we have a breaking change – you need to do the installation and the PSCONFIG run in the same maintenance window – otherwise search crawl
    will be broken.


  7. Thanks for the clarification Stefan, I love when the pieces fall into place and make sense. Cheers.


  8. Does the Sept. CU fix the inability to attach files to list items after the Aug. CU? Thanks.


  9. No it does not. If no further problems are identified we plan to ship the fix for this in October CU


    1. Does the September CU fix search issue lot of users experienced “When running search it returns with an error “Field or property “TimeZoneId” does not exist.” ? Is running UI version of PSConfig is the only fix going forward?


      1. You can use either the UI version of PSCONFIG or run the command line version with the “-cmd applicationcontent -install” parameter to get the DLLs correctly installed.


  10. Hi,
    Maybe simple question.
    I have SP Foundation.
    Always when I try to install new CU before that I must uninstall my language pack becuase I see warning of: “necessary version of product did not find…”.
    I had 15.0.4727.1001 level and I wanted to install this Semptember CU(​15.0.4753.1000). I had Language pack of 15.0.4569.1506. 1st I uninstall language pack and install new CU. 2nd I install language pack.
    is it normall or I do something wrong?


    1. Hi Sylwester,
      based on your description you installed the RTM version of the language pack without installing SP1 for the language pack.
      You need to install SP1 not only for the base product but also for each installed language pack to properly upgrade your system to SP1.
      After installing SP1 for the language pack you should be able to install September 2015 CU.


      1. Stefan,
        regarding to your advice installation should be:?
        1st 15.0.4569.1506 as Sharepoint from http://www.microsoft.com/en-us/download/details.aspx?id=42039
        2nd 15.0.4569.1506 as Languagepack from http://www.microsoft.com/en-us/download/details.aspx?id=42256
        2nd 15.0.4571.1502 from kb2880551 as SP1 from http://www.microsoft.com/en-us/download/details.aspx?id=42548
        3rd 15.0.4753.1000(KB2975894) from http://www.microsoft.com/en-us/download/details.aspx?id=49097

        is it ok? thanks in advance!


        1. Hi Sylwester,
          there is no need for step 3 (kb2880551) as step 2 is the download for the language pack which already includes SP1.
          Step 4 should install fine after step 1 and step 2.


          1. Hi Stefan,
            thanks a lot. I will check this next installation becuase I have a few separate Foundation environments so I suppose I will have chance.
            Your blog is really really a large knowledge base!

  11. Stefan – I found that after installing September 2015 CU (skipped August 2015 CU – no server package) to an externally facing farm that users experienced the error, “The server was unable to save the form at this time. Please try again,” when attempting to modify list and document properties. I installed this CU to an internally facing farm without issue. The externally facing farm is encrypted. This problem is only experienced for the production web application; it’s not experienced for the Central Administration web application on that farm. I’m not 100% certain, but to the best of my knowledge, the only change that triggered this problem was installation of the September 2015 CU. Given that this CU introduced schema changes, I’m wondering if it s the cause, particularly given that I identified ULS log messages such as “The schema for field with this id is wrong or missing. field ‘{7d95d1f4-f5fd-4a70-90cd-b35abc9b5bc8}’.” associated with modifying list item fields and attempting to save the modifications. Curiously, I was able to resolve this by adding the Link (for lists) and Link to Document (for document libraries) content types. While adding these content types resolved the immediate problem, it’s not clear to me that this resolves the actual cause. Thoughts?


    1. I haven’t seen that issue and it does not occur on my test system. I would recommend to open a support case for this to get this analyzed in more details.


  12. Hi Stefan,
    as you states “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.” I just have to install one package to patch my whole farm, correct?

    In my farm I have Languagepacks for polish, turkish and german installed (with SP1). Additionally I have Project Server 2013 installed also. If I understand your scentense right, I have to install just this package –> http://support.microsoft.com/kb/2986195

    A Micorosft Premier Field engineer just sent me an email where he says that I have to install two packages. One for SharePoint Server 2013 and for Project Server 2013. For language packs he says there is nothing delivered yet.

    Thanks in advance Stefan
    Kind regards Andre


    1. Our CUs contain fixes for all language packs. So you never have to install separate fixes for separate language packs.
      And the Project Server CU contains the SharePoint server CU. So only one package is required.


    1. The issue you are referring to was fixed with October CU/PU. So you can either install the specific security fix which is part of October PU or October CU.


  13. I am facing problem in installing Project Server 2013 updates/hotfixes after SP1 (KB 2880553)
    I install May 2014 update/hotfix (KB 2880484) then dialogue box says:

    Hotfix for Microsoft Project Server 2013 (KB2880484) 64-Bit Edition.
    The installation of this package failed.

    When I run: (get-spfarm).buildversion it shows 15.0.4569.1000
    but in Central Administration “Manage Patch Status” it shows 15.0.4571.1502

    Also my SP1 setup file properties details says, this file is 15.0.4571.1502 then why SP Management Shell command says 15.0.4569.1000

    Now I am installing SharePoint 2013 CU September 2015, it shows the same error as above.

    Is there any pre-requisites of PS 2013 SP1?
    How do I proceed with this issue?


    1. Hi Noman,
      the error indicates a problem during the installation. Usually that is not a missing dependency. I would recommend to use MSI logging to identify the reason.
      If you need assistance with this you should open a support case with Microsoft.


  14. Hello Stefan, so for fully patch my fresh SharePoint 2013 with SP1 installation is it enough to install Uber September 2015 CU? Is this still the latest Uber update? Thanks a lot, Nicola


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.