The product group released the May 2024 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for May 2024 CU will be available at the following Location in a couple of hours:
- KB 5002596 – May 2024 Update for SharePoint Server 2019 (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 5002538 from April 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for May 2024 CU are available through the following links:
- Download May 2024 Update for SharePoint Server 2019 (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 5002538 from April 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
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 2019 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.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint 2019 May 2024 CU Build Number:
Language independent fix: 16.0.10410.20003
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching Best Practices
- 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 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
What to do when these “fixes” completely break our SharePoint 2019 sites? This update seems to have made the Modern Experience the default. Any document libraries or lists set to Classic Experience will not display. It is preventing access to the Settings of anything on the site as the icon for this is no longer displayed. All sites are displaying a white page (it is NOT blank) the content is there you just can’t see it. In the console it is saying a 401 Error for all CSS elements. But NOT on any document library or list that had been set to Modern Experience.
Rolling back this “update” does nothing.
How then do we fix all document libraries and lists to be set to Modern Experience when this update is preventing any access to anything to adjust / amend??
Permalink
Hi Sally,
I would suggest to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Permalink
Hi Sally, i’ve updated 3 completely separate environments, have not seen that issue .. yet.
Quick question, but did you deploy both the April language dependent patch and the May independent patch?
Permalink
I am seeing an interesting in change in behavior since installing the SharePoint 2019 May Updates.
We have a number of document libraries with different Content Types. Previously sing the New button at the top of Document Library would present a dropdown of all of the Content Types available so we could choose which one we wanted to use. Now, we don’t get a choice and it always defaults to the Document type.
On certain other document libraries we only have one Content Type specified and have made it the default type. However, clicking on the “New” button only results in the document content type being used, even though it isn’t specified.
I am not seeing errors in the browser console or in the ULS Logging.
Permalink
Hi Stuart,
I would recommend to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Permalink
Sorry to follow up, but I actually am finding in the ULS the following error:
VdbNavStruct::LoadScopeMap – Failed to insert ScopeId:{59993323-9CF1-4D69-9997-E6325C1B5440} into the scope map.
Which I guess may be related.