
In order to change the delay applied to Automatic (Delayed Start) services, simply create the following registry key via the Windows Registry Editor. On fast hardware, this might just be too long to wait. The default delay is 120 seconds (2 minutes). One of the side effects of Automatic (Delayed Start) services is that they do start later in the boot cycle. You can also edit the default Service Definition template and make the Startup Mode Automatic for all new services that you create. You can, of course, change the Startup Mode to Automatic when you configure your FireDaemon Pro service if you want to. This change was made intentionally given that FireDaemon Pro services are not critical to the successful boot of the operating system and ideally they should start later in the boot cycle.

When you create a FireDaemon Pro service, the default Startup Mode is now Automatic (Delayed Start). You can find a reasonable (but older) discussion of this and other changes Microsoft made to optimise the boot process. The idea behind this was to delay the start of non-essential services in order to minimise the overall boot time of the operating system. In order to speed up the Windows boot process, Microsoft introduced Automatic (Delayed Start) Windows Services. How to adjust the Automatic (Delayed Start) services delay time at system boot

Modified on: Mon, 26 Sep, 2022 at 6:01 PM Solution home Frequently Asked Questions Technical FAQs Adjusting the Automatic (Delayed Start) services delay time at system boot
