Extending InControl (or other) service timeouts because of start failure after Windows reboot

Last modified on 26 Jan, 2023. Revision 5
Depending on many factors such as Windows version, disk speed, database size, installed memory and more, it is possible that some InControl services may not be able to start in time before Windows decides it has taken too long and cancels the service start-up.
Up to date for
Any version of InControl
Status OK
Peter Nilsson & Erik Holmlund


Sometimes after a system restart, Windows update etc. some of the InControl services do not start automatically and they have to be manually started afterwards. This is not desirable behavior and the problem has mainly been observed on Windows 10 (at this time). The solution to the problem is to configure Windows with either a delayed start of the service or extend the time-out for the application start-up by adding a registry entry in Windows that controls this.


An excellent guide was written by CodeTwo on how to perform either of these changes, the article can be found at the following location:


A short summary

Solution-1: Delay the automatic start of the service application(s). Such as InControl server, ILA and/or Log receiver. This can be done by opening the properties options on the service.

Solution-2: Increase the timeout value for the service startup by adding a new property to the Windows registry in the following location:


The new entry should be a DWORD (32-bit) called ServicesPipeTimeout (it is not an existing object as you need to create a new entry with this name). Change Base to Decimal and give it a vale of e.g. 240000 ms (4 minutes). Save changes + restart the machine. The time-out can be extended further if needed.

Please see the link to the KB article for more details if needed.

Related articles

No related articles found.