How to Fix “Windows Could Not Start Active Directory Web Services on Local Computer” Error

Some Windows users encounter the “Windows could not start Active Directory Web Services on Local Computer” error while attempting to start ADWS from the Services console or during Active Directory-related operations. In most cases, the error prevents administrators from managing domain services properly and may affect tools like Active Directory Administrative Center, PowerShell AD modules, and remote administration features.

Active Directory Web Services (ADWS) is an important Windows service that enables communication between Active Directory and management applications. If the service fails to start, it is usually caused by corrupted Active Directory components, disabled dependencies, DNS issues, damaged system files, improper service configuration, or failed Windows updates.

Fortunately, there are several ways to troubleshoot and fix this issue on Windows Server and supported Windows environments. In this guide, we will walk you through all the effective solutions step by step.

How to Fix “Windows Could Not Start Active Directory Web Services on Local Computer” Error

1. Restart the Server or Computer

Temporary service glitches or incomplete background processes can sometimes prevent Active Directory Web Services from starting correctly.

1. Open the Start menu.
2. Click the Power button.
3. Select Restart.
4. Wait for the system to reboot completely.

After restarting, try starting the service again.

1. Press Windows + R.
2. Type services.msc and press Enter.
3. Locate Active Directory Web Services.
4. Right-click the service and select Start.

If the service still fails to start, continue with the next method.

2. Verify Active Directory Domain Services Is Running

ADWS depends on Active Directory Domain Services (AD DS). If AD DS is not running properly, ADWS may fail automatically.

1. Open the Services window.
2. Locate Active Directory Domain Services.
3. Check whether the service status is listed as Running.
4. If the service is stopped, right-click it and select Start.
5. Restart the Active Directory Web Services service afterward.

You should also ensure that the server is properly configured as a domain controller.

3. Check the ADWS Service Startup Type

An incorrect startup configuration can prevent the service from launching automatically.

1. Press Windows + R.
2. Type services.msc and press Enter.
3. Double-click Active Directory Web Services.
4. Set the Startup type to Automatic.
5. Click Apply.
6. Select Start.
7. Click OK.

After changing the startup type, restart your server and check whether the service works correctly.

4. Check Dependency Services

ADWS relies on several Windows services to function properly. If a required dependency is disabled, the service may fail to start.

1. Open the Services console.
2. Double-click Active Directory Web Services.
3. Switch to the Dependencies tab.
4. Verify that all listed services are running.

Common dependency services include:

• Remote Procedure Call (RPC)
• Windows Event Log
• Active Directory Domain Services

5. Start any stopped dependency service.
6. Try starting ADWS again.

5. Run System File Checker (SFC)

Corrupted Windows system files can interfere with Active Directory services.

1. Open Command Prompt as administrator.
2. Run the following command:

sfc /scannow

3. Wait for the scan to complete.
4. Restart the server after the repair process finishes.

The SFC utility automatically repairs damaged system files that may affect ADWS.

6. Run the DISM Tool

If SFC cannot repair all corrupted files, you should use DISM to repair the Windows image.

1. Open Command Prompt as administrator.
2. Run the following command:

DISM /Online /Cleanup-Image /RestoreHealth

3. Wait for the repair process to complete.
4. Restart the computer afterward.

DISM repairs deeper Windows component corruption that may prevent services from starting.

7. Check DNS Configuration

Improper DNS settings are a common cause of Active Directory-related service failures.

1. Press Windows + R.
2. Type ncpa.cpl and press Enter.
3. Right-click your active network adapter.
4. Select Properties.
5. Double-click Internet Protocol Version 4 (TCP/IPv4).
6. Verify that the preferred DNS server points to the domain controller or internal DNS server.
7. Click OK to save the settings.

After updating DNS settings, restart the server and test the service again.

8. Review Event Viewer Logs

Event Viewer can provide detailed information about why ADWS is failing.

1. Press Windows + X and select Event Viewer.
2. Expand Windows Logs.
3. Open the System and Application sections.
4. Look for errors related to:
   • Active Directory Web Services
   • NTDS
   • DNS
   • Service Control Manager
5. Review the error details and event IDs carefully.

The logs may help identify missing dependencies, authentication issues, or corrupted components.

9. Reinstall Active Directory Web Services Components

If the service files are corrupted, reinstalling Active Directory services may help.

1. Open Server Manager.
2. Select Manage > Remove Roles and Features.
3. Locate Active Directory Domain Services.
4. Remove the role carefully if appropriate for your environment.
5. Restart the server.
6. Reinstall the role afterward.

This process should only be performed after backing up important Active Directory data.

10. Install Pending Windows Updates

Outdated Windows Server builds may contain bugs affecting Active Directory services.

1. Open Settings.
2. Navigate to Windows Update.
3. Click Check for updates.
4. Install all available updates.
5. Restart the server.

Keeping the server updated helps maintain service stability and compatibility.

Conclusion

The “Windows could not start Active Directory Web Services on Local Computer” error is usually caused by dependency failures, corrupted system files, DNS configuration problems, or damaged Active Directory components. In most cases, restarting dependency services, repairing system files, checking DNS settings, or updating Windows successfully resolves the issue.

If the problem persists after trying all the methods above, you may need to perform deeper Active Directory diagnostics or restore the server from a healthy backup. Regular maintenance, proper DNS configuration, and timely Windows updates can help prevent similar ADWS-related issues in the future.