In order to speed up the Windows boot process Microsoft introduced Automatic (Delayed Start) Windows Services. 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. You can find a reasonable (but older) discussion of this and other changes Microsoft made to optimise the boot process.
When you create a FireDaemon Pro 4 service, the default Startup Mode is now Automatic (Delayed Start). We made this change intentionally given that FireDaemon Pro services are definitely not critical to the successful boot of the operating system and ideally they should start later anyway in the boot cycle. You can, of course, change the Startup Mode to Automatic when you configure your FireDaemon Pro service if you want to.
One of the side effects of Automatic (Delayed Start) services is that they do start later in the boot cycle. The default delay is 120 seconds (2 minutes). On fast hardware, this might just be too long to wait. In order to change the delay applied to Automatic (Delayed Start) services, simply create the following registry key via the Windows Registry Editor.
It's of type REG_DWORD. Set the value of the key to the desired delay in milliseconds (eg. 60000 for one minute). You might need to reboot for the change to take effect. Remember this change affects all Automatic (Delayed Start) services.
If you want to granularly delay FireDaemon Pro service startup, in FireDaemon Pro 4.5 in the Scheduling Tab you can apply an Overall Launch Delay to the service when it starts. This means specific FireDaemon Pro services can be delayed further during operating system boot-up (i.e. 120 seconds + n x additional seconds). Alternately, you can change the FireDaemon Pro Startup Mode to Automatic and then set the Overall Launch Delay meaning your application will start much earlier in the operating system boot cycle yet not immediately at boot (i.e 0 seconds + n x additional seconds).