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


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

For July 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, July 2017 CU includes all fixes from July 2017 PU.

ATTENTION:

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 2017 CU should be available at the following locations in a couple of hours:

  • KB 3213563 - SharePoint Foundation 2013 July 2017 CU
  • KB 3213569 - SharePoint Server 2013 July 2017 CU
  • KB 3213566 - SharePoint Server 2013 with Project Server July 2017 CU
  • There was no fix released for Office Web Apps Server 2013 in July 2017

The Full Server Packages for July 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: 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 (6)

  1. Stephan Bren says:

    Stefan – what is the best account to use for running PSCONFIG? Is it the SharePoint Setup User Administrator account? Some admins I have talked to state that they use their own administration account (a standard domain account) that is a member of the local admin group on all farm servers and a member of the Farm Administrators group in Central Admin. Others I have talked to state that they use the farm service account – the one running the SharePoint Timer service. My understanding has been that the best account to use is the one that was used to perform the original installation and configuration of SharePoint – the Setup User Administrator account. This seems to be the account indicated by the TechNet posting, “Account permissions and security settings in SharePoint 2013”. What do you recommend? And what references are there that you know of that specifically address this? Thanks.

    1. Hi Stephan,
      I would stick with the recommendation on Technet.
      Cheers,
      Stefan

    2. Piotr Siódmak says:

      Do not use any of the service accounts – https://support.microsoft.com/en-us/help/3114011/800703fa-illegal-operation-attempted-on-a-registry-key-that-has-been
      “This problem typically occurs after an administrator uses a service account to log on to the server for an interactive session, and then logs off. For example, an administrator may log on to a Web Front End (WFE) server by using the farm account, and then log off. This activity forces the registry keys to be unloaded in the profile of that account. This condition makes the keys unavailable for future use.”

  2. anthony says:

    Hi Stefan, I have a couple of issues if you could advise on, that would be great. Are you aware of any issue running the July 2017 CU with Search Server. It now shows Paused for External request. I have tried to resume it via PS but still no joy., I have tried re-indexing as well. The CU installed with no issues and Config Wizard went through. Although on step 9 it reach 100% but failed due to a solution installed on the farm. Database shows No Action Required but shows failed in upgrade status. I removed solution and ran config again. it went through successfully but still shows Failed in upgrade status, with 1 error. when I search in Upgrade log I cant see any Error, what are your thoughts please.

    Thanks
    Anthony

    1. Hi Anthony,
      hard to say from just the information above.
      I would recommend to open a support ticket with Microsoft to get this investigated in more detail.
      Cheers,
      Stefan

      1. anthony says:

        yeah I think it looks that way. thanks for taking the time to reply. regards Anthony

Skip to main content