The product group released the January 2016 Cumulative Update for the SharePoint 2013 product family.
For January 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, January 2016 CU includes all fixes from January 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 December CU should be available at the following locations in a couple of hours:
- KB 3114492 - SharePoint Foundation 2013 January 2016 CU
- KB 3114497 - SharePoint Server 2013 January 2016 CU
- KB 3114493 - SharePoint Server 2013 with Project Server January 2016 CU
- there is no January 2016 CU for Office Web Apps Server 2013
The Full Server Packages for January 2016 CU are available through the following links:
- Download SharePoint Foundation 2013 January 2016 CU
- Download SharePoint Server 2013 January 2016 CU
- Download Project Server 2013 January 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 January 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/
This CU fixes the issue with outbound query federation which was introduced with October, November and December 2015 CU.
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.
- Common Question: What is the difference between a PU, a CU and a COD?
- SharePoint Patching demystified
- Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Support for SharePoint 2013 RTM has ended
- SP1 for SharePoint 2013
- January 2016 Office Update Release
- CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Update Center for Microsoft Office, Office Servers, and Related Products
- SQL Server 2014 and SharePoint Server 2013