The service did not respond to the start or control request in a timely fashion

Published: 2013-06-28


Last Updated: 2015-12-29


Applies To




A service related to a Guard1 product (see list below) fails to start after the system is rebooted.


The following error may be displayed:




The Windows System Event Log shows Event 7000 and Event 7009:



Services that may be affected:




Operating System and/or PC system resources are not yet available, or dependent/required service resources are not yet started when the affected service attempts to start.




When a service starts, the service communicates to the Windows Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds, after which the Service Control Manager ends the process.


On PCs with limited CPU or RAM resources, or where system resources are stressed by heavy workload (such as loading a significant number of background processes), the default SCM timeout may be insufficient.


Increase the SCM timeout period by following these steps:


  1. In Registry Editor, locate and right-click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
  2. Select New, then DWORD Value.
  3. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
  4. Right-click the ServicesPipeTimeout registry entry that you created in Step 3 and click Modify. The Edit DWORD Value dialog box appears.
  5. In the Value data text box, type a value (in milliseconds) for the SCM time-out period you want to set.
  6. Click OK.
  7. You must restart the computer for Service Control Manager to apply this change.


The service will now have a longer window to start, during which any required system resources should be able to come online.


If the issue persists, repeat the procedure and increase the timeout value in Step 5.

















Copyright © 2013-2016 TimeKeeping Systems, Inc.