August 2022 CU for SharePoint Server 2019 is available for download

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

  • KB 5002246 – August 2022 Update for SharePoint Server 2019 (language independent)
  • KB 5002245 – August 2022 Update for SharePoint Server 2019 (language dependent)

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

Language independent fix: 16.0.10389.20000
Language dependent fix: 16.0.10389.20000

 
Related Links:

8 Comments


  1. Hi Stefan,

    Whether SP2019 August 2022 CU installation directly into the SP2019 server where the last patch done till April 2022 CU, will it taken care of “Trending Issue: left navigation missing after applying May 2022 CU for SharePoint Server 2019” issue as well (or) we still need to follow the work around steps?

    Reply

    1. From the Microsoft Premier Support, I received the following:

      “The fix has now been released as part of the August 2022 SharePoint 2019 Cumulative Update (CU) packages.
      All details as well as the download links for the CU you can find on my colleague’s (Stefan Goßner) blog post available at -> https://aka.ms/sp2019/2022-08.”

      Reply

    2. Hi Prabhu,
      installing August 2022 CU will resolve the issue. No need to apply the workaround.
      Cheers,
      Stefan

      Reply

      1. Hi Stefan,

        Just to be clear, we no longer need to run the Update SideBySide token PowerShell command after applying the updates and running the configuration wizard? Or should we still do that step?

        Thanks in advance!

        -Daniel

        Reply

        1. Hi Daniel,
          if SideBySide patching is being used/active you have to update the SideBySide token with all updates as before.
          But if SideBySide patching was only activated as a workaround for the trending issue reported earlier it is now safe to disable sidebyside patching.
          Cheers,
          Stefan

          Reply

  2. Thanks Rickard & Stefan for your kind response.

    Reply

  3. After running the updates I still do not have left navigation.
    DBs are up to date
    No Errors on after updates: PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
    No Errors on: Install-SPApplicationContent
    Object Cache 5gb

    Reply

    1. Hi Toni,
      the fix will resolve the issue that could otherwise be resolved using CTRL-F5. so a client side caching issue.
      If CTRL-F5 does not solve the problem, then this fix will not do anything.
      Please double check. If CTRL-F5 does not solve it, your problem is different and requires different resolution.
      E.g. a common problem is that the patch level of the language dependent and independent fix is not the same.
      If you need assistance to troubleshoot the issue I would recommend to open a ticket with Microsoft support.
      Cheers,
      Stefan

      Reply

Leave a Reply

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