May 2022 CU for SharePoint Server 2019 is available for download

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:

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:

14 Comments


  1. Hello Stefan,

    So is this CU for SharePoint 2019 a Public Update for the Month of May? Thanks,

    Reply

  2. Thank you for all the excellent work you do

    Reply

  3. 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

    Reply

    1. 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

      Reply

  4. 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).

    Reply

    1. 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

      Reply

      1. 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…

        Reply

        1. 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

          Reply

  5. 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!

    Reply

    1. 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

      Reply

      1. 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

        Reply

          1. 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.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.