The product group released the May 2022 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 2022 CU will be available at the following Location in a couple of hours:
- KB 5002207 – May 2022 Update for SharePoint Server 2019 (language independent)
This is also a security update! - KB 5002206 – May 2022 Update for SharePoint Server 2019 (language dependent)
The downloads for May 2022 CU are available through the following links:
- Download May 2022 Update for SharePoint Server 2019 (language independent)
This is also a security update! - Download May 2022 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 May 2022 CU Build Number:
Language independent fix: 16.0.10386.20011
Language dependent fix: 16.0.10386.20015
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
Hello Stefan,
So is this CU for SharePoint 2019 a Public Update for the Month of May? Thanks,
Permalink
yes
Permalink
Thank you for all the excellent work you do
Permalink
Hi Stefan,
Two components: sts and wssloc have different build numbers. Is this OK? Which build number will SharePoint config database display after I deploy these?
Language independent fix: 16.0.10386.20011
Language dependent fix: 16.0.10385.20015
Permalink
Of course that is ok. We never guarantee that they will have the same build number.
The config DB schema version should have the version 16.0.10386.20011
Cheers,
Stefan
Permalink
Hello Stefan,
after installation of these updates I have noticed on our test farm that language dependent fix has slightly different version number. Page “Manage Patch Status” (CA / Check product and patch installation status) is showing 16.0.10386.20015 for both LP we use (1051, 1033).
Permalink
Hi eLKey,
that is correct. If you check my blog post above it outlines the two different versions for the language dependent and language indepedent fix.
Cheers,
Stefan
Permalink
I am aware of possibility to have different version numbers for sts/wssloc, but I tried to note that your article is stating that language dependent fix has number 16.0.10385.20015 instead of 16.0.10386.20015…
Permalink
Ah – sorry. My bad.
I did not notice the difference in the 3rd part.
You are right – I mistyped that part it in my blog post. Its corrected now.
Cheers,
Stefan
Permalink
We just applied the May 2022 update and in the Modern UI document library we have been getting sorry we cannot open (excel file URL) in the client. Has this been reported by anyone else? Thanks in advance!
Permalink
Hi Daniel,
this has been reported before if the SharePoint config wizard was not run after installing the updates.
In this case the new files are not moved to the _app_bin directory of the different web applications.
Please ensure that the SharePoint config wizard was executed on all servers in the farm.
Cheers,
Stefan
Permalink
Hi Stefan, Thank you again for your response. We did run the PSConfig Command after installing the updates and I just ran the PS Config command again for farm and the issue is still remaining. Should I have done this through the UI instead? This is the first time this issue has happened for us in our SP19 farm we’ve had for over a year. Thank you again for your help. – Daniel
Permalink
Hi Daniel,
the command line version is fine if you specified the correct parameters as outlined here:
https://blog.stefan-gossner.com/2015/08/20/why-i-prefer-psconfigui-exe-over-psconfig-exe/
Cheers,
Stefan
Permalink
Hi Stefan, Thank you again for your reply. We always use this version: “PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install” The issue is sporadic as sometimes the document will open and sometimes it will throw the “Sorry, we cannot open (URL)” in Word or Excel.
Permalink
Hi, we have the problem that the edit button is missing on modern page after install patch KB5002207, KB5002206.
In addition we have the problem under Gearwheel (I hope you know what I mean), here we can’t go on site- permissions, site-information or change the look.
Permalink
Many users reported losing the navigation menu on the left in all sites after the May 2022 CU.
Apparently, it is a caching issue and it is resolved by clearing browser cache (Shift+Control+Reload page).
Permalink
Hi GA,
that is correct. The easiest way to prevent this is by using side-by-side-patching which guarantees that updated javascript files get a new URL:
https://blog.stefan-gossner.com/2017/01/10/sharepoint-server-2016-patching-using-side-by-side-functionality-explained/
Cheers,
Stefan
Permalink
Hi Stefan
Is this something that you expect it will be fixed in the next CU or it is something that we should be doing as part of our routine from now on?
(even if we enable this, it is my understanding that after a new patch, we should also update the the side-by-side token)
Permalink
Hi GA,
it should be fixed in a couple of months.
A release date cannot be shared at this time.
And yes: the side-by-side token needs to be updated with each patch install to ensure that the latest javascript files will be served.
Cheers,
Stefan
Permalink
Recently we have install patch KB5002207, KB5002206, but afterwards, all modern pages are missing edit button and left navigation
Permalink
Hi S1nce,
if you flush the browser cache or do an CTRL-F5 the problem should be solved.
To avoid it from server-side you should use a side-by-side token to force loading a specific version of the javascript files:
https://blog.stefan-gossner.com/2017/01/10/sharepoint-server-2016-patching-using-side-by-side-functionality-explained/
Cheers,
Stefan
Permalink
great, it works