The product group released the August 2016 Cumulative Update for the SharePoint 2013 product family.
For August 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, August 2016 CU includes all fixes from August 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 August 2016 CU should be available at the following locations in a couple of hours:
- KB 3115447 – SharePoint Foundation 2013 August 2016 CU
- KB 3115450 – SharePoint Server 2013 August 2016 CU
- KB 3115448 – SharePoint Server 2013 with Project Server August 2016 CU
- KB 3115446 – Office Web Apps Server 2013 August 2016 CU
The Full Server Packages for August 2016 CU are available through the following links:
- Download SharePoint Foundation 2013 August 2016 CU
- Download SharePoint Server 2013 August 2016 CU
- Download Project Server 2013 August 2016 CU
- Download Office Web Apps Server 2013 August 2016 CU
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.
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Blog: Support for SharePoint 2013 RTM has ended
- Blog: SP1 for SharePoint 2013
- Blog: August 2016 Office Update Release
- Technet: CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- Technet: Install a software update for SharePoint 2013
- Blog: How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SQL Server 2014 and SharePoint Server 2013
Great information as usual! Thanks for putting the effort into this blog.
Is there not a SP2010 Aug CU this month, or is it just delayed?
SharePoint 2010 is in extended support since nearly a year now which means that only security fixes will be created.
In August we did not have any security fixes for SharePoint 2010 which is the reason that no CU was released.
Thanks, figured but needed to dbl check.
Sorry if I’m missing something here but we have SharePoint Server 2013 SP1 installed and I have downloaded the cumulative update but it only has the cab file which is about 1.4GB. Isn’t there meant to be an accompanying exe file?
the fix consists of 3 files: 1 exe and 2 cab files:
ubersrv_1.cab – 1.4 GB
ubersrv_2.cab – 304.9 MB
ubersrv2013-kb3115450-fullfile-x64-glb.exe – 1.4 GB
You need to select all of them in the download page and store them in the same directory.
Thanks for the prompt reply. Yes I just saw that. I had a browser issue so it didn’t show me all of the files, it just downloaded the first cab file. All sorted now. Thanks again.
What’s about Language Packs? Which Language should I install? Our System is english with german language pack.
it does not matter which language you select in the dropdown – the package will always be the same.
There is only a single patch and this contains fixes for all languages.
Hi Stefan, I didnt see any post from you on July 2016 CU for SharePoint Server 2013, are there any known issues to be aware of ?
here is the blog post about July 2016 CU for SP 2013:
No new known issues till now.
Since installing the SharePoint 2013 August 2016 CU I’ve noticed two things. One, I can no longer hide/show pages in the Navigation Settings. Two, all Managed Metadata Site Columns are no longer connected to the MM Service Application Term set. Has anyone else noticed similar issues? Thank you.
it seems you were upgrading from an older CU level.
The navigation issue was introduced with June CU – a fix is currently planned to be released for October CU.
The MMS issue is not (yet) a known issue. I would recommend to open a support ticket with Microsoft to get this issue analyzed.
I am unable to hide/show pages & subsites from the navigation in SharePoint Server 2013 (15.0.4849.1000 August 2016 CU), also looking forward to update in October.
Thank you for the post. We’re experiencing the same issue here. Unable to hide / show elements in the navigation. Looking forward to the bug fix this month.
I believe there is something wrong with this update. When updating our SharePoint 2013 Search farms, the update failed with following error message:
“There is already an object named ‘domain\someADgroup’ in the database. CREATE SCHEMA failed due to previous errors.”
To fix this, I need to remove manually all the Schema’s, with the name from the error message, from the Search, CrawlStore, AnalyticsReporting and Linkstore databases.
When running the psconfig command again, the update is successfully.
This problem is related to the search db’s and SQL schema’s based on AD groups.
I did a test on two search farm’s in our test environment and always with the same error message. When updating another farm without a search service application configured, everything goes fine.
I haven’t seen this error before – looks to be specific to your environment.
I would recommend to open a support ticket to get this analyzed as manual changes in SharePoint DBs lead to an unsupported environment.
I did the same in our quality environment with the same error message.
Meanwhile I found the culprit. The problem occurs because we have assigned a global AD security group as administrator for the search service application.
My workaround without touching the database:
Remove this group temporarily in “Central Administration->Service Applications->Search Service Application->Administrators”.
Run Configuration wizard.
Add the global security AD group back to the Search Service Application administrators.
Sorry, I posted my workaround too early.
Adding the AD group to the Search Service Application administrators after running the configuration wizard give me the same error message. I Always need to go directly into the search db’s and delete the schema’s.
I’m going to open a support ticket.
as always, thanks for your blog. very helpful.
We are experiencing an issue after applying the August 2016 CU. The CU that had been applied prior to this was Nov 2015.
It seems that our search relevance is not working like it had in the past. It was “weighted” on a part number column so when a user searched for part number “400” it returned that first. After the CU, it seems to be returning based on how often “400” shows up in the descriptions or other metadata.
Do you think any of the CU’s after Nov 2015 could have contributed to this behavior? Has there been any search related problems in the previous CU’s
Seems to be a bug with this fix in Site Look and Feel / Navigation. Can no longer Show/Hide navigation items. System Admin; Site Collection Admin; Site Owners. Go through the steps, it says it’s hidden or show but does not work.
Has this resolved the following issue for anyone: Unable to open SharePoint documents in local client (rich client) from Chrome due to NPAPI plug-in missing
This update was supposed to address it but I’m still having the issue after applying it.
we applied the AUG 2016 CU (last one was Nov 15 CU) and noticed an issue with listdata.svc. in the past, when a column name started with numeric (ex: 480VKAICRating), the service prepended a c_ to the name. After the CU, it prepends C_. This broke one of our Windows Services that was using this as web reference. We have confirmed this in our Stage and UAT enviroments. We have not applied the CU to production yet.
Has anybody else reported this? is this the new standard? we don’t want to change our services and then find out that another CU changes it back.
this has not been reported before. I would suggest to open a support case with Microsoft to get this analyzed in more Detail.
Hello, in production environment this patch update broke mirroring for the usage_SA. I had to call Microsoft for support to go through diagnostics and identify this issue.
Have you been privy to any information regarding the Aug2016 CU changing the Require Check Out setting on a library?
have not heard about such an issue.