The product group released the February 2026 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 February 2026 CU will be available at the following location in a couple of hours:
- KB 5002814 – February 2026 Update for SharePoint Workflow Manager
The download for February 2026 CU is available through the following link:
- Download February 2026 Update for SharePoint Workflow Manager
- No new version of SharePoint Workflow Manager Client has been released with February CU
This CU requires SharePoint Workflow Manager Client version 16.0.19127.20336 to be installed
- on all servers in the Workflow Manager farm AND
- on all servers in the SharePoint Server farm
This is the same SPWFM client version that was shipped with the November 2025 CU. If version 16.0.19127.20336 is already installed from the November CU, there is no need to reinstall or update SPWFM client with this CU.
For detailed download and installation instructions see the KB article above.
Permalink
There seems to be an error with the URL https://support.microsoft.com/en-US/help/5002814 ?
Permalink
Hi SharePointAdmin,
the link is correct – but the KB article is not yet published.
I some cases it take a couple of hours till they are published and replicated.
For this reason I have written in the blog post: “The KB article will be available at the following location in a couple of hours”
Cheers,
Stefan
Permalink
The article is available now.
Permalink
I’m still getting the KB article link error a day later. Any idea when the KB article might be available?
Permalink
Hi Fred,
yes – this is a known issue. There is a problem with the publishing system which is currently being investigated.
Aside from the links I shared above the following information might be interesting:
“This update resolves an issue in which the SharePoint Workflow Manager (SPWFM) wizard can’t run when you use an encrypted Microsoft SQL Server connection.”
Cheers,
Stefan
Permalink
Hi Fred,
The article is available now.
Cheers,
Stefan
Permalink
Thank you!
Permalink
Ist es eigentlich notwendig oder empfehlenswert, nach dem Update vom Manager / Clients die Workflows nochmal neu zu veröffentlichen?
Permalink
Hi Kevin,
This should not be required.
Cheers,
Stefan .
Permalink
Hello Stefan,
currently im migrating from SP2019 to SPSE, new windows servers and new SQL servers but moving the databases of course. I have searched so long online but couldn’t find an answer to this: Can the Workflow manager databases be moved to a new SQL server and then remounted to the same farm or will i have to set up workflow manager from scratch and if so, will all current workflows break and have to be recreated?
Thank you!
Permalink
Hi Philip,
in this case you need to use the desaster recovery instructions for SharePoint Workflow Manager:
https://learn.microsoft.com/en-us/sharepoint/governance/sp-wf-mgr-farm-restore-disaster-recovery
Be aware that there is currently one problem:
In Step “Restore the Workflow Manager Services Farm” the “-InstanceDBConnectionString” parameter needs to be modified by removing the this part: “Asynchronous Processing=True;”
Cheers,
Stefan
Permalink
Hi Stefan,
We are in the process of installing SharePoint Workflow Manager (SPWFM) on our SharePoint Subscription Edition (SPSE) farm, but we are consistently running into multiple issues throughout the setup.
At times, the Workflow Backend service crashes repeatedly, and when we manage to stabilize it, the Service Bus services get stuck in “Starting” and never complete the startup. Unfortunately, there are no complete step‑by‑step installation documents available for SPWFM specifically on SPSE, and despite following the currently available guidance, we keep encountering the same errors.
We have also had a Microsoft support case open for over two months, but there has been no resolution so far.
Could you please provide practical, end‑to‑end documentation or a validated installation guide for deploying SPWFM on an SPSE farm—ideally something that works in one clean run without these recurring issues? Any internal or field-proven guidance would be greatly appreciated.
Thank you for your help.
Error Log: Application: Microsoft.Workflow.ServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.MissingMethodException
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.IsPoison(Microsoft.Activities.Dispatcher.DispatcherMessage, Microsoft.Activities.Dispatcher.MessageSessionContext)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.PoisonCheckPeekCompleted(System.IAsyncResult)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion, System.IAsyncResult)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(System.IAsyncResult)
Exception Info: System.AggregateException
Exception Info: Microsoft.Workflow.Common.FatalException
at Microsoft.Workflow.Common.Fx+<>c__DisplayClass18_0.b__0()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 16.0.19127.20506, time stamp: 0xb253bee9
Faulting module name: KERNELBASE.dll, version: 10.0.26100.32522, time stamp: 0x5bbcd73d
Exception code: 0xe0434352
Fault offset: 0x00000000000ca80a
Faulting process id: 0x2CF8
Faulting application start time: 0x1DCB5EEB5189EBF
Faulting application path: C:\Program Files\Workflow Manager\1.0\Workflow\Artifacts\Microsoft.Workflow.ServiceHost.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 272f7e65-bad6-4d9c-9100-da53305eb7b4
Faulting package full name:
Faulting package-relative application ID:
The Workflow Manager Backend service terminated unexpectedly. It has done this 4 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
If above fixed getting another one – Faulting application name: Microsoft.ServiceBus.MessageBroker.exe, version: 16.0.19127.20506, time stamp: 0xc02b363e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ffd5f0c3102
Faulting process id: 0x329C
Faulting application start time: 0x1DCB648BD3EE2FE
Faulting application path: C:\Program Files\Service Bus\1.1\Microsoft.ServiceBus.MessageBroker.exe
Faulting module path: unknown
Report Id: a10f3805-2db7-4cb0-a489-3a36454f4ae5
Faulting package full name:
Faulting package-relative application ID:
Application: Microsoft.ServiceBus.MessageBroker.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Failed to start Service Bus Broker Service.
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Microsoft.ServiceBus.MessageBroker.Backend.OnStart(System.String[])
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Permalink
Hi Stefan,
We are in the process of installing SharePoint Workflow Manager (SPWFM) on our SharePoint Subscription Edition (SPSE) farm, but we are consistently running into multiple issues throughout the setup.
At times, the Workflow Backend service crashes repeatedly, and when we manage to stabilize it, the Service Bus services get stuck in “Starting” and never complete the startup. Unfortunately, there are no complete step‑by‑step installation documents available for SPWFM specifically on SPSE, and despite following the currently available guidance, we keep encountering the same errors.
We have also had a Microsoft support case open for over two months, but there has been no resolution so far.
Could you please provide practical, end‑to‑end documentation or a validated installation guide for deploying SPWFM on an SPSE farm—ideally something that works in one clean run without these recurring issues? Any internal or field-proven guidance would be greatly appreciated.
Thank you for your help.
Permalink
Hi Stefan,
While reviewing the CU installation process, I noticed that the documentation indicates the step “Run Upgrade Workflow Manager Farm in the Workflow Manager Configuration Wizard” should be performed.
However, I do not see the “Upgrade Workflow Manager Farm” option in the wizard.
Could you please let me know where I can find this option?
Thanks in advance.