Converting Windows Server from evaluation edition

To convert Windows Server 2022 Evaluation to a licensed edition, run DISM Set-Edition with your product key from an elevated Command Prompt or PowerShell. This applies the key, changes the edition to Standard or Datacenter, and prompts for a reboot to finish.

Run this to convert to the edition you own:

What the command does: uses DISM to switch the installed Windows Server edition and install your 25-character product key, then accepts the licence terms.

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

Or for Datacenter:

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

Run these in an elevated session on the server. Replace the Xs with your product key.

Before you start

• Plan a maintenance window. The conversion requires at least one reboot. Running it on a live production VPS without a window will cause an outage.
• Have the right key for the conversion step. The Set-Edition command needs a retail or MAK product key. A KMS client (GVLK) key will fail at this stage. You can switch to KMS later.
• Know the supported paths. Datacenter Evaluation cannot convert to Standard retail. It can convert only to Datacenter retail. Standard Evaluation can convert to Standard retail or Datacenter retail. You cannot convert to a lower edition than you have.
• Desktop Experience vs Core. Since Windows Server 2016, Desktop Experience evaluation builds cannot convert to Core retail. Some Core evaluation builds have limited paths. You must check your allowed targets first.
• Domain controllers are an exception. Microsoft does not support converting a DC from Evaluation to retail. The supported approach is to add a licensed DC, transfer FSMO roles, then demote the evaluation DC.
• Be aware of expiry behaviour. When an evaluation expires, Windows Server begins shutting down about every hour until it is licensed. Convert as soon as possible if you are near or past expiry.
• Back up what matters. Take application and data backups before you change the OS edition. Conversion is in-place, but a fallback makes recovery straightforward if something else on the server fails during the reboot.
• Have console access ready. If Remote Desktop drops during the reboot, open the VNC console in Virtualizor through your Hostworld client area so you can watch the restart and sign in on the console if needed.

Step 1: Confirm you are on an evaluation build and see your allowed targets

What the command does: shows the currently installed edition name so you can check for “Eval”.

DISM /online /Get-CurrentEdition

You will see your current edition name. If you are on an evaluation build, “Eval” appears in the name.

What the command does: lists the editions you are allowed to convert to from your current state. You must use one of these exact edition names.

DISM /online /Get-TargetEditions

Make a note of the exact target name returned, for example ServerStandard or ServerDatacenter. If the edition you want is not listed, a fresh installation is required. On Hostworld you can rebuild the VPS or mount a custom ISO in Virtualizor and reinstall, once you have taken backups.

Step 2: Open an elevated shell on the server

• Sign in via RDP, or use the VNC console in Virtualizor from your Hostworld client area if RDP is not available.
• Open Start, type “cmd”, right-click Command Prompt, choose “Run as administrator”. Or open Windows Terminal as Administrator and use a PowerShell tab.

Step 3: (Optional) Save the licence terms you are accepting

What the commands do: create a folder to hold the licence file, then save the Windows Server licence terms to a local file so you have a copy before accepting them.

mkdir C:\temp
DISM /online /GetEula:C:\temp\ws2022-eula.xml

Step 4: Convert the edition using DISM Set-Edition

Have your 25-character retail or MAK product key ready. Do not use a KMS client key at this point.

What the command does: tells DISM to set the target edition, installs your product key, and accepts the licence terms non-interactively.

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

Or, if your target is Datacenter:

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

• Use the exact edition name returned by /Get-TargetEditions. Typing the name incorrectly causes the command to fail.
• If DISM reports that the edition cannot be set, check the constraints in “Before you start”: you may be attempting Datacenter Eval to Standard, a DC conversion, or a Desktop to Core path that is not supported.

Step 5: Reboot when prompted and verify conversion and activation

DISM will request a restart. Allow it to reboot. Reconnect using RDP or the Virtualizor VNC console.

What the command does: confirms the installed edition after the reboot.

DISM /online /Get-CurrentEdition

“Eval” should be gone from the edition name.

What the commands do: show detailed licence status, then attempt online activation.

slmgr /dlv
slmgr /ato

If activation succeeds, you are finished. If it fails, review the key type you used and network access to Microsoft activation services, then run slmgr /ato again after addressing the cause.

Step 6: If you use KMS, switch to KMS after conversion

If your organisation uses Key Management Service (KMS), convert Eval to retail first with a retail or MAK key. After that, install the appropriate KMS client setup key (GVLK) and activate.

What the commands do: install the KMS client setup key for your edition, then trigger activation.

Windows Server 2022 Standard:

slmgr /ipk VDYBN-27WPP-V4HQT-9VMD4-VMK7H
slmgr /ato

Windows Server 2022 Datacenter:

slmgr /ipk WX4NM-KYWYW-QJJR4-XV3QB-6VM33
slmgr /ato

If activation does not complete, confirm that you are using KMS in the first place and that you have already converted away from Evaluation.

Step 7: If your desired edition is not offered, reinstall instead

If /Get-TargetEditions does not list the edition you want, conversion is not supported. The path forward is a fresh installation.

• On a Hostworld VPS: you can rebuild the VPS from Virtualizor or mount a custom ISO and install the licensed edition you own. Take backups first. Rebuilding or installing from ISO replaces the operating system.
• On a domain controller: do not attempt conversion. Build another Windows Server on a licensed edition, promote it to a DC, move FSMO roles, then demote the evaluation DC and decommission it.

Step 8: Common errors and how to avoid them

• Using a KMS client key with Set-Edition: this fails. Use a retail or MAK key for the conversion, then change to KMS with slmgr /ipk and /ato.
• Trying to convert a DC: not supported. Follow the add-new-DC, move roles, demote sequence.
• Datacenter Eval to Standard: not supported. The target will not be listed by /Get-TargetEditions.
• Mistyping the edition name or leaving out /AcceptEula: use the exact target name from /Get-TargetEditions and include /AcceptEula, or the change will be blocked.
• Forgetting the reboot: the conversion does not complete until after the restart. Plan downtime.

What next

If you are done converting and activating, take a moment to document the key you used and store the EULA you saved. If you expected your Windows VPS to include a licence key and cannot find it in your records, open a support ticket and we will check your order in WHMCS.

If you could not convert because the edition you want is not offered, plan for a fresh install. On a Hostworld VPS you can rebuild or mount a custom ISO in Virtualizor through your client area. Back up data first so you can restore your services afterwards. If you need help coordinating the rebuild to minimise downtime, open a support ticket.

For broader VPS administration topics, see our VPS guides. If you are looking to deploy more capacity in the UK, see our Linux VPS range. We host in our own Maidenhead data centre, with an option in New York if you need US presence.