September 2024 CU for SharePoint Server 2019 is available for download

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

  • KB 5002639 – September 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 5002597 from August 2024 CU.
    If this is not yet installed on your Farm, you need to install it together with the language independent fix.

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

Language independent fix: 16.0.10414.20002
 

Related Links:

17 Comments


  1. Where can I find second update file (language dependent), you said I need to install both but there is only one link. Also can you confirm this is CU? It looks like Security Update not cumulative patch.

    Reply

    1. Hi,
      if you check the article aove you will see the link to the most recent language dependent fix. It was released with August CU and if it was not installed earlier you need to install it now together with the language independent fix from September.
      All SharePoint fixes are CUs. No exception.
      Cheers,
      Stefan

      Reply

  2. Is there also a fix planned for the IncludeUserSecurity parameter in the Import-SPWeb command? It still throws the error Import-SPWeb: Updates to system roles is not allowed. It crashes, for example, on a file that has permission inheritance disabled or in requests for access to the site. Without the parameter the import is successful. I need it for migrate subsite to site collection with all permissions.

    I use for export:
    Export-SPWeb -Identity $subsiteURL -Path $backupLoc -IncludeUserSecurity -IncludeVersions All -NoLogFile -NoFileCompression -Force -Verbose

    For Import:
    Import-SPWeb -Identity $url-Path $backupLoc -UpdateVersions Overwrite -NoLogFile -NoFileCompression -Force -IncludeUserSecurity -Verbose

    Reply

    1. Hi Adrián,
      I just verified and did not find a customer escalation on this topic.
      My suggestion would be to open a support case with Microsoft to get this investigated.
      Cheers,
      Stefan

      Reply

  3. Hi Stefan,

    Are you aware about an issue since this CU with Approval workflow ?

    I have this in ULS

    Workflow Compilation XPath killswitch resulted in an exception: System.InvalidOperationException: This feature has been temporarily disabled. at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.CompileBytes(Byte[] xomlBytes, Byte[] rulesBytes, Boolean doTestCompilation, String assemblyName, SPWeb web, Boolean forceNewAppDomain)

    No problem with 3-state workflow.

    Thanks

    Reply

    1. The same problem. Simple SharePoint designer flow stop working.

      Reply

    2. Hi, this work. Put this in web.config

      <System.Workflow.ComponentModel.WorkflowCompiler>

      <targetFx version="v4.0">

      <authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" Namespace="Microsoft.SharePoint.WorkflowActions.WithKey" TypeName="*" Authorized="True" />

      </targetFx>

      Reply

  4. Hi Stefan,
    One of our SharePoint 2019 farms uses the French language pack. I attempted to download the French version of the August 2024 language dependent KB 5002597 however the drop down selection only has English as a choice. Could you please advise if there is a direct link we could use to obtain the French version of the language dependent KB 5002597? Thank you.

    Reply

  5. Hello! Do you know anything about the known issue “Certain types that inherit from IDictionary are blocked from deserialization (KB5043462)”? Do you know if it will be resolved in the next release?

    Reply

    1. Hi Daniela,
      sorry I don’t have this info. My suggestion would be to apply the workaround from KB 5043462.
      Cheers,
      Stefan

      Reply

    2. Hi, the problem also occurs with other types from the System.Collections.Generic namespace for example System.Collections.Generic.List, but I don’t know what to enter in the name property because “AllowedListType” doesn’t work.

      Reply

      1. Hi Maciej,

        I checked the existing escalations but it seems there is no such escalation.
        Does the issue reproduce in SharePoint Server Subscription Edition?
        Because there only security fixes will be made available for products in extended support like SharePoint Server 2019.

        Cheers,
        Stefan

        Reply

      2. Hi Maciej,
        please open a ticket with Microsoft to get this analyzed in more detail.
        Cheers,
        Stefan

        Reply

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.