November 2025 CU for SharePoint Workflow Manager is available for download

- - 16 Comments

The product group released the November 2025 Cumulative Update for SharePoint Workflow Manager.

This CU consists of a fix for SharePoint Workflow Manager and the SharePoint Workflow Manager client components which need to match SharePoint Workflow Manager.

The KB article for November 2025 CU will be available at the following Location in a couple of hours:

  • KB 5002799 – November 2025 Update for SharePoint Workflow Manager

The download for November 2025 CU is available through the following link:

This CU requires SharePoint Workflow Manager Client version 16.019127.20336​​​​​​ to be installed

  • on all servers in the Workflow Manager farm AND
  • on all servers in the SharePoint Server farm

For detailed download and installation instructions see the KB article above.

16 Comments


  1. Hi, Stefan,

    for new client, should I uninstalled oldclinet first, or can upgrade directly in all servers?

    thanks!

    Jing

    Reply

    1. Hi Jing,
      please use the detailed step-by-step instructions in the KB article.
      In short: yes, you need to uninstall the current client components and then install the new ones.
      The client components cannot be upgraded.
      Cheers,
      Stefan

      Reply

  2. Hi Stefan,

    Thanks for your work keeping us up to date – it’s very much appreciated! Just wondering if it is critical that the patch version of Sharepoint Subscription Edition matches the patch version of Sharepoint workflow manager? As in if I apply the November CU for SPSE do I also need to patch Workflow manager to the Number CU?

    Thanks again!

    Reply

    1. Hi Troy,
      not really. A minimum of August 2025 CU for SPWFM is technically required.
      But August 2025 CU for SPWFM has a couple of critical issues which are resolved in November 2025 CU for SPWFM. This is the main reason that this requirement was added to the KB article.
      But if there are SPWFM problems, Support might require November 2025 CU for SPWFM to be installed as it is much more stable than August and October CU.
      Cheers,
      Stefan

      Reply

  3. Hi Stefan,
    Do SPWFM patches function like SharePoint patches, in that each new patch replaces the previous ones, or do we need to apply all prior patches before installing the November patch? For instance, we have the August patches for SPWFM installed—can we directly install the November patch, or must we apply the September and October SPWFM patches first?

    Thanks.

    Reply

    1. Hi Umr,
      for the SPWFM server patches: they are cumulative and you only have to apply the most recent.
      For the SPWFM client: these a full installers. You need to uninstall the old one and then install the latest.
      Cheers,
      Stefan

      Reply

  4. Goo evening. Is anyone else having issues after installing the SPWFM updates for Server 2016? The workflows won’t start. The previous working patch was for September. I skipped October due to the issues others were having. I haven’t looked at the logs yet. All the other patches are up-to-date (SP 2016, Office, SQL).

    Reply

    1. Never mind. I had 1 of the collections in read-only mode (although I was testing the other one). Once I took it out, the workflow started OK.

      God bless you all and have a Happy Thanksgiving!!

      Reply

  5. Hi Stefan,

    Hope you are doing Great 🙂

    In the KB article, the installation steps for an existing farm in the November SharePoint Workflow Manager client still show the old client version, i.e., Install the SPWFM Client (16.0.19127.20262). However, in the steps for installing on a new farm, it shows a newer client version — Install the SPWFM Client (16.0.19127.20336).
    Is this a typo, or do we need to install the newer version? I checked older patch installation KB articles, and in those, both the existing farm and new farm steps used the same client version.

    Thanks.

    Reply

    1. Hi Chandu,
      yes – this seems to be a typo. As you can see above it is clearly written that the new client version is required.
      I will ping the KB article writer to update the article.
      Cheers,
      Stefan

      Reply

      1. Hi Chandu, the articles has been updated.
        Thanks for your helpful feedback!

        Reply

  6. Hi,

    This November CU update is still not stable.
    It was already a known issue with the previous WFM CU update that there was a problem after the update. https://blog.stefan-gossner.com/2025/10/14/resolved-trending-issue-classic-workflow-manager-workflows-fail-after-september-2025-cu-for-sharepoint/
    At the time, I managed to restore everything in our test environment using a farm restore, and planned to wait with the production update until a stable cu update.

    Yesterday evening I went ahead and started the update in production, and after the upgrade nothing worked again :-(.
    The logs were full of these errors:

    Service Bus exception swallowed at location ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException. Microsoft.ServiceBus.Messaging.MessagingCommunicationException: Error during communication with Service Bus. Check the connection information, then retry.
    —> System.ServiceModel.CommunicationObjectFaultedException: Internal Server Error: The server did not provide a meaningful reply; this might be caused by a premature session shutdown.
    TrackingId: urn:uuid:2eab927e-9749-41f9-a032-b927bfb45ee7, Timestamp: 27/11/2025 18:23:19

    So I quickly deleted the two management databases and started a farm restore. Now everything is working again.

    PS: Our production environment was a WFM farm running the original version from when WFM was first released.

    Regards,

    Johan

    Reply

  7. Hi,
    We just installed the october CU of SharePoint Subscription with november CU of SharePoint Workflow Manager and the workflow platform is broken even if it seems working. Get-SBFarmStatus and Get-WFFarmStatus are up and running, Workflow Service Status is connected, i can publish workflow 2013, i can start and terminate workflow but all the tasks inside the workflow are not executed. I always receive this error => Retrying last request. Next attempt scheduled after 12/3/2025 2:46 PM. Details of last request: HTTP Forbidden to https://……/_api/web/lists(guid’3d43213d-5866-447c-b51d-af679f2b70d7′) Correlation Id: c7937442-5437-7e92-b330-6e53eb871d41
    I don’t find any solution and it becomes really a mess to upgrade the platform.
    Regards,
    Angelo

    Reply

    1. Hi Angelo,

      I would suggest to open a ticket to get this analyzed.

      Cheers,
      Stefan

      Reply

      1. Hello Stefan,

        a ticket has already been created. But can you be assigned to this ticket ?

        Regards,
        Angelo

        Reply

        1. Hi Angelo, sorry – I am on business travel for the next 2 weeks.

          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.