The product group released the June 2018 Cumulative Update for the SharePoint 2013 product family.
For June 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, June 2018 CU includes all fixes from June 2018 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 June 2018 CU should be available at the following locations in a couple of hours:
- KB 4022184 – SharePoint Foundation 2013 June 2018 CU
- KB 4022187 – SharePoint Server 2013 June 2018 CU
- KB 4022185 – Project Server 2013 June 2018 CU
- KB 4022183 – Office Web Apps Server 2013 in June 2018 CU – This is also a security update!
The Full Server Packages for June 2018 CU are available through the following links:
- Download SharePoint Foundation 2013 June 2018 CU
- Download SharePoint Server 2013 June 2018 CU
- Download Project Server 2013 June 2018 CU
- Download Office Web Apps Server 2013 June 2018 CU
Important: If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post:
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.
- 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: June 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
Hi Stefan ,
After June CU Applied for Sharepoint 2013 , i see Version 15.0.5023.1000 ? PSconfig Completed successfully Without errors
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
Again used the Same command with -Force switch same result .Ran Get-SPProduct -local Still Version Remain the Same , Have you or anyone noticed this yet ?
you mean as configuration database schema version? That is correct. There was no database schema change since April CU.
Just in case you are not aware of it: this version number is not valid indicator if a fix was applied.
See here for details:
Yes, Stefan looking both ways :Configuration database version:15.0.5023.1000 in Central Admin (under Servers in Farm) as well When I run
Powershell: (Get-SPFarm).BuildVersion , After going through your link I think I don’t need to worry about it. We have Multiple Farms Specially Search and SharePoint & When they are not in Same Version might cause some Crawl failure or other issues So Wanted to Confirm before rolling out to Prod