The product group released the August 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 August 2022 CU should be available at the following locations in a couple of hours:
- KB 5002249 – August 2022 Update for SharePoint Server 2016 (language independent)
- 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 August 2022 CU are available through the following links:
- Download August 2022 Update for SharePoint Server 2016 (language independent)
- 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 August 2022 CU Build Numbers:
Language independent fix: 16.0.5356.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, I’ve noticed that there hasn’t been a language dependent fix for a while. Is there any reason why this is the case?
Permalink
Hi Chris,
SharePoint Server 2016 is in extended support where only security related fixes are implemented.
The reason that no language dependent fix was released is that no security fixes were required for the language dependent parts.
Cheers,
Stefan
Permalink
Hi Stefan,
I already patched the DEV and QA servers with the July 2022 CU but not the Production servers because we are trying to implement a fail over system to restore production farms in case of failure. Now, the August 2022 CU is available. Will there be an issue if I proceeded with patching the DEV and QA servers with the August 2022 CU then production even if we have not patched the production servers with the July 2022 CU? Can you also send me a link on how to back up server farms and configurations and restore in case some issues regardless of the nature of event and its cause.
Thanks,