How to uninstall Workflow Manager 1.0 when the command ‘Remove-WFHost’ does not work

One of my customers had installed Workflow Manager 1.0 but while uninstalling it, he was encountering the mentioned below error:
This computer is part of a farm. To uninstall, first leave the farm either using 'Leave from Farm' option in Configuration Wizard or Remove-WFHost cmd-let in PowerShell. 


When we tried to execute the command Remove-WFHost, we were getting the following error:
remove-wfhost : Ceritificate requested with thumbprint {GUID} not found in the certificate store



We executed the following steps to resolve the issue. 

  1. Deleted the following registry hives: 

HKLM\Software\Microsoft\Workflow Manager
HKLM\Software\Microsoft\Service Bus

        2.  Deleted the following databases:


       3.  Uninstalled CU1 for Workflow Manager 1.0 and CU1 for Service Bus 1.0 from Control Panel

       4.  Uninstalled Workflow Manager 1.0, Workflow Manager Client 1.0, Service Bus 1.0 and Windows Fabric in the order mentioned (Refer:

       5.  Rebooted the machine hosting WFM 1.0

Written by:
Kshitij Dattani

Reviewed by:
Shashidharan Krishnan 

Microsoft India GTSC

Comments (8)
  1. Tina says:

    I am planning to install Workflow Manager, I have 3 WFE and 4 APP server. Do I need to install on all the servers or I can just install it on the 3 WFE server. I was checking this FAQ but it does not mention anything about the Workflow Manager…/Sharepoint-2013-FAQ-and-changes-467.html

  2. Rajesh says:

    I have 1 APP,  3 WFE Servers …Do i need to install workflow manager 1.0 in all servers?

    Shall i install workflow manager  first in APP server then do i need to JOIN the form in all 3 WFE by installing workflow manager 1.0 at all 3 WFE.

    Please advise.

  3. Zed says:

    It helps me solve my problem. thanks

  4. Inteleptu says:

    You must add to the guide that the folder: C:Program filesWorkflow Manager must be also deleted mainly because it will give you an error if you try to install again workflow manager.

  5. anthony.edwards says:

    Can you give me more instruction on this step please?!

      2.  Deleted the following databases:







  6. Chris C says:

    @Anthony, use SQL Management studio upon your SQL Server to delete those databases

  7. NickThoman says:

    Tip: I had this same problem in my test environment because the machine cert that was used for workflow expired and was deleted from the server. I was able to recover this “old” cert however by looking for the original request ID in the CA cert list. Once I found the original machine cert by matching the thumbprints, I grabbed the RequestID and ran: “certreq -retrieve 1246 Old.cer”. This exported the old cert so I could copy it to the workflow server and import it again. Once imported, you will still get this error. That’s because the cert expired. Easy fix though, just roll back time on the server till the day before it expired. Now with just run the powershell found here to replace the old cert with your new one. Should update with no issues and now you can just reset the time on the server back to the current time and everything should be happy once more.

  8. Tam Dao says:

    Thanks Kshitij for your useful post.
    #1 & #2 helped me.

Comments are closed.

Skip to main content