Forum Discussion

dimar221's avatar
dimar221
Copper Contributor
Nov 20, 2026

upgrade Server 2016 Essentials to 2025 Standard

https://info.microsoft.com/ww-landing-evaluate-windows-server-2025.html

I'm planning to upgrade my Server 2016 Essentials to 2025 Standard. Would Evaluate Windows Server 2025 let me do the ugprade?

 

Thanks for any feedback

2 Replies

  • maskwill's avatar
    maskwill
    Iron Contributor

    No. The Windows Server 2025 Evaluation ISO cannot be used to upgrade your existing Server 2016 Essentials installation. Microsoft does not support upgrading an existing installation to an Evaluation edition.

     

    What you should do instead:

     

    1. Obtain the Windows Server 2025 Standard full installation ISO (not Evaluation).
    2. Mount the ISO inside Server 2016.
    3. Run `setup.exe`.
    4. Select Windows Server 2025 Standard (Desktop Experience) if you want the GUI.
    5. Select Keep personal files and apps if Setup offers it.
    6. Activate using a valid Server 2025 Standard license.

     

    Important: Microsoft lists Server 2016 → Server 2025 as a supported direct upgrade path, but verify the Essentials edition upgrade compatibility before proceeding. Back up everything first.

     

    Reference: Microsoft – Windows Server upgrade paths - https://learn.microsoft.com/windows-server/get-started/install-upgrade-migrate?tabs=windows-update

  • Short answer: I would not plan the production upgrade around the Evaluation media. Use licensed Standard media for the real move, and use the evaluation only to rehearse on a clone. A few things matter more than the media, and some of them change the cost.

     

    1. Test on a copy first. Take a full backup or image, restore it to a VM, and run the whole upgrade there. That tells you how long it takes and what breaks.

    2. The Essentials Experience features. As far as I know, the Essentials Experience role (the Dashboard, Remote Web Access, client backup and the Microsoft 365 integration) is not part of 2025 Standard. If you rely on any of that, plan replacements before you upgrade.

     

    3. Licensing is different. Essentials has user limits but no CALs. Standard is licensed per core (with a minimum core count) and needs CALs for your users or devices. Check this before you commit, because it can change the budget.

     

    4. The path. In-place upgrades from 2016 are supported to a newer release as far as I know, but moving from the Essentials edition to Standard is an edition change. Check Microsoft's current upgrade path and edition conversion pages for your exact build, and confirm the server is the only domain controller and holds all roles. A clean alternative is to build a new 2025 server, move the roles and data, and retire the old one, which is often safer than an in-place jump.

     

    5. Before you start: check hardware and driver support for 2025, make sure every line of business app supports it, and note your domain and forest functional level.

     

    It would help to know whether this is a physical server or a VM, how many users you have, which Essentials features you actually use, and whether the server runs anything besides AD, files and print.