| Previous | Next |
| ERROR_INVALID_SERVICE_CONTROL | ERROR_SERVICE_NO_THREAD |
ERROR_SERVICE_REQUEST_TIMEOUT
ERROR_SERVICE_REQUEST_TIMEOUT (1053, 0x0000041D) means that the Service Control Manager did not receive the required response while starting a service or delivering a control request.
What the timeout usually means
When Windows starts a service process, it expects that process to call StartServiceCtrlDispatcher promptly. A timeout can mean that the service process did start but did not connect to the Service Control Manager, or that the dispatcher thread is blocked while a control handler is running.
Control notifications are processed serially by the Service Control Manager. A handler that performs lengthy work directly can therefore delay unrelated start or control requests and make them fail with this code. The handler should hand off long work to another thread and return quickly.
How to investigate
- Check the System event log and the service's own log for the first failure, rather than treating 1053 as the root cause.
- Use QueryServiceStatusEx to inspect the current state, wait hint and checkpoint while the service is starting or stopping.
- For a slow but otherwise healthy service, confirm that initialization reports progress correctly. Increasing
ServicesPipeTimeoutcan be a temporary workaround, but it should not hide a deadlock or a blocked control handler.
See also: Microsoft guidance for slow service startup.
Looking for a different code? Search another status or error code.