Fix Exchange Server 2016 Services Not Starting After Reboot
Question details
Determine why Exchange Server 2016 services fail to start automatically after a reboot and restore service startup.

- Product
- Microsoft Exchange Server 2016
- Device & OS
- not provided
- Scenario
- An administrator restarts an Exchange server and expects its services to start automatically.
- Observed behavior
- Several Exchange services remain stopped after the reboot and require manual intervention.
Sign in to the Exchange server with an administrator account and identify the services that remain stopped after a reboot. Check whether the server can reach its domain controllers and DNS servers before investigating startup dependencies.
Start the affected Exchange services manually
Use this to restore stopped services while you investigate why automatic startup failed.
Press Windows+R, enter services.msc, and select OK.
Find each affected Microsoft Exchange service, right-click it, and select Start. Record any error message if a service fails to start.
Right-click each affected service, select Properties, and review its Startup type and Dependencies tab. Do not change startup types without confirming the service's documented requirements.

Check domain controller placement and connectivity
Investigate Active Directory availability and whether Exchange was installed on a domain controller.
Review the Exchange Server build
Use the installed build number and event logs to guide further troubleshooting and update planning.
Keep working on Office files with WPS Office
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for an easier migration. You can continue working on local documents during an Exchange outage, although WPS does not repair Exchange services or restore email connectivity.

Frequently Asked Questions
How can I start an Exchange service that is stopped?
Open Services by running services.msc, right-click the affected Microsoft Exchange service, and select Start. Record any error if it does not start.
How do I check whether Exchange is installed on a domain controller?
Run Get-CimInstance Win32_ComputerSystem | Select-Object Name,DomainRole in PowerShell. A DomainRole value of 4 or 5 indicates a domain controller.
Where can I find errors from the failed startup?
Open Event Viewer and check Windows Logs > System and Windows Logs > Application for errors recorded around the reboot time.
How do I find the Exchange Server 2016 build number?
Open Exchange Management Shell and run Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion. Compare AdminDisplayVersion with Microsoft's Exchange build-number documentation.




