The product group released the October 2018 Cumulative Update for the SharePoint 2013 product family.
For October 2018 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, October 2018 CU includes all fixes from October 2018 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 October 2018 CU should be available at the following locations in a couple of hours:
- KB 4461455 – SharePoint Foundation 2013 October 2018 CU
- KB 4461458 – SharePoint Server 2013 October 2018 CU
- KB 4461456 – Project Server 2013 October 2018 CU
- There was no fix released for Office Web Apps Server 2013 in October 2018 CU
The Full Server Packages for October 2018 CU are available through the following links:
- Download SharePoint Foundation 2013 October 2018 CU
- Download SharePoint Server 2013 October 2018 CU
- Download Project Server 2013 October 2018 CU
- There was no fix released for Office Web Apps Server 2013 in October 2018 CU
Important: If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post:
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 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.
Related Info:
- Technet: Updated Product Servicing Policy for SharePoint 2013
- 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: October 2018 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
Permalink
Hi Stefan,
got a new error when doing the cumulative. During the DB upgrade i get this.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional
exception information: The server principal “” is not able to
access the database “Maintenance” under the current security context.
do you know why the Service Account needs access to the Maintenance DB?
Permalink
Server Principal in this case is the Farm service account. What level of access does it need to Maintenance?
Permalink
Hi Stefan,
I installed this update using the links provided here and through the Microsoft KB Articles after I hadn’t run any updates in a few months, but the Build number in Central Admin and via Get-Farm show that it was updated to 15.0.5067.1000 (September 2018 CU) instead of 15.0.5075.1000. I triple checked and tried re-downloading and re-running the the CU and it stated “Nothing to Upgrade”.
Any thoughts on why the Build Number might not be getting updated?
Permalink
Hi JWright,
the places you looked for a Version number are wrong. See here for details:
https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
The only place where you can see the correct build number is in the patch status page:
Cheers,
Stefan