Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is the difference between Automatic and Automatic (Delayed Start) for a property setting for a Windows service? i.e. what do I gain or lose by setting my service as one or the other?

Running the service on Windows Server 2008 x64

share|improve this question

migrated from May 19 '11 at 9:29

This question came from our site for professional and enthusiast programmers.

up vote 59 down vote accepted

A service marked as Automatic (Delayed Start) will start shortly after all other services designated as Automatic have been started. In my experience, this means that they are started 1-2 minutes after the computer boots.

The setting is most useful in lessening the "mad rush" for resources when a machine boots.

Note that when you have 20 services all being started at the same time, each will start up slower as it competes with the others for slices of the machine's precious resources (CPU/RAM/Disk/Network). That is, each service takes longer to become available!

If you have a few services that are critical, then you may want to set those few to Automatic and set as many of the others as you can to Automatic (Delayed Start). This will ensure that the critical services get the most resources early and become available sooner, while the non-critical services start a bit later (which by definition is ok).

share|improve this answer
Indeed, after handling the Non-Delayed Start services it will queue a worker thread which has a default delay of 120 seconds, which can be overridden by the AutoStartDelay value in HKLM\SYSTEM\CurrentControlSet\Control. When this worked thread runs the Delayed Start services are handled and when they are done the SCM signals the event \BaseNamedObjects\SC_AutoStartComplete... – Tom Wijsman May 20 '11 at 23:05

From my understanding, it's simply a delay before launching the service.

Later versions of Windows introduced this to ensure that they didn't trip over each other's feet during the boot process (having a gazillion processes starting up at the same time is not conducive to performance).

The documentation for this feature states that services marked thus will be started "shortly after boot", hopefully once the boot-time-required services have settled down a little.

share|improve this answer

Here's an example. I have a SonarQube service that depends on my MySQL database service. So, I set the MySQL service to automatic to get the database up and running when the machine boots. I have the SonarQube service set to the automatic (delayed) start to make sure it starts up AFTER the database service it depends upon is started.

If you have a dependency like this it can be helpful to use the delayed start to make sure dependent services start up in the right order.

share|improve this answer

This is also used when you want to delay the start of a service to allow other services to start completely, such as the SCCM Client, which does a delayed start to allow the WMI service to start fully as it is dependent on it being fully up and running.

share|improve this answer

This is mostly used for services that starts on with AD accounts. If the service is trying to start before the server has network connection to contact the DC, it will fail and sometimes the system gets stuck and gets unreachable.

The delay ensures the service will start once network connection is up in order to use the AD account for it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.