This can also be done via an elevated command prompt using the sc
command. The syntax is:
sc config [service name] depend= <Dependencies(separated by / (forward slash))>
Note: There is a space after the equals sign, and there is not one before it.
Warning: depend=
parameter will overwrite existing dependencies list, not append. So for example, if ServiceA already depends on ServiceB and ServiceC, if you run depend= ServiceD
, ServiceA will now depend only on ServiceD. (Thanks Matt!)
Examples
Dependency on one other service:
sc config ServiceA depend= ServiceB
Above means that ServiceA will not start until ServiceB has started. If you stop ServiceB, ServiceA will stop automatically.
Dependency on multiple other services:
sc config ServiceA depend= ServiceB/ServiceC/ServiceD/"Service Name With Spaces"
Above means that ServiceA will not start until ServiceB, ServiceC, and ServiceD have all started. If you stop any of ServiceB, ServiceC, or ServiceD, ServiceA will stop automatically.
To remove all dependencies:
sc config ServiceA depend= /
To list current dependencies:
sc qc ServiceA
It does exactly what it says on the tin: the OS manages the size of the pagefile, which can shrink or grow dynamically. The lower and upper bounds are 1x your RAM size and 3x your RAM size or 4 GB (whichever is larger) as explained more elaborately here. The pro is that you don't have to worry about sizing your pagefile, the con is that your pagefile can become fragmented.
Where it is useful is in exactly the situation it's designed to avoid: sizing your pagefile. You can set it to System Managed and check in every several minutes (via a script), recording the smallest and largest sizes it uses over a typical usage period of a month or so. You should then have a very good idea how large to manually set your pagefile to be.
Best Answer
Delayed start has two major components:
This greatly reduces the slowdown in responsiveness in user sessions that the services might otherwise cause, because their disk I/O, CPU time, and pace of allocating RAM all ramp up at a more gradual slope than they would otherwise. It helps to avoid the classic "type password then wait 2 minutes" login that we all hate after a fresh boot.
It can also solve some problems if you have, for example, two high-I/O services. You can have one start automatically and the other delayed, or even both delayed, and they may start more smoothly than they would if both configured for Automatic start.
At the moment, it's not really configurable. You can sort of configure chains of service starts by making setting one as dependent on another, even if they technically aren't, i.e. make service 3 dependent on service 2, which is dependent on service 1, then set service 1 to delayed, so they will start in the order 1, 2, 3, once all the Automatic services have started.