Workflow Manager 1.0 Now Supported on Windows Server 2016 with CU4


Hello everyone,

Today I’ll talk about a great news that can interest those who works with SharePoint On-Premises.

I have a customer where the infrastructure team wanted to upgrade our entire server to the latest version as a part of our migration from SharePoint 2013 to SharePoint 2016.

Seems pretty cool to be up to date but they warn us about one little problem


Windows Server 2016 does not support Workflow manager… ouch


As a reminder, Workflow Manager was introduced with SharePoint 2013 to run the custom workflows out of the SharePoint. That’s how you were supposed to develop your new Visual Studio Workflow to use it.

Workflow manager introduced also the possibility to create SharePoint 2013 Workflow with SharePoint Designer.

So in the end, many people used it one way or another.


Not so long ago, the workflow team announce the good news, Workflow Manager Server 1.0 now supports the following platforms when used in a SharePoint Server 2016 environment.

  • .NET 4.6+ (when using Service Bus Server 1.1 with KB3086798)
  • Windows Server 2016
  • Windows 10 x64 (for development purposes)
  • SQL Server 2014 & SQL Server 2016


More info here :


Hoping this helps,



Could not successfully create management Service Bus entity ‘WF_ManagementWFTOPIC’


Hello everyone,

Today I will talk about the day I almost became bald … the day I wanted to install the workflow manager on my 2013 development environment.

Wanting to do a clean install, I wanted to specify a specific service account for the application and not the Almighty Dev Farm Admin. However during my many attempts I always ended in front of an error like « Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of…”

After tearing my hair out for hours I made a last attempt which proved successful, connect to my server directly with the desired service account and perform the installation.

I confess not to understand why because I tried the installation with a “Run as”. Perhaps a user profile on the machine is needed to store data.


Hope this helps.