Troubleshooting New Responder Scripted Installations

Michael Barrow -

During the installation of the Responder using the scripted method there could a process missed due to workstation performance, missing required components or general errors. This guide will assist with resolving the majority of the issues.


The pyrusconnectresponder service has not been installed

There are a number of reasons as to why the service may not have been installed. The most common reasons are detailed below:-


Missing .NET Components

If you had seen the following window during the service installation then the .NET Framework 3.5 (Including .NET 2.0 and 3.0) are not installed /enabled on the workstation:-



Simply complete the installation by clicking on Download and install this feature

If this has been missed, the feature can also be added via Programs and Features - Turn Windows features on or off


Once this has been completed browse to where the Responder installation files have been stored (For example C:\Responderinst). Within the file list execute the SVCInst.bat file (as Administrator). This should now install the pyrusconnect-responder service.


No Service installation Window was displayed

If .NET Framework 3.5 (Including .NET 2.0 and 3.0) was already installed/ Enabled it could be that the SVCInst.bat was not executed. In some cases we have found this to be an environmental issue and have been unable to reproduce this in house.

Again simply executing the SVCInst.bat (As Administrator) should install the pyrusconnect-responder service.

If the batch file is not available the following can be completed to also install the service:-

  • From a Windows Command Prompt (Run As Administrator) change folder to C:\node\pyrusconnect-responder\ and run node index install to create and start the Windows service

For further information on troubleshooting the responder installation please use the below guide.

If further assistance is required please do not hesitate to contact our engineers via email



Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk