June 2024 CU for SharePoint Server 2019 is available for download

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

  • KB 5002602 – June 2024 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • There was no language dependent fix released this month.
    The most recent language dependent fix is KB 5002538 from April 2024 CU.

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

Language independent fix: 16.0.10411.20004

Related Links:


  1. Hi, Stefan!
    A few months ago, I wrote to you about my problem with installing updates on a large SharePoint farm. Unfortunately, I don’t remember which post my comment was in and attach link. 🙁

    At that time, you advised me to update my 1200 content databases in parallel using PowerShell. I took your advice and ran 4 sessions simultaneously (one for each SQL cluster). As a result, the database update time was reduced from 11 hours to 2.5 hours. Great result!

    However, after updating the databases, I need to run the Configuration Wizard on the servers, and it can’t be run in parallel. On each of my 20 servers, the Wizard runs for 10-15 minutes (depending on the server). The most time-consuming step is the last one – “Finalizing upgrade”. According to the logs, at this step, the Wizard goes through all the databases again and just checks their version. And this happens on each server.

    Do you have any ideas on how to speed up this process?


    1. Hi Evgeny,
      you cannot run it in parallel completely – but you can executed it first on one server to ensure that all the database specific operations are completed and after this is done you can run it on all other servers in parallel.


  2. I don’t know if Stefan will see this response, but his instructions explaining that you can run the Configuration Wizard in parallel after you run it successfully once on the first server is huge. We also upgrade 100 content databases in multiple sessions to speed up the process, plus to also allow for monitoring since you can view this step’s progress in CA.

    We have only 7 servers in our farm, but running the Configuration Wizard in parallel for 6 of these servers will save over an hour in the process.

    Nice tip to learn after 10 years with a company that requires the monthly patch to be installed within two weeks of release.

    Thanks Stefan!


Leave a Reply

Your email address will not be published. Required fields are marked *

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