April 2024 CU for SharePoint Server 2019 is available for download

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

  • KB 5002580 – April 2024 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • KB 5002538 – April 2024 Update for SharePoint Server 2019 (language dependent)

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

Language independent fix: 16.0.10409.20027
Language dependent fix: 16.0.10409.20027

Related Links:


  1. The language dependent update installation fails for us. Anyone else experiencing this? The language independent installation worked fine, and we used the same account and procedures when installing both).
    The error we see in the log is below:

    OPatchInstall: Getting the data from the file ‘C:\Temp\2024_04_April\wssloc2019-kb5002538-fullfile-x64-glb.exe’
    OPatchInstall: Successfully retrieved the data location and size
    OPatchInstall: Extracting the file id ‘wssmui-nb-no.msp’ to the path ‘C:\Users\SVCOPN~1\AppData\Local\Temp\OWP15D6.tmp\wssmui-nb-no.msp’

    OPatchInstall: The extraction of the files failed
    OPatchInstall: Setting system property ‘SYS.ERROR.INERROR’ with value ‘1’
    OPatchInstall: Setting system property ‘SYS.ERROR.CODE’ with value ‘0x80004005’


  2. Hello,
    After installation, the administration pages on my sharepoint site are blank Anyone else experiencing this?


    1. Yes, I do on the CA Pages


  3. After installation we experienced an issue when uploading a new version of a document using drag’n’drop into the EDGE and the old-school “Upload” button. An error icon is displayed on the right-hand side in the library’s toolbar, but without any message display, instead an empty tooltip appears. The document has not been uploaded. This happens in modern view only. Uploading new documents works fine.

    A workaround is to upload new versions of an existing document in classic view.

    Any thoughts?


  4. HI,

    I have installed this patch and I have problem with the CA. Blank screen on the Central Administration.
    Other web applicatnion work well.
    I don’t have any special errors in uls.


    1. Hi Adam,
      did you install both patches and did you run PSConfig?


  5. Hi Stefan,
    Yes, I check on every server update status in the windows app apps.
    When I have updated last server yestarday I check status and it look good with success on every servers
    Can I check it in the powershell. I am looking for the SP powershell docs but I didn’t find it.
    Thank in advance.


    1. Hi Adam,
      I would suggest to open a ticket with Microsoft Support to investigate this.
      Some steps you could do on your own: check the http status code and correlation ID in the response in Fiddler for the request.
      If the response does not have a correlation ID enable failed request tracing in IIS and check if an error is reported here.


  6. Thanks Stefan,

    I checked in SysKit. Staus look good for all servers.
    Probably I will open ticket.


  7. Hello Stefan, we have recently discovered the following problem in the People Picker with the April CU 2024 for SP2019. New users are no longer displayed in People Picker since the CU was installed. Old users are still displayed. The new users are synchronized without errors in the user profile. No errors are displayed in the ULS log. The LDAP query simply returns a 0 result. Several domains are trusted in People Picker. All domains are fully trusted. When I try to execute the generated LDAP Query with the powershell command Get-ADUser it works. Do you know this problem?Christian


    1. Hi Christian,
      I haven’t seen this issue. Are you executing the LDAP query in powershell in context of the same user account as the SharePoint? To ensure that its not a permission issue.


      1. Yes, and in the context of the service account with PowerShell it works fine. Only in the SharePoint process I get this behaviour. It is very strange. This behaviour startet after applying the CU.


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.