SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Windows New Added 26 September 2026

Error 1053: The service did not respond to the start or control request

A service has about 30 seconds to report back to the service control manager, and the process either failed before doing so or spent that time on startup work. A console application installed as a service never reports at all, which is why it runs perfectly from a command prompt and times out as a service.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
# 1053 is only the timeout, the real error is in the event log
Get-WinEvent -LogName Application -MaxEvents 20 |
  Where-Object { $_.LevelDisplayName -eq 'Error' } | Format-List TimeCreated, Message

# Run the binary interactively as the service account to see it fail
sc.exe qc MyService              # binary path, account, dependencies
Get-Service MyService | Select-Object Name, StartType, Status

# A missing runtime, or a config path relative to the wrong directory,
# is the usual cause: services start in C:\Windows\System32
# .NET: BackgroundService.ExecuteAsync must not block StartAsync
# Node and Java wrappers (node-windows, procrun) report readiness for you

# Widen the timeout only once the slow startup is genuinely necessary
# HKLM\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout (DWORD, milliseconds)

# Then confirm it starts and stays up
Start-Service MyService; Get-Service MyService

How to diagnose Windows errors

Windows errors surface as numeric codes that mean little on their own, but the operating system keeps detailed logs that almost always contain the real cause. Two categories dominate developer machines: missing Visual C++ redistributables (a DLL-not-found error for a runtime the application assumed was present) and architecture or dependency mismatches (the 0xc000007b family, usually a 32-bit/64-bit mix).

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Read Event Viewer under Windows Logs → Application and System, filtered to the time of the failure. The numeric code in the dialog maps to a detailed entry there.
  2. For MSI failures, install with verbose logging: msiexec /i package.msi /l*v install.log, then search the log for "Return value 3". The lines just above name the failing action.
  3. For missing DLLs, install the matching Visual C++ Redistributable and confirm the architecture matches the application (x64 versus x86).
  4. Repair system corruption with sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth, in that order.
  5. For access-denied errors, check both NTFS permissions and whether the process needs elevation; UAC virtualisation can make writes appear to succeed while landing elsewhere.

Tools worth reaching for

  • Event Viewer
  • msiexec /l*v
  • sfc /scannow
  • DISM /RestoreHealth
  • Process Monitor (ProcMon)

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

learn.microsoft.com learn.microsoft.com

Related Windows errors

See all 20 Windows errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.