Status: Closed (View Workflow)
Currently the service starts in the "Automatic" mode, so there can be conflicts with other services like login service, shared directory mappers, etc. "Automatic (Delayed start)" could resolve this issue by allowing other services to start before Jenkins master/slave starts the initialization.
The change requires https://github.com/kohsuke/winsw/releases/tag/winsw-1.17 at least (not merged into Jenkins core)
- is duplicated by
JENKINS-43575 Windows service agents and master should use the delayed start option
Most people probably don't use UNC paths for storage - and then you are impacting the majority of users with a slow startup to fix the minority of users.
If you want to fix 80% of the minority without impacting the majority you could just depend on the "workstation" service.
Anyone that wants anything more complex can suck it themselves.
 based on nothing other than gut feeling and finger in the air - and that we still have huge amount of users that run builds on master!
teilo After some reconsideration I have decided not to enable it by default, but to provide a proper feature in WinSW: https://github.com/kohsuke/winsw/pull/205 . So anyone will be able to enable it if he wants.
Would it work for you?
Closing as Resolved. The option is there since 2.60, but it is an opt-in behavior
I still think that a default delayed start would be preferable for users, who would like to get a working infrastructure out-of-the-box. All service configuration steps may require much time from users, who have no appropriate qualification.