How to Fix Error 1053: The service did not respond to the start or control request in a timely fashion
Error message
Windows could not start the <service> service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.
If you're seeing "Error 1053: The service did not respond to the start or control request in a timely fashion", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
Windows started the service process and waited 30 seconds for it to report Running, but it never did. The Service Control Manager gave up.
Why this happens
Service code crashes during startup, missing dependency or DLL, wrong .NET runtime, hung database/network call during init, or the service host process needs more time than the default timeout.
Step-by-step fix
Check Event Viewer → Windows Logs → Application and System for events around the failure timestamp. The exception reason is usually there.
Confirm any dependencies the service needs are installed and started (database, .NET version, files in the install folder).
If the service is legitimately slow to start, raise the SCM timeout (machine-wide).
commandNew-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control' -Name 'ServicesPipeTimeout' -Value 60000 -PropertyType DWord -Force Restart-ComputerRun the service binary directly (not via SCM) to capture stdout/stderr.
Affected products
Windows Admin
Still broken? Try these
- If it's a custom .NET service, attach a debugger or add startup logging before the first slow call.
- Check for antivirus locking the service binary on startup.
- Verify the service account has 'Log on as a service' rights and isn't locked out.
Related errors
Frequently asked questions
What does "Error 1053: The service did not respond to the start or control request in a timely fashion" mean?
Windows started the service process and waited 30 seconds for it to report Running, but it never did. The Service Control Manager gave up.
What causes "Error 1053: The service did not respond to the start or control request in a timely fashion"?
Service code crashes during startup, missing dependency or DLL, wrong .NET runtime, hung database/network call during init, or the service host process needs more time than the default timeout.
How do I fix "Error 1053: The service did not respond to the start or control request in a timely fashion"?
1. Check Event Viewer → Windows Logs → Application and System for events around the failure timestamp. The exception reason is usually there. 2. Confirm any dependencies the service needs are installed and started (database, .NET version, files in the install folder). 3. If the service is legitimately slow to start, raise the SCM timeout (machine-wide). 4. Run the service binary directly (not via SCM) to capture stdout/stderr. Always test changes in a non-production environment first.
Browse more errors in Windows Admin: Fix Windows administration errors. Access denied, RPC server unavailable, trust relationship failures, Group Policy errors, and network path issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.