The product group released the April 2022 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for April 2022 CU should be available at the following locations in a couple of hours:
- KB 5002183 – April 2022 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002118 from January 2022 CU.
The downloads for April 2022 CU are available through the following links:
- Download April 2022 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002118 from January 2022 CU.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 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.
SharePoint 2016 April 2022 CU Build Numbers:
Language independent fix: 16.0.5305.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- 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
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hi Stefan,
You mentioned that there is no language dependent fix for April 2022 CU. Does that mean I need to download the language fix from January 2022 CU and install it? Or, is it already included in the April 2022 CU?
Thanks,
Raymund
Permalink
Hi Raymund,
you have to apply the one from january if it is not already installed.
Cheers,
Stefan
Permalink
Hi Stefan,
Thanks for your email. Could you send me the download link for the January 2022 CU language dependent fix? I just want to make sure that I am not downloading the wrong fix.
Regards,
Raymund
Permalink
It is listed in my blog post above.
Permalink
Hi Stefan,
I checked the Central Admin > Upgrade and Migration > Check product and patch installation status and under the
Microsoft SharePoint Foundation 2016 1036 Lang Pack – Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002118) 64 Bit Edition, Status – Installed
Microsoft SharePoint Server 2016 – Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002118) 64 Bit Edition, Status – Installed
Microsoft SharePoint Foundation 2016 Core – Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002183) 64 Bit Edition, Status – Installed
Does this mean that the January 2022 Update for SharePoint Server 2016 (language dependent) fix is already installed in our server? Anyway upon installation will also tell me if its already installed right?
Regards,
Raymund
Permalink
Hi Stefan,,
any issues and problems identified as of now ,
if proceed to install APR CU 2022
Permalink
Hi Arshad,
no but it is advised to verify the CU in a test environment and verify it against all business critical processes before applying in production as it is impossible to test every single use scenario.
Cheers,
Stefan
Permalink
Hi Stefan,
Thanks for Advise,
Sure we are following upgrade with SIT,UAT and PROD