loading...

. . . . . .

Request a Quote







    How to Convert Windows Server Evaluation to Standard Edition

    • By Rashid Sharafat
    • March 1, 2026
    • 2086 Views

    If you’re running a Windows Server Evaluation edition in your lab or production environment, there comes a point when you need to convert it to a fully licensed Standard edition. The good news? You don’t need to reinstall the operating system.

    In this comprehensive guide, you’ll learn how to safely and properly convert Windows Server Evaluation to Standard edition using DISM, remove existing product keys, and activate your server the correct way.

    This method works for supported Windows Server versions such as:

    • Windows Server 2016
    • Windows Server 2019
    • Windows Server 2022

    Why Convert from Evaluation to Standard Edition?

    The Evaluation edition:

    • Expires after 180 days
    • Shows activation warnings
    • Cannot be used long-term in production

    Converting to Windows Server Standard allows you to:

    • Permanently activate the server
    • Remove expiration limits
    • Continue using your existing configuration
    • Avoid reinstalling roles and features

    This process is supported by Microsoft and does not require data loss when performed correctly.

    Important Prerequisites

    Before starting, make sure:

    • You have a valid Windows Server Standard product key.
    • You are logged in as an Administrator.
    • You open Command Prompt as Administrator (elevated CMD).
    • You have a backup or snapshot (recommended for production systems).

    Step-by-Step Guide to Convert Evaluation to Standard Edition

    Step 1: Open Elevated Command Prompt

    • Click Start
    • Type cmd
    • Right-click Command Prompt
    • Select Run as administrator

    You must run the following commands in an elevated session.

    Step 2: Uninstall and Clear the Existing Product Key

    If a product key is already installed, remove it first.

    Run:

    slmgr /upk
    slmgr /cpky

    What These Commands Do

    • slmgr /upk → Uninstalls the current product key
    • slmgr /cpky → Clears the product key from the registry

    This ensures a clean conversion process.

    Step 3: Check Current Windows Server Edition

    To confirm you’re running an Evaluation edition:

    DISM /online /Get-CurrentEdition

    Typical output for evaluation:

    Current Edition : ServerStandardEval

    Step 4: Verify Available Target Editions

    Run:

    DISM /online /Get-TargetEditions

    If conversion is supported, you’ll see:

    Target Edition : ServerStandard

    This confirms your system can be converted.

    Step 5: Convert Evaluation to Standard Edition

    Now run the conversion command:

    DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

    Command Breakdown

    • /online → Targets the running OS
    • /Set-Edition:ServerStandard → Converts to Standard edition
    • /ProductKey: → Installs the Standard product key
    • /AcceptEula → Accepts license terms

    The system will begin processing and may take several minutes.

    Once complete, you will be prompted to restart the server.

    Step 6: Restart the Server

    Reboot the system to finalize the edition upgrade.

    After reboot, verify the edition again:

    DISM /online /Get-CurrentEdition

    It should now display:

    Current Edition : ServerStandard

    Step 7: Activate Windows Server

    You can confirm activation status:

    slmgr /dlv

    Common Errors and Fixes

    Error: “This edition cannot be upgraded”

    Make sure:

    • You’re converting from ServerStandardEval
    • Not converting between incompatible editions (e.g., Datacenter to Standard)

    Error 0x800f0805

    Indicates incorrect edition name. Double-check output from:

    DISM /online /Get-TargetEditions

    Can You Convert to Datacenter Instead?

    Yes, if supported:

    DISM /online /Set-Edition:ServerDatacenter /ProductKey: /AcceptEula

    Always confirm using /Get-TargetEditions first.

    Does This Method Work on Domain Controllers?

    Yes — but:

    • Take a system state backup first.
    • Avoid interrupting the upgrade.
    • Schedule downtime if in production.

    The conversion does not remove AD roles, but best practice is to ensure proper backup.

    When Should You NOT Use This Method?

    Do not use this method if:

    • You’re switching between different Server versions (e.g., 2019 → 2022)
    • You’re attempting unsupported cross-edition migrations
    • The Evaluation period has expired and system state is unstable

    Leave a Reply

    Your email address will not be published. Required fields are marked *