July 2016 CU for SharePoint 2013 product family is available for download

The product group released the July 2016 Cumulative Update for the SharePoint 2013 product family.

For July 2016 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, July 2016 CU includes all fixes from July 2016 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 July 2016 CU should be available at the following locations in a couple of hours:

  • KB 3115290 - SharePoint Foundation 2013 July 2016 CU
  • KB 3115293 - SharePoint Server 2013 July 2016 CU
  • KB 3115291 - SharePoint Server 2013 with Project Server July 2016 CU
  • KB 3115289 - Office Web Apps Server 2013 July 2016 CU - This is also a security fix!

The Full Server Packages for July 2016 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 July 2016 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: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/

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 (14)

Cancel reply

  1. Jan Boznik says:

    Just as an FYI, after upgrading our on premise 2013 farm from June 2015 to July 2016 CU, the app pool hosting the Excel services stopped with an error: “Application pool ‘[app pool name]’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.”
    A couple of warnings before the error: “A process serving application pool ‘[app pool name]’ suffered a fatal communication error with the Windows Process Activation Service. The process id was ‘[id]’. The data field contains the error number.” Event ID was 5011.
    Came accross this article that describes the lack of permissions on a registry key: https://blogs.msdn.microsoft.com/spike/2015/02/12/sharepoint-2013-excel-services-w3wp-exe-fails-with-exception-code-0x80131623/
    We’ve added the WSS_WPG group to the key’s permissions and the app pool has been running uninterrupted for a whole day (previously it stopped a couple of minutes after being started).

  2. Marcel Havekes says:

    Hello Stefan,

    Something seems to have changed in the handling of the document-id prefix since I installed the july 2016 CU.
    Before I installed the CU, when I changed the document id prefix of a (new) site collection, I could run ‘the two’ timer jobs that are related to the document-id’s and the new prefix would be taken into account by SP in generating doc-id’s.
    Now, since I installed the july 2016 CU, when I change the doc-id prefix, and run the two timer jobs, the prefix is not immedialtely used by SP. I have to wait a hour or two, run the timer jobs, and it works; the new prefix is used by SP.
    “wait a hour or two” sounds like a dependancy on an other another timerjob, but which one?
    This change in behaviour is not shocking, but it can be a bit annoying when having automated site collection creation that ends with a change of the prefix followed by a “run now” of the two timerjobs.

    Further information:
    Before the july 2016 CU I had the januari 2016 CU installed.
    The described behaviour is confirmed on an other system

    1. Hi Marcel,
      I’m not aware of a change in this area.
      I would recommend to open a support ticket with Microsoft to get this analyzed.

  3. Len says:

    Within weeks of completing July 2016 upgrade, all of our web and app servers ate lusted again as Upgrade required. We have a support case open but are currently stumped. A colleague heard that this was a known issue, and ms was looking into it. Is this a known issue?

    1. Hi Len,
      I’m not aware of such an issue.

  4. Venkatesan Nadimuthu says:

    Hi Stefan,
    We were at SP 2013 SP1 -15.0.4569.1000
    Last Weekend We installed the July 2016 CU and ran SP Product Config Wizard. Everything went well and Configuration was successful.
    Today, We observed issues with Workflows.

    List->List Item->Workflows
    Sorry, something went wrong
    Method ‘StartWorkflowOnListItem’ in type ‘Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider’ from assembly ‘Microsoft.SharePoint.WorkflowServices, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have an implementation.
    I found a solution to install “Update 2880963 for SharePoint Server 2013: May 13, 2014”

    As I have the latest CU installed, Do I Still need to install the Update 2880963 to fix the issue.

    If yes, I may have to go with another maintenance window with VM snapshots and install the update and run PS config wizard. Am i right?

    1. Hi Venkatesan,
      SharePoint fixes are cumulative.
      Means July 2016 CU includes all previous fixes – including May 2014 CU.
      You cannot install an older CU on top of a newer.

      1. Venkatesan Nadimuthu says:

        Thanks Stefan for a quick response.

        I missed to explain the whole scenario here.
        In our SP2013 Farm, Automatic update was enabled and someone accidentally clicked on update and it has installed about 15 Security patches in one of the App Server.

        In order to have all the Servers in the Farm to be in Sync, We have installed those 15 Security updates in all the Servers in the Farm and ran PS config wizard.

        List of 15 Security Updates installed:

        Once it is installed, We get to see the Sharepoint Version at : 15.4841.1000 ( July 2016 CU)

        Do I have to install the KB3115293 such that issue that we are currently facing can be addressed?

        1. Hi Venkatesan,
          yes I would suggest to install the full July 2016 CU.

          1. Venkatesan Nadimuthu says:

            Hi Stefan,
            Thanks for your response. I thought the same!
            Instead of rolling out full July 2016 CU, Do you recommend as to go with next CU August 2016 CU(15.0.4849.1000) or September 2016 CU(15.0.4859.1000) as we have some of the updates already rolled out which are part of July 2016 CU
            Hopefully, this will address the Workflow issues too.

            Many thanks

          2. Hi Venkat,
            we do not blindly recommend specific CUs. You always have to valide a CU in a test environment before applying it on your production environment to verify if it has any negative side effects in your specific environment.

  5. Venkatesan Nadimuthu says:

    Hi Stefan,
    I agree. We will definitely install the CUs in DEV environment before going to PROD.
    Will post the comments after we roll out July or later CUs in our environment.
    Many thanks

    1. Venkatesan Nadimuthu says:

      Hi Stefan,
      I have installed July 2016 CU today in DEV environment and ran PS Config. Everything looks good. As we have rolled out the Security updates, They are showing as “Superseded”. Q: Is it safe to leave them as Superseded or any corrective action to be taken?
      I was going through your another article – https://blogs.technet.microsoft.com/stefan_gossner/2014/08/18/sharepoint-patching-demystified/ but Superseded Status was not discussed.

      1. Hi Venkat,
        that is perfectly normal. A newer fix has replaced those.

Skip to main content