The product group released the January 2022 Cumulative Update for the SharePoint 2013 product family.
For January 2022 CU we have full server packages (also known as Uber packages) for all products. No other CU is required to fully patch SharePoint.
As this is a common question: Yes, January 2022 CU includes all fixes from January 2022 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 January 2022 CU should be available at the following locations in a couple of hours:
- KB 5002123 – SharePoint Foundation 2013 January 2022 CU
- KB 5002126 – SharePoint Server 2013 January 2022 CU
- KB 5002125 – Project Server 2013 January 2022 CU
- KB 5002122 – Office Web Apps Server 2013 January 2022 CU
The Full Server Packages for January 2022 CU are available through the following links:
- Download SharePoint Foundation 2013 January 2022 CU
- Download SharePoint Server 2013 January 2022 CU
- Download Project Server 2013 January 2022 CU
- Download Office Web Apps Server 2013 January 2022 CU
After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct Options.
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.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
- Technet: Updated Product Servicing Policy for SharePoint 2013
- Blog: SharePoint Patching Best Practices
- 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
- 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
Hello Stefan, after installing KB5002126 CU in our SharePoint 2013 DEV environment, we noticed that the version number is15.0.5411.1000 and not the expected 15.0.5415.1000. Is this an issue of concern? Thank you.
Hi Steve, this is normal and expected. It looks as if you looked at either the database schema version or the farm build number. Both of these are not expected to show the number in the KB article and cannot be used to identify if a patch is correctly installed.
Please have a look in the following article which explains in detail what you are seeing and how to correctly identify if a patch is installed:
Hi Steve, We are also seeing the same version number ‘15.0.5411.1000’ after installing the ‘SharePoint Server 2013 January 2022 CU’. We have tried this in 4 of our SharePoint 2013 farms which earlier were on December version ‘15.0.5399.1000’.
Is this just a bug with the number or is there a different CU for Jan22 which is missing. Please update at the earliest as we are due to install these patches on our PRODUCTION farms in next 3 days.
Hi HImanshu, please see my response above to Steve.
we had a strange behavior with our SharePoint 2013 Farms.
The Farm reside in one Domain and the users in another. Our servers get the 2022 Januar Windows Updates (WinServer 2012 r2)
2022-01 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5009595)
2022-01 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5009624)
These Windows Januar updates has several issues, a new update was released from MS but it does not solve all the problems.
Some of the issues -our biggest concern is regarding the 2nd Article LDAP Queries in cross domain scenarios when NTLM used.
After we had this 2 updates Installed on our SharePoint 2013 Farm we could not find via people picker the users from the other domains. We had to remove these 2 updates to get this working again.
After some investigation we found following:
The cross domain NTLM Auth works if we are using encryption
$AuthType = [System.DirectoryServices.AuthenticationTypes]::Encryption
$DirEntry = New-Object System.DirectoryServices.DirectoryEntry($Connect,$Accountname,$AccountPassword,$AuthType)
We understand that this is a more secure way to do cross domain LDAP queries.
My question is this “Scenario” and secure LDAP queries in People Picker in some of the CU updates for SharePoint 2013 Products taken care of?
Or do you think the next Montly Update for Windows Servers will change something regarding the cross Domain LDAPs when using NTLM?
Kind regards, Gabor
sorry I don’t have information for this.
Also be aware that SP2013 is in extended support – so fixes for non-security issues will most likely not be released or worked on.
I am trying to install the updates SharePoint 2013 and it fails after Extracting files. Error message The instllation of this package failed. It is not our first patching, SP1 should be already installed. I have all my 3 files in the same folder. Can you please advise?
if you need assistance with this I would recommend to open a support ticket with Microsoft.
Should I be concerned with the issue that this patch has. The issue is below:
Known issues in this update
Most users cannot access Web.config files in Microsoft SharePoint Server. The affected group of users does not include farm administrators, local administrators, or members who are managed by the system. For more information, see Users cannot access Web.config files in SharePoint Server (KB5010126).
I want to double check of that before I go ahead and install the patch on my production environment.
Thank you Stefan
this is a security update which improves the security of your SharePoint servers by removing permissions from the web.config file.
If you have business processes which allows non-administrators to access these files – that will no longer be possible and you would have to evaluate whether to apply the workaround.