Exchange Service Error 1068: IT Administrator’s Guide for 2026
User Query: Our Exchange Server services suddenly stopped working after a Windows update. When I try to start the Microsoft Exchange Transport service, it shows ‘Error 1068: The dependency service or group failed to start.’ Emails are no longer flowing, and users cannot send or receive messages. How can I fix Exchange Server Error 1068 without affecting my mailbox data?
Introduction: Microsoft Exchange Server depends on several Windows services to run properly. If one of these required services fails, Exchange may stop working and display Exchange Service Error 1068: The dependency service or group failed to start. This error usually appears due to several reasons. As a result, important Exchange services such as Transport, Information Store, or Frontend Transport may fail to start. This blog explains the manual method for a hassle-free recovery. Also, use the DRS Softech Exchange Server Backup Tool to backup your important data before performing any step.
What is the Exchange Service 1068 Error?
Error 1068: Exchange Service is a Windows service dependency error. It means the Exchange service you are trying to start depends on another Windows service that is currently stopped, disabled, or unable to start. Instead of starting normally, Windows displays:
- Windows could not start the service.
- Error 1068: The dependency service or group failed to start.
- Until the missing dependency is restored, the Exchange service will remain unavailable.
Common Symptoms of Exchange Server Error 1068
- Microsoft Exchange services fail to start.
- Outlook cannot connect to Exchange.
- Users cannot send or receive emails.
- Exchange Admin Center becomes inaccessible.
- Event Viewer records multiple service-related errors.
- Exchange Health Checker reports failed services.
Possible Solutions to Fix Exchange Service Error 1068
If you’re seeing Exchange Error 1068: The dependency service or group failed to start, don’t panic. In most cases, the issue can be resolved by checking Windows services, Exchange health, or server resources. Follow the solutions below one by one until the problem is fixed.
1st Solution: Check and Start the Required Exchange Services
- Press Windows + R, type services.msc, and press Enter.
- Locate the Exchange services that are stopped.
- Right-click each service and select Properties.
- Set the Startup Type to Automatic.
- Click Start if the service is not running.
- Restart the server and verify whether the issue is resolved.
2nd Solution: Check the Dependent Services
- First, open Services (services.msc) and right-click the Exchange service that is failing.
- Now, select Properties and open the Dependencies tab.
- Check whether all the listed services are running.
3rd Solution: Review the Event Viewer Logs
- Press Windows + R, type eventvwr.msc, and press Enter.
- Go to Windows Logs > System.
- Look for recent Error or Warning events related to Exchange or the Service Control Manager.
- Open the event details to identify which service failed.
4th Solution: Check the Health of Your Exchange Server
- Open the Exchange Management Shell and run:
- Get-ServerHealth -Identity <ServerName> | Format-Table Server,CurrentHealthSetState,Name,HealthSetName,AlertValue,HealthGroupName -Auto
- Replace <ServerName> with the name of your Exchange Server.
- The command displays the health status of Exchange services and highlights any components reporting errors or warnings.
5th Solution: Verify Server Resources
- Low system resources can also prevent Exchange services from starting.
- Check the following: Available CPU usage, Free RAM, Disk space on the system drive, Free space on Exchange database and log drives.
- If the server is running low on resources, free up disk space, stop unnecessary applications, or increase available storage before trying to start the Exchange services again.
6th Solution: Review Recent Changes on the Server
- If the error appeared recently, think about what changed before the problem started.
- Check for: Windows Updates, Exchange Updates, Newly installed software, Antivirus changes, Security policies, Firewall modifications, and Configuration changes made by administrators.
7th Solution: Rebuild the Exchange Server (Last Option)
You can then reinstall Exchange using Recovery Mode to restore the server while preserving its configuration.
Note: Rebuilding an Exchange Server should only be considered after all other troubleshooting methods have failed. If you’re managing a production environment, it’s recommended to perform this task during a maintenance window or with assistance from an experienced Exchange administrator.
Backup Your Exchange Server Data Before Troubleshooting
The DRS Softech Exchange Server Backup Tool is a quick, reliable, and hassle-free solution. It allows users to backup your emails, contacts, calendars, and attachments with no data loss. This tool preserves the original email formatting, structure, and metadata during the entire process. Offer several features, like Remove Duplicates, Date Filter, Custom Folder Name, Skip Existing Exports, and more. The demo version of this tool is available to test its features and functions.
Simple Steps to Backup Exchange Emails and Data
- Download and install the Exchange Server Backup & Restore Tool. Click Backup and Continue.

- Use Modern Authentication/Admin Impersonation or Client Secret ID to Sign In.

- Select Backup option (Primary, Online Archive, Public Folder). Tick the Source User ID to backup. Press Next.

- Preview and select the emails, contacts, calendars, and attachments to backup.
- Choose Saving Format as per your needs (File Formats or Email Clients).

- In the end, apply features and filters, such as Date Filter, Fast Mode, and more. Press Backup.

Conclusion
Exchange Service Error 1068 is mainly caused by failed or stopped dependency services in Windows. In most cases, the issue can be resolved by using different manual methods. It includes checking and starting the Exchange service, checking the dependent service, verifying server sources, and more. Also, take a backup of your important emails with the help of the DRS Softech Exchange Server Backup Tool. You can download the demo version of this tool to understand its features and performance.
Frequently Askes Questions
Ans. You can fix Exchange Service Error 1068 by checking and starting required Windows services, verifying service dependencies, and ensuring all Exchange-related services are set to Automatic. Also review Event Viewer logs to identify the exact failing service.
Ans. The most commonly affected services include: Transport, Information Store, Frontend Transport, and Active Directory Topology. These services often fail when a dependency service is stopped or disabled.
Ans. Yes, restarting Windows can sometimes fix the issue temporarily. A reboot restarts stopped dependency services automatically, which may allow Exchange services to start normally again. However, it does not fix the root cause.
Ans. You should check key dependency services such as:
1. Remote Procedure Call (RPC)
2. Windows Event Log
3. Windows Management Instrumentation (WMI)
4. IIS (World Wide Web Publishing Service)
5. Net.TCP Port Sharing Service
Ans. A corrupted Exchange database (EDB) may prevent services like Information Store from starting properly, which can trigger dependency failures and result in Error 1068.
Ans. Yes. Incorrect DNS settings can prevent Exchange from communicating with Active Directory. This can lead to failed service dependencies and trigger Error 1068 during startup.
Ans. No, this error does not directly corrupt mailbox data. It only affects service startup. However, if the issue is not resolved and services remain down for a long time, mailbox accessibility may be impacted.
Ans. Yes. If the root cause is related to Active Directory, DNS, or shared dependency services, multiple Exchange servers in the same environment can be affected at the same time.
Ans. The best approach is a step-by-step troubleshooting process:
1. Start the required Windows and Exchange services
2. Check service dependencies
3. Review Event Viewer logs
4. Verify server resources and network/DNS health
5. Run Exchange health checks using PowerShell