April 2025 CU for SharePoint Server 2016 is available for download

- - 28 Comments

The product group released the April 2025 Cumulative Update for SharePoint Server 2016 product family.

This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.

The KB articles for April 2025 CU should be available at the following locations in a couple of hours:

  • KB 5002692 – April 2025 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • KB 5002682 – April 2025 Update for SharePoint Server 2016 (language dependent)
    This is also a security update!

The downloads for April 2025 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 2016 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.

 
SharePoint 2016 April 2025 CU Build Numbers:

Language independent fix: 16.0.5495.1002 updated: 16.0.5495.1003
Language dependent fix: 16.0.5495.1002

 
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

Related Links:

28 Comments


  1. Just like the previous 2016 CU, this one fails to install (for us). I tried it multiple times but it always ends with „The installation of this package failed“.

    I also stopped and disabled the following services, re-booted the machine but no success:
    AppFabricCachingService
    SPAdminV4
    SPSearchHostController
    SPTimerV4
    SPTraceV4
    SPWriterV4
    W3SVC
    IISADMIN

    Will Microsoft address this issue this time or should we open a ticket..?

    Reply

    1. Hi Simon, please open a ticket to ensure that this can be investigated.

      Reply

      1. Thanks for the reply. We will open a ticket, but with all the issues this month as well as in February I would assume that Microsoft would provide a general fix for this issue.

        Again, thanks for all your contributions here 🙂

        Reply

  2. two times in a row installation failed.

    Reply

    1. reached out to Microsoft, it’s a known issue on their side, the engineers are working on it.

      Reply

  3. Does anyone else have trouble installing this patch?

    In the MSI log, I’m getting this:
    MSI (s) (14:44) [12:18:15:896]: Assembly Error:Strong name signature verification failed for assembly ‚%1‘. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.
    MSI (s) (14:44) [12:18:15:896]: Note: 1: 1937 2: {FD7C5302-4D93-4227-9FEA-DB22FE55459F} 3: 0x80131045 4: IAssemblyCacheItem 5: Commit 6: Microsoft.Office.Project.Server.PWA,fileVersion=“16.0.5493.1000″,version=“16.0.0.0000000″,culture=“neutral“,publicKeyToken=“71E9BCE111E9429C“,processorArchitecture=“MSIL“
    04/09/2025 12:18:15.896 [4116]: ACE[4]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-2

    MSI (s) (14:44) [12:18:15:911]: Product: Microsoft SharePoint Foundation 2016 Core — Error 1937. An error occurred during the installation of assembly component {FD7C5302-4D93-4227-9FEA-DB22FE55459F}. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.Office.Project.Server.PWA,fileVersion=“16.0.5493.1000″,version=“16.0.0.0000000″,culture=“neutral“,publicKeyToken=“71E9BCE111E9429C“,processorArchitecture=“MSIL“

    Error 1937. An error occurred during the installation of assembly component {FD7C5302-4D93-4227-9FEA-DB22FE55459F}. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.Office.Project.Server.PWA,fileVersion=“16.0.5493.1000″,version=“16.0.0.0000000″,culture=“neutral“,publicKeyToken=“71E9BCE111E9429C“,processorArchitecture=“MSIL“
    04/09/2025 12:18:15.911 [4116]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393

    And yes, the signature of the file Microsoft.Office.Project.Server.PWA.dll has a strange certification Path:
    1. Microsoft Corporation
    2. Microsoft Testing PCA 2010 (this looks strange)
    3. Microsoft Testing Root Certificate Authority 2010 (this one is not in my trusted root certification authorities)
    Other DLLs have this:
    1. Microsoft Corporation
    2. Microsoft Code Signing PCA 2010
    3. Microsoft Root Certificate Authority 2010

    Reply

    1. Hey all,

      We had the same thing on all of our servers for that KB. We raised a ticket with premier, that Root CA is wrong (Microsoft Testing Root Certificate Authority 2010), so the chain is broken on the .dll, they are going to the product group and will release a patch for the patch or will retract the update. I will report back when we get an update from them! Good luck everyone!

      Reply

  4. Since the test comment only stays visible if I uncheck the notification settings, I suggest to review this, Mr. Webmaster 😐 Previously, I commented three times and after initially being visible, the comments disappeared to god-knows-where after the next page reload.

    On topic: I tried to install KB 5002692 onto SP2016@server 2026 and it fails with error 1603!
    The log offers no details in its 118 MB as to why, at least not what I can gather.
    Anyone else affected? Tried to stop services (appfabric cache, IIS, …) since that is all I find googling sharepoint update 1603 and retried the installation, still 1603.

    Reply

    1. Hi Weil, this is due to comment moderation to avoid comment spam. Comments will be visible after approval.

      Reply

  5. Hi Stefan,

    I’m curious if you experienced any issues with installation of KB5002692. I have unsuccessfully tried all three methods (installing via Windows Updates, downloading the standalone package from the Microsoft Update Catalog and also from the Microsoft Download Center) on a 4 server farm. Each of the servers had the same issue whereby installation failed.

    Event logs show the following detail with ID 11937 „Product: Microsoft SharePoint Foundation 2016 Core — Error 1937. An error occurred during the installation of assembly component {FD7C5302-4D93-4227-9FEA-DB22FE55459F}. HRESULT: 0x80131045, assembly interface: |AssemblyCacheItem, function: Commit, assembly name: Microsoft.Office.Project.Server.PWA,fileVersion=“16.0.5493.1000″,version=“16.0.0000000″,culture=“neutral“,publicKeyToken=“71E9BCE111E9429C“,processorArchitecture=“MSIL“.

    Initially, I stepped through the process of clearing the Windows Update cache (renaming SoftwareDistribution and catroot32 folders, etc.). When that didn’t work, I tried installing from the package in the Download Center. Same result. The package from the Update Catalog threw an error about writing to the microsoft.office.project.server.native.dll file but the account I was logged in with had full control permissions to C:\Program Files\Microsoft Office Servers\16.0\Bin.

    By comparison, KB5002682 installed without any issues. Other Windows Updates are also succeeding.

    Previously I was running the February 2025 language independent update along with the January 2025 language dependent update and had no issues installing those but have found that a script we use for creating project sites stopped working so I’m keen to try the April updates.

    Any suggestions?

    Reply

    1. Hi Judith, I would suggest to open a ticket with Microsoft support for this.
      Cheers,
      Stefan

      Reply

  8. We have also the same problem to install the Update on all of our SharePoint farms.
    In the Application Logs we get this Event:
    Product: Microsoft SharePoint Foundation 2016 Core – Update ‘Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002692) 64-Bit Edition’ could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

    In the System Event Logs we get this:
    Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for Microsoft SharePoint Enterprise Server 2016 (KB5002692) farm-deployment.

    Reply

  9. Same problems here.
    Also tried to download and install in manually and that install also fails.
    Did Microsoft test these updates before releasing them?

    Reply

  10. Just to confirm other with same problem:
    Same here – we tried to install the update on 3 different environments – completely same error. There must be something wrong with the package.

    Reply

  11. Hi Stefan/everyone,

    adding myself here as +1 for this issue for visibility.
    Running SP2016 on Windows Server 2016, installation fails some time after the bar completes.
    It is only the STS package that throws the error, WSSLOC works fine.

    Did a “remove from farm”, even a full reinstallation of SP2016. STS from 2025-01 installs fine, WSSLOC 2025-03 as well.

    Reply

  12. Hi Stefan/everyone,

    Just adding myself here as a +1 on this issue for visibility.

    The error log shows something similar to what Judith Buddle experienced.

    Reply

  13. We encountered the same errors in February, but they were limited to the frontend servers. This month, the issue has reoccurred and is now affecting all servers, with the update failing. The primary error is code 1603, along with multiple instances of Assembly Install: Failing with hr=80070005. We plan to log a support ticket to investigate further.

    Reply

  14. Hi Stefan,

    Same issue we are also facing on all servers in a SharePoint 2016 farm. KB 5002682 installed successfully but KB 5002692 is getting failed.

    Need your assistance to fix this issue.

    Cheers,
    Ganesh P.

    Reply

  15. Thanks a lot Stefan for your help, guidance any all the updates on the issues which we are facing every month post installing the security update in all SharePoint products.

    It is very much appreciated !!!

    Cheers,
    Ganesh P.

    Reply

    1. Hi Stefan,
      The problem is fixed in this new release ?
      Jeff

      Reply

      1. Hi Jeff,
        which problem do you mean?
        Cheers,
        Stefan

        Reply

  17. The installation of the SP 2016 April 2025 CUS :
    This will fail to install due to a DLL that is signed incorrectly

    Jeff

    Reply

    1. Yes. An updated package was released which fixes this issue.
      You can see this info also at the top of the KB article.

      Reply

  18. Ok, thanks Stefan !

    Jeff

    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.