The product group released the March 2023 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 March 2023 CU will be available at the following Location in a couple of hours:
- KB 5002358 – March 2023 Update for SharePoint Server 2019 (language independent)
This is also a security update!
- KB 5002357 – March 2023 Update for SharePoint Server 2019 (language dependent)
The downloads for March 2023 CU are available through the following links:
- Download March 2023 Update for SharePoint Server 2019 (language independent)
This is also a security update!
- Download March 2023 Update for SharePoint Server 2019 (language dependent)
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 March 2023 CU Build Number:
Language independent fix: 16.0.10396.20000
Language dependent fix: 16.0.10396.20000
- 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.
I have noticed after applying the March 2023 Updates (and I was aware that a fix was in place for the People Picker in the Modern UI not resolving with AD DS) that when the people picker field is used it is displaying “This User Was No Longer Existing, Maybe Deleted” however it is not having an impact in saving. I was wondering if Microsoft is aware and if this is a potential issue or not?
Thanks in advance!
are the additional steps from the february updates also necessary? We have not installed this update yet?
Thanks for your great work!
which additional steps did you mean?
Could it be that the march cu had impacts on the last modified date of lists and libraries?
I have a customer where the dates changed but all files or items inside lists and libraries are way older.
We have a SharePoint OnPremise 2019 Farm, updated from 2016 months ago. Now with the march CU I noticed a new tab in the new created document libraries, „PerformancePoint“. I am sure it was not there with the 2016. Is there a way to disable/hide it?
sounds to me as if you created a “PerformancePoint” service application in your farm.
If you don’t need it I would recommend to remove it.
See here for more details:
Thanx for the reply.
I checked the link you posted and at the Service Application Associations in my Central Administration unfortunately I couldn’t find the PerformancePoint Service. It does not show up under the ServiceApplications neither.
Rene’s comment got me looking at our farm and I noticed an anomaly with the last modified date on the document sets after applying the Mar 2023 CU. Almost all of the last modifed dates on the document sets were updated during a 5 day period by the System Account. None of the documents themselves were affected.
Any ideas what might have caused this?
Always such great info on your site – thank you!
I think this was always like this.
Here is a quite old discussion which also reached the product group at that time and they concluded that they are not changing the behavior:
Thank you for the quick response – I did some further digging and it was coincidental with the CU patching. It is the Content Type Hub publishing that causes the update to the Document Set modified date and modified by.