STATUS_DOMAIN_LIMIT_EXCEEDED (0xC00000E1) on Windows Server

You're setting up a new domain trust or trying to join a server to a second domain, and boom — STATUS_DOMAIN_LIMIT_EXCEEDED (0xC00000E1). This usually hits in a lab, a branch office, or during a migration where someone didn't read the fine print. The trigger? You're running Windows Server Standard Edition. It only supports one domain per server. The moment you try to add a second domain, either as a trust partner or a domain join target, the OS slams the door.

Why This Happens

Microsoft locks domain participation by edition. Server Standard? One domain. Server Datacenter? Unlimited. That's the rule since Windows Server 2012 R2. The error 0xC00000E1 is the OS telling you — Sorry, you hit the limit. It's not a glitch. It's a license check. The NT kernel enforces this at the security subsystem level. So don't waste time checking DNS, firewalls, or AD replication. The culprit here is almost always the edition.

The Fix — Step by Step

Step 1: Identify Your Server Edition

Run this in an elevated command prompt or PowerShell:

systeminfo | findstr /C:"OS Name"

You'll see something like Microsoft Windows Server 2019 Standard. If it says Standard, you found the problem.

Step 2: Check Your Current Domain Setup

Look at what domains the server is already handling. If it's a domain controller, it's serving one domain. If it's a member server, check its trust relationships:

nltest /domain_trusts

If this shows more than one domain, that's your issue.

Step 3: Decide Your Path

You have three real options. Pick one:

• Upgrade to Datacenter Edition. This removes the limit entirely. You'll need a new license. Do an in-place upgrade using the setup ISO for Datacenter. Reboot, and the error vanishes.
• Move the extra workload to another server. If you have another Standard license, run a second VM or physical box for the second domain. Then break the trust or domain membership on the first server.
• Consolidate to a single domain. If you don't truly need two domains, merge them. That means decommissioning one trust or migrating resources. Painful but works.

Step 4: Apply the Fix

Let's say you upgrade. Here's the quick route:

1. Get the Datacenter ISO for the same Windows version (e.g., 2019 -> 2019 Datacenter).
2. Mount the ISO or insert the DVD.
3. Run setup.exe from the source.
4. Choose Install, then Keep personal files and apps (this upgrades the edition in place).
5. Enter your Datacenter key when prompted.
6. Reboot. Check the edition with systeminfo again.

If you choose option 2 (move to another server), just unjoin the server from the second domain or remove the trust. Use Server Manager or:

netdom trust /remove

If It Still Fails

Two things to check. First, make sure the upgrade actually took. Run systeminfo and confirm the edition changed. Second, look for leftover trust objects in AD. Sometimes a trust is removed locally but the AD object sticks around. Use Active Directory Domains and Trusts to delete any orphaned trusts. Also verify the server isn't somehow still referencing the second domain in a script or service account. Reboot after cleaning up. If the error persists, you might be dealing with a corrupt security database — then a clean reinstall of the server OS is your last resort.