Fix ERROR_DS_FOREST_VERSION_TOO_LOW 0X00002175

This error hits when you try to add a domain controller with a newer Windows Server version into an older AD forest. The fix is raising the forest functional level.

When this error pops up

You're trying to promote a new domain controller running Windows Server 2022 into an existing forest. You run DCPROMO or PowerShell's Install-ADDSDomainController, and bam — you get error 0X00002175 with the message "ERROR_DS_FOREST_VERSION_TOO_LOW." The promotion fails outright. This happens a lot when you're migrating from an older environment like Windows Server 2008 R2 or 2012 R2 to something newer.

The culprit here is almost always the forest functional level. That's the version flag for your whole AD forest. If it's set below what the new server supports, the promotion won't let you in. Windows Server 2022 needs at least Windows Server 2016 forest functional level. Same goes for Server 2019 — it needs 2016 or higher.

Root cause

Active Directory forest functional level controls what features are available across all domains. Each Windows Server version has a minimum functional level for joining the forest. Microsoft locks this down intentionally — it's their way of keeping your infrastructure consistent. The error code 0X00002175 translates to "the forest version is too low to accept this domain controller."

Don't bother checking individual domain functional levels first. They can be lower than the forest level, but the forest level is the gatekeeper here. Also skip any DNS or replication troubleshooting — this isn't a connectivity issue.

The fix — step by step

You need to raise the forest functional level. Then run adprep on the schema master. Here's how:

Check current forest functional level. Log in to any domain controller or management machine with Domain Admin rights. Open Active Directory Domains and Trusts. Right-click Active Directory Domains and Trusts, then choose Raise Forest Functional Level. The dialog shows you the current level. Write it down.
Determine the target level. For the new DC to join, the forest must be at least:
- Windows Server 2016 for Server 2019 or 2022
- Windows Server 2012 R2 for Server 2016
I always push to the highest the new DC supports. You can't go back, so pick wisely.
Run adprep /forestprep. On the schema master domain controller (usually the first one built), open PowerShell or Command Prompt as admin. Insert the new server's installation media or mount an ISO. Navigate to \support\adprep folder. Run:
```
adprep /forestprep
```
Confirm with any warnings — it'll ask you if you're sure. Answer Y or Yes.
Run adprep /domainprep. If you're raising the domain functional level later, run this too:
```
adprep /domainprep /gpprep
```
The /gpprep flag updates Group Policy. Do it on each domain where you plan to add new DCs.
Raise the forest functional level. Go back to Active Directory Domains and Trusts. Right-click and select Raise Forest Functional Level. Pick the target you noted. Click Raise. A confirmation box shows up — read it. That's your last warning.
Verify the change. After a few minutes (replication time), run this from a command prompt:
```
dsquery * cn=partitions,cn=configuration,dc=yourdomain,dc=com -attr msDS-Behavior-Version
```
Replace yourdomain and com with your domain name. The value should be 7 for Server 2016 functional level, 8 for Server 2019, 9 for Server 2022. If you see a lower number, replication hasn't finished yet.
Retry the promotion. On the new server, run DCPROMO or Install-ADDSDomainController again. It should work now.

What if it still fails?

If you still see error 0X00002175 after raising the functional level, check these:

Schema master hasn't replicated. Run repadmin /syncall on the schema master to force replication. Wait a few minutes after that.
You missed running adprep on the schema master. That step is mandatory. If you raise the functional level without running adprep first, the schema doesn't get updated. The new server still sees an old schema version.
The new server's ISO is mismatched. If you're using Windows Server 2022, make sure you used the right version in adprep. The adprep tool must match the new server's build. Running adprep from a Server 2019 media on a Server 2022 target won't work.

In my 14 years, I've seen this error twice when someone tried to sneak a Server 2022 DC into a 2008 R2 forest. Both times the forest was at 2008 R2 level. Raising it to 2016 level and running adprep fixed it. No other magic involved.

One last thing — don't try to bypass this by installing a compatibility pack or editing registry keys. That's a fast ticket to breaking your AD. The forest functional level exists for a reason. Respect it.