The product group released the April 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 April 2026 CU will be available at the following location in a couple of hours:
- KB 5002844 – April 2026 Update for SharePoint Workflow Manager
The download for April 2026 CU is available through the following link:
- Download April 2026 Update for SharePoint Workflow Manager
- Download SharePoint Workflow Manager Client version 16.0.19725.20210
This CU requires SharePoint Workflow Manager Client version 16.0.19725.20210 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.
Permalink
I believe this should be omitted: “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.”
Permalink
Hi Viktoriia,
thanks a lot for the hint!
Indeed a copy&paste error. 🙂
Cheers,
Stefan
Permalink
The client download doesn’t have client in the .msi name, like past downloads. Is this really the client installer?
Permalink
Hi Marlene,
yes it is the correct installer even if the name is different this time.
Cheers,
Stefan
Permalink
Please delete my post. The version numbers are correct.
Permalink
Hi Kevin,
yes the version is correct. You can verify it yourself by checking the file system property of the two files.
The version number is listed on the Details tab.
16.0.19127.506 does not make sense a the last number in the version always has 5 digits and not 3.
We switched from 18526 to 19127 as the 3rd number with October 2025 CU.
August 2025 CU had version 16.0.18526.20518
October 2025 CU had version 16.0.19127.20262
There was no September 2025 CU. So the lowest version number for SPWFM starting with 16.0.19127 is 16.0.19127.20262
Cheers,
Stefan
Permalink
Hi Stefan,
After installing these updates on brand new SP SE farm, we began to receive the following error when we browse the workflow service default port. Despite the Workflow service is displayed as Connected on Central Admin:
AuthorizationErrorThe caller does not have the necessary permissions required for this operation. Permissions granted: None. Required permissions: ReadScope.
Permalink
Hi Murat,
the required steps are:
– uninstall the old Workflow Manager Client component from all SharePoint Servers and all Workflow Manager Servers.
– install the new Workflow Manager Client component on all SharePoint Servers and all Workflow Manager Servers.
– install the update for SharePoint Workflow Manager on all Workflow Manager machines.
– restart the workflow manager machine if requested by the installer.
– Upgrade Workflow Manager Farm using the Workflow Manager Configuration Wizard.
Did you follow these exact steps?
Cheers,
Stefan
Permalink
Hi Stefan,
Nothing has changed. Do you think are we missing some db permissions?
Permalink
Hi Murat,
hard to day – might require to analyze some logs.
If you need assistance here my suggestion would be to open a ticket with Microsoft Support.
Cheers,
Stefan
Permalink
Hi Stefan,
after deinstallation of SharePoint Workflow Manager Client on Workflow Manager machine, I couldn’t install the new version 16.0.19725.20210 “sharepointworkflowmanager.msi” !!
After Doppelklick or right-Mouse-Klick on the file nothing happens 🙁
the same happens with “sharepointworkflowmanager-x64-subscription-kb5002844-fullfile-x64-glb.exe” update-File 🙁
What are your experiences with these Files?
How can I install them?
Permalink
Hi Mohammed,
if nothing happens, it sounds as if there is something wrong with the Windows Microsoft Installer component on this server.
My suggestion would be to open a support case with Microsoft to get this investigated or to reinstall the affected machine.
Cheers,
Stefan
Permalink
Thank you Stefan for the quick Answer 🙂
I could install the Files in Admin-PowerShell Window.
After the WF-Farm Upgrade all Workflows are working again 🙂
Best Regards
Permalink
Hi Stefan,
I have a problem.
Operation failed. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
When the user starts the workflow, the following message is displayed.
I checked the server and found that the related certificate has expired.
At the moment, the current situation is as follows:
Service Bus Gateway is stopped
Workflow Management Site (port 12290) is using an expired certificate
I searched online for possible workarounds, and some suggest setting the system clock back to a date before the certificate expired, but that is not an option in my case.
Leaving that option aside, I found the following workaround.
Do you think it would work?
Once you have new cert in the cert store, you can update it using the below powershell:
• So, the first step should be updating the Service Bus Services, for that you should start a Workflow Manager PowerShell console as an Administrator and run the below cmdlets.
Set-SBCertificate -FarmCertificateThumbprint YourThumbprint -EncryptionCertificateThumbprint YourThumbprint
Stop-SBFarm -Verbose
Update-SBHost
Start-SBFarm
• After this step, we need to update the Workflow Manager Services related Certificates
Set-WFCertificate -SslCertificateThumbprint YourThumbprint -EncryptionCertificateThumbprint YourThumbprint
Stop-WFHost
Update-WFHost
Start-WFHost
Does “YourThumbprint” refer to the thumbprint of the new certificate that should replace the expired one?
I’m pasting the full link below.
https://sharepoint.stackexchange.com/questions/252320/sharepoint-2013-workflow-manager-expired-certificate-renewal
Hi, thank you.
Permalink
Hi Stefan,
I have a question regarding SharePoint Subscription Edition and SharePoint Workflow Manager.
I have a SharePoint Subscription Edition farm running the April 2026 CU, integrated with SharePoint Workflow Manager. The SharePoint servers currently have SPWFM Client 16.0.19127.20336 installed.
I noticed that the version of the SharePoint Workflow Manager Client required by SharePoint is lower than the version required by the April 2026 CU for SharePoint Workflow Manager, which requires SharePoint Workflow Manager Client 16.0.19725.20210.
My concern is that if I install SPWFM Client 16.0.19725.20210 on the SharePoint servers to meet the Workflow Manager requirements, could this cause any issues or compatibility errors with the SharePoint April 2026 CU?
Is it recommended to keep version 16.0.19127.20336, or should the client be upgraded to 16.0.19725.20210?
Thank you.
Permalink
Hi Jesus,
the SharePoint Workflow Manager client neesds to match the version of SharePoint workflow manager.
If you have SharePoint Workflow Manager from April 2026 CU installed you need to have SharePoint Workflow Manager Client version 16.0.19725.20210 installed as well on the SharePoint server machines and on the SharePoint workflow manager machine.
Different SPWFM clients can cause problems and such a combination is unsupported.
Cheers,
Stefan
Permalink
Hello,
I keep having a terrible time with updates for Workflow Manager. I follow the directions and every time it destroys my install. I’ve had to rebuild every single time.
Can anyone tell me why Workflow Manager is so buggy and dies?
I ran the upgrades for SharePoint Subscription Edition. That required I update Workflow Manager. I did the clients, I did the manager, I ran the Config wizard. It died before I even got to the SharePoint upgrade.
Any help in understanding would be so very helpful. I keep stepping on SharePoint landmines.
Permalink
Hi David,
can you be more specific what “destroys my install” and “It died” means in this context?
Cheers,
Stefan
Permalink
Sorry for the stress comment. 🙂
I just went through the upgrade. I suspect it would have gone better if I didn’t have a bad Datasource connection.
The disaster recovery document connection string changed from the last time I used it. The “Asynchronous Processing=True” was a problem.
Restore-WFFarm -RunAsAccount $wfmAcc -InstanceDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfInstanceDB;Integrated Security=True;Asynchronous Processing=True;Encrypt=False” -ResourceDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfResourceDB;Integrated Security=True;Asynchronous Processing=True;Encrypt=False” -WFFarmDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfManageDB;Integrated Security=True;Encrypt=False” -InstanceStateSyncTime $restoreTime -ConsistencyVerifierLogPath $logPath -CertificateAutoGenerationKey $certGenKey -Verbose
Now as I look back at documentation, I see it was updated. And that part removed.
Restore-WFFarm -RunAsAccount $wfmAcc -InstanceDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfInstanceDB;Integrated Security=True;Encrypt=False” -ResourceDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfResourceDB;Integrated Security=True;Encrypt=False” -WFFarmDBConnectionString “Data Source=$newSQL;Initial Catalog=$wfManageDB;Integrated Security=True;Encrypt=False” -InstanceStateSyncTime $restoreTime -ConsistencyVerifierLogPath $logPath -CertificateAutoGenerationKey $certGenKey -Verbose
So, when I upgraded, I was seeing this invalid connection string issue. Workflows broke and so on.
Then I got lost in attempts to recover the workflow server but have no idea how to change a connection string. Had to rebuild the workflow server.
Only a few weeks ago I had a disk fill with logs on my last workflow server. That one could not be recovered either. I had to rebuild. (yeah alerts didn’t go out like they should have 🙂 )
I did recover. I did find that I really did need to remove the old wfm client. I had dll issues installing over the client. (I was in a testing phase trying to figure out the connection string issue.)
Thanks for input and response.
Permalink
Hi David,
I see where you are coming from. The product evolved a lot in the last 12 months. E.g. the asynchronous processing issue came from a change in the DB connectivity layer (switch from legacy System.Data.SqlClient to the modern Microsoft.Data.SqlClient. The incompatibilty related to connection string parameters between these two layers caused a lot of problems in the past.
And yes, upgrading the SPWFM client always requires uninstall and reinstall.
Installing on top of an installed client is not supported.
If I understand correctly at this moment you have a working SPWFM farm, correct?
Cheers,
Stefan
Permalink
Hello Stefan,
Yes, I did recover. I’m at the most recent patch level. Patches are a little hard to find these days adding a little to the stress of updating.
Your site helps. I do wonder why Microsoft doesn’t seem to have an official posting of the updates in chronological order. I had to find your site to get the details.
Best regards