The product group released the March 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 March 2024 CU should be available at the following locations in a couple of hours:
- KB 5002559 – March 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 March 2024 CU are available through the following links:
- Download March 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 March 2024 CU Build Numbers:
Language independent fix: 16.0.5439.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
same error exists in new CU update as existed in January.
500 Internal Server error
there is a problem with the resource you are looking for, and it cannot be displayed.
do you think the script to fix environment suggested in January is required once again to fix this?
Permalink
@
gerard mcgrath , what is the error you are getting in SP2016 After the march CU 2024?. Could you please share with more details because we would be planning it to install on our servers shortly?..If incase any impact with march2024 cu will hold it.
Permalink
Server Error
500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
same error as I got when I installed the January CU update
i ended up restoring from backup last time,
I might try the script shared by Stefan this time to fix as I only applied the patch in UAT.
Permalink
Hi Kevin,
if this is the 500.19 due to exceeded web.config size: a fix for this issue is not included in March CU.
The script to remove the duplicates is still the best option available.
Cheers,
Stefan
Permalink
Hi Stafan,
I can confirm i ran the script and this fixed the issue for me in my environment..
All good now in my UAT environment.
Would you recommend waiting to see if a fix will be deployed for 500.19 due to exceeded web.config size in a later update for a production environment or go with update and then run the same ps1 ?
Permalink
Hi Kevin,
as this CU includes a security fix I would recommend to apply the fix and run the script to cleanup rather than waiting for a later CU.
Cheers,
Stefan