What could cause Exchange 2019 services to not start automatically after a reboot, and are there any recommended startup order or dependency adjustments to ensure reliable service initialization?

Hi @Mote Jeffery

Thank you for posting your question in Microsoft Q&A. 

We understand you are trying to determine why your Exchange Server 2019 services are not starting automatically after a reboot. Based on my research, this issue may be caused by one or more of the following factors: 

Incorrect Startup Type Configuration 

Services may be set to Manual or Disabled instead of Automatic. (You have rechecked the service dependencies and confirmed that the startup type is set to "Automatic.")

Unavailable Dependency Services 

Required services may not be running or may fail to start in time. 

Corrupted Service Dependencies 

Misconfigured or broken service links can prevent proper initialization. 

Insufficient System Resources 

Limited CPU, memory, or disk space can delay or block service startup. 

User Permission Issues 

The service account may lack necessary privileges, such as Log on as a service rights. 

Corrupted Exchange Server Files 

Damaged or missing files can interfere with service execution. 

Anti-Virus or Firewall Interference 

Security software may block or delay Exchange-related processes. 

Registry Misconfigurations 

Incorrect registry values, especially for service startup types, can prevent automatic launching. 

You could try to follow these steps to troubleshoot it: 

1.Verify Sufficient System Resources 

Check system resources (CPU, RAM, Disk Space) to ensure there are no bottlenecks during startup. 

Use Task Manager (Ctrl + Shift + Esc) or Performance Monitor to assess usage. 

If resources are insufficient, consider upgrading hardware or closing unnecessary applications. 

2. Check Permissions and Accounts 

Open Services and check which account is used to run Exchange services (for example, domain or local system account). 

Verify the account has the necessary permissions, including Log on as a service rights. 

Adjust permissions via Local Security Policy or Active Directory for domain accounts. 

3.Run System Integrity Checks 

Open Command Prompt as Administrator and run:

sfc /scannow  

To repair sytem images, run:

dism /online /cleanup-image /restorehealth  

4.Check Event Logs 

Open Event Viewer (press Win + X, select Event Viewer). 

Navigate to Windows Logs > System and Applications. 

Look for relevant issues or warnings related to Exchange services and investigate any codes. 

5. Reconfigure Anti-Virus/Firewall Settings 

Temporarily disable any anti-virus or firewall software on the server. 

Attempt to restart the Exchange services and check if they start automatically after reboot. 

If the issue is resolved, configure exceptions for Exchange-related ports and processes in your security software. 

6. Check Registry Settings 

Open the Registry Editor (press Win + R, type regedit, and press Enter). 

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services  

Locate the keys related to Exchange services and verify the Start value is set to 2 (Automatic startup). 

Note: Modifying the registry can cause serious system issues. Always back up the registry before making changes. 

I hope this helps. 

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.