June 2022 CU for SharePoint Server 2019 is available for download

The product group released the June 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 June 2022 CU will be available at the following Location in a couple of hours:

  • KB 5002212 – June 2022 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • KB 5002211 – June 2022 Update for SharePoint Server 2019 (language dependent)

The downloads for June 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 June 2022 CU Build Number:

Language independent fix: 16.0.10387.20008
Language dependent fix: 16.0.10387.20008

Related Links:


  1. Hello Stefan,

    Does the June 2022 CU for SharePoint Server 2019 is taking care of the “Trending Issue: left navigation missing after applying May 2022 CU for SharePoint Server 2019”, based on your update only we are planning to update SP2019 Jun2 2022 CU to our environment. Please confirm.


    1. Hi Prabhu,
      not automatically. You need to apply the same workaround as with May CU.
      Either clearing the browser cache or using a side by side token.



      1. Hi Stefan
        Just to be clear on this: the issues is caused by a mix of old & new of JS libraries from April CU to May CU, correct? Or is it a perpetual issue?
        So, if we are going from April to June it will still exist.
        But, what about going from May (where it has already surfaced and libraries are removed from users’ cache) to June? Still there?

        Thanks for your patience


        1. Hi Giorgos,
          the same issue will happen when going from April to June.


Leave a Reply

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