# Windows Service Manager Timeout

On a Microsoft Windows architecture machine, the Windows Service manager has a hard time limit to get all services started. In some circumstances on a reboot, the machine might be busy and unable to achieve this goal, leaving the Agilicus Connector unstarted.

The Agilicus Connector has a watchdog to workaround this issue, with a default time of 300 seconds. In the event your individual server is even slower than this, you can change the Windows Registry key AutoStartDelay (using regedit) at

```
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\agilicus-connector-watchdog
```

![Windows Service Manager Timeout Error: Troubleshooting and Solutions - Image shows the Windows Services Manager with a service highlighted and a timeout error message displayed. Learn how to resolve Windows service timeout issues and increase startup time with our comprehensive guide.](https://www.agilicus.com/www/3c78f618-image-1024x686.png)    You may not have this watchdog installed, if not, you can manually enable it with:

```
"C:\Program Files\agilicus\agent\agilicus-agent.exe" client --force-install-connector-watchdog --cfg-file "C:\Program Files\agilicus\agent\agent.conf.enc.yaml"
```