This article outlines the differences between Automatic and Automatic (Delayed Start) for Windows Services. By setting non-essential services to Automatic (Delayed Start), you can optimize your system’s boot time and improve performance during start-up.
- Automatic Start
- Behavior: Services set to Automatic start immediately during the system boot process.
- Timing: These services are loaded early in the boot sequence, often before the user logs in.
- Use Cases: Essential services that are critical to the functioning of the operating system, such as networking, security, and system utilities.
- Impact: Since these services start during the boot sequence, they can increase boot time, especially if there are many Automatic services.
- Automatic (Delayed Start)
- Behavior: Services set to Automatic (Delayed Start) start shortly after the boot process is complete.
- Timing: These services wait until other core services and tasks have finished loading. The default delay is about 2 minutes after the system has booted.
- Use Cases: Services that are not immediately required for system functionality, such as non-critical background services or maintenance tasks.
- Impact: Reduces the initial boot time by spreading out the load. This helps the system become responsive faster after start-up.
Key differences
|
Feature |
Automatic |
Automatic (Delayed Start) |
|
Startup Timing |
Immediate during boot |
Delayed (typically ~2 minutes) |
|
Priority |
Higher priority |
Lower priority |
|
Boot Time Impact |
Can increase boot time |
Reduces initial boot time |
|
Use Case |
Essential system services |
Non-critical services |
Example
- Automatic: A service like Windows Defender Antivirus Service needs to start immediately to protect your system from potential threats during boot.
- Automatic (Delayed Start): A service like Windows Update or Background Intelligent Transfer Service can safely start a bit later since they aren't critical during the initial boot phase.
Related Articles
From v11.11.1, the service-startup type for lmgrd is set to Automatic (Delayed Start) in the Windows Services Manager. 3Number of Views How do the lmgrd and lmdown Processes Work to Start and Stop vendors on Windows? 9Number of Views Unable to stop FNMEA services in the Windows Services 12Number of Views Reasons for lmgrd Service not Getting Started 25Number of Views Lost connection to lmgrd, heartbeat timeout expired, exiting. EXITING DUE TO SIGNAL 37 Exit reason 5 15Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago