The product group released the April 2024 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 2024 CU should be available at the following locations in a couple of hours:
- KB 5002583 – April 2024 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 5002524 from December 2023 CU.
The downloads for April 2024 CU are available through the following links:
- Download April 2024 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 5002524 from December 2023 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 2024 CU Build Numbers:
Language independent fix: 16.0.5443.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, the MS description states:
“This security update also contains a fix for the following nonsecurity issue in SharePoint Enterprise Server 2016. To fix this issue completely, you have to install KB 5002050 and KB 5002545 together with this update.
Fixes an issue in which OneNote cannot safely unload LibletAPI across multiple DLLs it owns. After you install this update, LibletAPI can be safely uninitialized in various OneNote DLLs by uninitializing in a locked, reference-counted code block.”
Does it mean we have to add those two other KBs to SharePoint even when there’s no MS Office installed in the servers?
Permalink
Hi Desmond, KB 5002050 and KB 5002545 need to be installed on the machines that have OneNote client installed – not on the SharePoint Server.
Cheers,
Stefan
Permalink
Phew! Thank you for the clarification!
Permalink
Hi Stefan,
we noticed the pervious SharePoint updates got disappeared from one of the WFE servers in the farm! any idea or anyone else has the same issue?
Permalink
Hi Frank,
it is technically impossible to uninstall a SharePoint update once it has been applied.
Only reasons a once installed fix might no longer be installed would be if the product itself was reinstalled (SharePoint Server) or a machine snapshot/backup has been restored.
Cheers,
Stefan