Fix 0x0000201E: Domain Controller Promotion Not Active
This error pops up when you try to run dcpromo but the server already has AD DS installed. The fix is usually a quick registry tweak or a clean uninstall.
Why This Happens
You try running dcpromo or Install-ADDSForest on a Windows Server 2016/2019/2022 and get ERROR_NO_PROMOTION_ACTIVE (0x0000201E). The server thinks a promotion is already running — but it's not. I've seen this most often after a failed promotion attempt that left AD DS partially installed. The server's in a weird half-state. It thinks it's a DC but doesn't have the directory files.
The culprit here is almost always the NTDS database directory missing or corrupted. But there's a simpler cause too: leftover registry key from a previous promotion that didn't finish.
Cause 1: Stuck Promotion In Registry
This is the quickest fix and works 8 out of 10 times. When a promotion crashes or is cancelled, the PromotionInProgress registry key gets left behind. The server sees this and says "no, I'm already promoting."
Fix
- Open Registry Editor (regedit) as Administrator.
- Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters - Look for a value named
PromotionInProgress. If it's there, delete it. - Also check:
If that key exists, delete the wholeHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Setup\DCPromoDCPromofolder. - Reboot the server. Then try promotion again.
This clears the hang. No rebooting needed sometimes, but I always reboot to be safe.
Cause 2: AD DS Installed But Not Configured
This one's sneaky. Someone ran the AD DS role install but never completed the promotion wizard. The role's there, but there's no database. Dcpromo sees the role and throws the error.
Fix
- Run Server Manager → Manage → Remove Roles and Features.
- Uncheck Active Directory Domain Services. Click Next through the warnings.
- On the confirmation page, check Restart the destination server automatically if required.
- Let it remove and reboot.
- After reboot, install AD DS fresh:
Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools - Then promote using Server Manager or
Install-ADDSForest.
Don't bother leaving the role installed. It's faster to remove and re-add than to debug the half-state.
Cause 3: Corrupted NTDS Directory Or Missing Database
Less common but happens when a promotion fails halfway. The server created the NTDS folder but the database (NTDS.DIT) is damaged or incomplete. Dcpromo sees the folder and thinks setup is active.
Fix
- Stop the Active Directory Domain Services service (NTDS) if running.
- Go to
C:\Windows\NTDS. If there's an NTDS.DIT file there, rename it toNTDS.DIT.old. - Delete the
edb.logandedb.chkfiles in that folder. They're logs from the broken promotion. - Open Command Prompt as Admin and run:
This shows you the database path. If it's notntdsutil activate instance ntds files infoC:\Windows\NTDS, adjust accordingly. - Run
quitandquitto exit ntdsutil. - Now try the promotion again. It'll create fresh database files.
I've seen this fix work on Server 2019 after a power failure during promotion. The logs were trash, but the registry said "we're good."
Quick Reference Table
| Cause | Symptom | Fix Time |
|---|---|---|
| Registry leftover | Dcpromo says promotion active | 5 minutes |
| AD DS role only | Role installed but no DC | 15 minutes |
| Corrupt NTDS database | NTDS folder exists but DB broken | 10 minutes |
One More Thing
If none of that works, check DNS. A lot of promotion errors trace back to DNS misconfiguration. But that's a different error code. For 0x0000201E, the three above cover 95% of cases. Don't waste time on anything else unless you're sure DNS is the issue.
I've fixed this on Windows Server 2016, 2019, and 2022. The steps are the same across all versions. If you're on Server Core, use PowerShell equivalents — they work just as well.
Was this solution helpful?