Windows Server error 1053: the service did not respond in a timely fashion

Published Sources checked By helps.wiki editorial team

Error 1053 is the Service Control Manager telling you a service did not respond to a start or control request in time. Check Event Viewer for the service's own error first, and only then consider raising the wait with the ServicesPipeTimeout registry value.

Applies to:Windows Serverall versionsWindowsall versions
On this page

What it means

The full message reads: "Error 1053: The service did not respond to the start or control request in a timely fashion." It is not a specific server fault. It is a general timeout from the Service Control Manager (SCM), the part of Windows that starts and controls services.

The SCM launches the service's process and waits for it to report that it is starting or running. If that report does not arrive within the SCM's limited wait, it gives up and shows 1053. The same error can appear when a stop, pause or other control request goes unanswered. The wait can be changed with the ServicesPipeTimeout registry value, described below.

Microsoft's developer documentation describes what a well-behaved service must do: register its control handler immediately, and if startup takes more than about a second, report either that it is running (accepting no controls yet) or that start is pending, with a wait hint and regular status updates. A service that skips this looks dead to the SCM, even if it is busy working.

Because the code is generic, the fix depends on why this particular service was slow or failed. Raising the timeout is a workaround, not a cure, so look for the cause first.

Symptoms and causes

You are likely dealing with this problem if:

  • A popup reading "Error 1053: The service did not respond to the start or control request in a timely fashion" when you start a service from services.msc.
  • The same failure from net start or Start-Service.
  • The service never reaches the Running state, sometimes right after patching or a reboot.
  • Service Control Manager entries in the System event log around the time of the failed start.

The usual causes, most common first:

Slow service startup
The service does too much work before it reports back (large database, slow disk, high CPU load, slow network or domain lookup) and exceeds the wait window.
The program does not follow the service protocol
It does long initialization in ServiceMain without reporting start-pending, or it is an ordinary console program registered as a service.
Security software, outdated components or wrong privileges
A Microsoft Q&A answer from 2016 about the Windows Defender service points to these. Treat it as specific to that case.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Find the real error in the event logs

Easy

The timeout hides the reason. The service's own log entries usually say what went wrong.

  1. Open Event Viewer and go to Windows Logs > System. Look for Service Control Manager entries from the time of the failed start.
  2. Check Windows Logs > Application for errors from the service's own program.
  3. Check the service's account and dependencies. Make sure the dependent services are running and the account has the rights it needs.
    Command Prompt
    sc qc <service name>

2.Restart the server and try again

Easy

A restart clears a stuck state left by a previous failed start or a pending update.

  1. Restart the server.
  2. Start the service again from services.msc.

3.Raise the service startup timeout (ServicesPipeTimeout)

AdvancedChanges settings

For a service that is legitimately slow to start, giving the SCM longer to wait avoids the false failure. It applies to every service on the machine, not just one.

Before you start: Registry edits can break the system. Create a restore point and export the registry key first. Raising the timeout can also hide a service that is genuinely failing, so use it only after checking the logs.

  1. Press WinR, type regedit and press Enter.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
  3. Create a new DWORD (32-bit) Value named ServicesPipeTimeout.
  4. Select Decimal as the base and enter the time in milliseconds: 60000 for 60 seconds, or 180000 for 3 minutes.
  5. Restart the computer, because the change takes effect only after a reboot.

4.Windows Defender service only: refresh definitions and related services

ModerateChanges settings

A Microsoft Q&A answer for error 1053 on Windows Defender suggested updating Defender and resetting related services. It is an old thread, so use it only for that service.

Before you start: The same answer also suggested removing other security software that may conflict. Only do that if you have another way to keep the server protected, and reinstall or replace it right away.

  1. Update the Defender definitions manually.
  2. Restart the BITS, Cryptographic Services and Windows Update services, then start Defender again.

5.If you wrote the service: follow the SCM protocol

Advanced

The Microsoft documentation says a service that initializes slowly must tell the SCM it is alive.

  1. Call RegisterServiceCtrlHandler immediately at the start of ServiceMain.
  2. During long initialization, report SERVICE_START_PENDING with a wait hint and call SetServiceStatus periodically with a checkpoint.
  3. Move heavy work to another thread, or report SERVICE_RUNNING with no accepted controls until you are ready.

Check that it worked

  • Start the service from services.msc or with net start and confirm it reaches Running without the 1053 message.
  • Restart the server and confirm the service starts on its own at boot.
  • Check the System event log for new Service Control Manager errors after the start.

If it still fails

  • Read the service's own application log and the vendor's documentation, since the real failure is probably inside the application.
  • Contact the software vendor with the Event Viewer entries from the failed start.
  • If a built-in Windows service fails, contact Microsoft support.

Questions

Does ServicesPipeTimeout apply to one service?

No. It is a system-wide setting for how long the SCM waits for services to connect, so it affects every service.

Sources

  1. Service ServiceMain FunctionOfficial · Microsoft Learn
  2. Changing the Service startup timeout (ServicesPipeTimeout) in Windows (CTX221996) · Citrix
  3. Error 1053 Q&A answer (Windows Defender) · Microsoft Q&A

Browse