Dear Nikita Kotschkin,
Windows Server 2025 Essentials shares its core binaries with the Standard edition, meaning it no longer includes the legacy Essentials Experience role that actively crashed servers for Active Directory topology violations.
You can promote Windows Server 2025 Essentials to be your new Domain Controller. Because the legacy hard system blocks have been removed from the codebase, the operating system will successfully execute the Install-ADDSDomainController deployment without active interference. You simply need to ensure your underlying infrastructure meets the modern Microsoft prerequisites, specifically utilizing DFSR instead of the deprecated FRS for SYSVOL replication, and maintaining a Forest and Domain Functional Level of at least Windows Server 2016. Crucially, you must adhere to the strict licensing topology for the Essentials edition: your server must be deployed at the root of a single-domain forest, hold all five FSMO roles, and operate within the hard limit of 25 users and 50 devices. If your environment requires replica domain controllers or exceeds these user limits, you are required to execute the DISM /online /Set-Edition:ServerStandard /ProductKey:<StandardKey> /AcceptEula command in an elevated prompt to convert the host to the Standard edition before configuring the Active Directory Domain Services role.
Hope this answer brought you some useful information. If it has, please consider accepting the answer so that other people sharing the same issue would benefit too. Thank you.
VP