Converting Windows Server 2022 Evaluation to Standard Edition: Complete Activation Guide

Going from Server 2022 evaluation to Standard doesn’t need a rebuild. One DISM command with a Standard retail key, then a restart. Roles, settings and data stay in place. We can’t fix the trial with slmgr, and a domain controller can’t be converted at all.

The mistakes happen before and after the command, so most of this page is about those.

1. Back up: a full backup or a VM checkpoint.
2. Check the edition: DISM reports ServerStandardEval on a trial.
3. Convert: Set-Edition:ServerStandard with your key and /AcceptEula.
4. Restart, then check activation with the slmgr license report.
5. Domain controllers: move the roles to a licensed server first.

Converting Windows Server 2022 evaluation to Standard in place

It works, and Microsoft supports it. DISM turns the trial into the retail edition in place. Roles, features, applications, domain membership and data are kept.

Two exceptions apply. A server that’s a domain controller can’t be converted. And a Datacenter trial can only become retail Datacenter.

Plenty of IT teams start with the free Windows Server 2022 evaluation from the Microsoft Evaluation Center. They test roles, Hyper-V or an application stack before buying. Weeks pass, and the test box becomes useful. That’s exactly the case this conversion was built for.

A reinstall would cost you an export of the configuration, a software reinstall and new permissions. The conversion takes one command, a key and a restart window. It’s usually under half an hour. We’d say the only real decisions are the edition and the kind of license you activate afterwards.

Windows Server 2022 evaluation limitations

The trial is full-featured and lasts 180 days. When it ends, three things happen. The desktop shows a licensing warning. The server starts shutting down about once an hour. And the remaining time disappears from the watermark.

Between shutdowns the installation keeps working. So you can still convert it. Production use is over at that point, though.

Check the clock before anything else, in an elevated prompt:

slmgr.vbs /dlv

On a trial copy the Description line contains EVAL. The output also shows the time left and the remaining rearm count. An unactivated trial shows the days left in the bottom right corner of the desktop as well.

Stretching the trial

Usually possible, a few times. This resets the clock, followed by a restart:

slmgr.vbs /rearm

The license details show how many rearms remain. We’d treat it as a short bridge to a purchase, not as a licensing strategy. Rearming gives you no production rights.

No registry trick turns an expired trial into a licensed server. A guide that suggests one deserves to be skipped. The supported fix is the DISM conversion below, with a genuine key.

Prerequisites for converting evaluation to Standard

• A Windows Server 2022 Standard product key.
• Local administrator rights.
• An elevated Command Prompt or PowerShell window.
• A fresh backup.
• A maintenance window for one or two restarts.
• A server that isn’t a domain controller.
• ServerStandard in DISM’s list of target editions.

Internet access makes the final activation simpler.

Which key works

Microsoft’s procedure uses a retail product key for the target edition. A retail Standard key is the simple choice. Ours: a Windows Server 2022 Standard key, instant to email. DISM installs it during the conversion, and online activation follows.

• Retail key. Works directly with the Set-Edition switch. Activates online or by phone.
• Volume license, MAK. Convert first. Then install the MAK with slmgr.
• KMS. Many admins pass the public KMS client setup key for this edition to DISM. Then they activate against their own KMS host.

That public KMS client key is this one. It activates nothing without a KMS host on your network:

VDYBN-27WPP-V4HQT-9VMD4-VMK7H

Datacenter keys don’t convert to Standard. Keys for other server releases don’t work on a 2022 installation either.

Preparation checklist

1. Take a full backup, or a VM snapshot or checkpoint. The conversion keeps data, and a restore point costs minutes and saves days.
2. Write down the installed roles and features. The command is below.
3. Install pending updates and restart once. DISM shouldn’t meet a pending reboot.
4. Leave several gigabytes free on the system drive.
5. Schedule downtime and tell users. The server restarts during the change.
6. Does the server run Active Directory Domain Services? Stop here and read the domain controller section first.

Get-WindowsFeature | Where-Object Installed

How to convert Server 2022 evaluation to Standard with DISM

1. Open Command Prompt as administrator.
2. Check the current edition.
3. List the editions the install can move to.
4. Run the conversion with your key and accept the license terms.
5. Confirm the restart, sign in again and check the result.

Step 1: check the current edition

Right-click Start and choose Terminal as admin. Or search for Command Prompt and pick Run as administrator. Then:

DISM /online /Get-CurrentEdition

Look for ServerStandardEval as the current edition. Desktop Experience and Server Core use the same name. ServerDatacenterEval tells you the Datacenter trial got installed.

Step 2: list the target editions

DISM /online /Get-TargetEditions

ServerStandard has to appear in the answer. From a Standard trial you normally see ServerStandard and ServerDatacenter.

ServerStandard is missing? Then conversion isn’t possible on this installation. A clean install of the retail edition is the way forward.

Step 3: read the license terms, if you need a record

Microsoft’s procedure includes saving the terms before you accept them. Some organisations require that record. Open the saved file in WordPad.

DISM /online /Set-Edition:ServerStandard /GetEula:C:\license.rtf

Step 4: run the conversion

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

What each part of that line does:

Then wait. The progress bar can sit at 10% for a long time, and that’s normal. On SSD hardware it typically finishes in 10 to 20 minutes. Slower disks take longer.

At the end DISM asks whether to restart Windows to complete the operation. Press the Y key. The server applies changes during boot, sometimes with an extra automatic restart.

Step 5: confirm the result

Sign in and open an elevated prompt again. Either of these should now answer with ServerStandard:

DISM /online /Get-CurrentEdition
Get-WindowsEdition -Online

We’d run DISM from a local console or a VM console, not over RDP. If the session drops mid-conversion, the command still runs. You lose sight of the restart prompt, though, and may wait for nothing.

Why slmgr.vbs can’t convert the evaluation

The tool only installs and activates keys for the installed edition. A trial edition has its own SKU. So a retail Standard key fed to it typically fails with 0xC004F069, “the product SKU is not found”.

Microsoft documents slmgr for switching license types after the conversion, and for Essentials. Not for leaving the trial. Older guides presented it as an alternative route. An earlier version of this page did too. It isn’t one for Standard or Datacenter.

More DISM edition switches, Datacenter scenarios included, are in our walkthrough on activating Windows Server with DISM.

Activating Windows Server 2022 Standard after conversion

After the restart the server usually activates online by itself, within a few minutes. If it doesn’t, there are three routes.

Online

Open Settings, System, Activation. Or run the first line below and wait for the “Product activated successfully” dialog. The second line should then show License Status: Licensed.

slmgr.vbs /ato
slmgr.vbs /dlv

By phone, for offline servers

slui 4

1. Run the command from an elevated prompt.
2. Select your country or region.
3. Call the number shown and read out the installation ID.
4. Type the confirmation ID you receive into the wizard and click Activate.

The call itself, explained: activate Windows by phone.

MAK or KMS

Both run from an elevated prompt, one line at a time, in this order.

The license details of a KMS client show the host name and a renewal interval.

Activation errors after a conversion are rarely about the conversion. We cover the remaining scenarios in our guide to Windows Server 2022 activation for every edition. Error 0xC004F074 has its own page, because KMS setups hit it so often.

A domain controller on the trial

It can’t be converted directly. Microsoft states that plainly. The way round takes a second server.

1. Build or convert a second server to the licensed Standard edition and promote it to a domain controller.
2. Let replication finish, and check it.
3. Move the FSMO roles to the new one.
4. Demote the trial server. Server Manager, Remove Roles and Features, Active Directory Domain Services.
5. Restart. Then run the DISM conversion on what’s now a member server.

repadmin /replsummary
Move-ADDirectoryServerOperationMasterRole

The first line checks replication. The second is the PowerShell cmdlet that moves the roles.

Rarely does anyone plan for this in a lab. That’s why it catches people. The test server became the only DC, and the trial clock keeps ticking.

Server 2022 evaluation to Standard: conversion and activation errors

Four causes produce most failures. The wrong key for the target edition. A target edition DISM doesn’t list. A domain controller role. Or a pending restart.

Read the exact DISM message, and check the log. Fix the cause and run the command again. The log is here:

%windir%\Logs\DISM\dism.log

Activation errors after a successful conversion usually point to the network, DNS or the key type.

What to send us if it still fails

• The output of the current edition query and of the target editions query.
• The exact DISM error text, or a screenshot of it.
• The last lines of the DISM log.
• Whether the server runs Active Directory Domain Services.
• Your order number, not the full key.

With those five things we can usually tell which of the four causes it is. No need to put the key itself in a screenshot.

Windows Update misbehaving afterwards

A restart and a manual update check solve it in most cases. Still failing? Reset the update components from an elevated prompt, one line at a time:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

If system files look damaged, follow up with these two:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Verifying Server 2022 after the evaluation to Standard switch

1. Edition. The edition query returns ServerStandard.
2. Activation. The license details say Licensed, with no trial end date. Settings shows Windows as activated.
3. Roles and services. Server Manager has no red alerts. File shares, IIS sites, Hyper-V VMs and applications respond.
4. Event logs. Scan System and Application for new errors since the restart.
5. Updates. Run Windows Update and install everything offered.
6. Cleanup. The command below recovers space in WinSxS.
7. Records. Store the key securely, with the conversion date, the edition and the server name. Delete the VM checkpoint once you’re satisfied.

DISM /Online /Cleanup-Image /StartComponentCleanup

Licensing considerations after the conversion

The conversion doesn’t change the licensing rules. It makes the installation legal once the key matches your licensing. The Standard edition is licensed per physical core.

• Core count. Every core in the host needs a license. The minimum is 8 per processor and 16 per server. Count physical cores, not threads.
• An example. A two-socket host with 12 cores each needs 24 core licenses.
• Virtual machines. Standard covers two VMs per fully licensed host. Stacking another set of licenses on the same host adds two more each time.
• CALs. User or device CALs for normal access. Remote Desktop Services CALs on top, if people log on through RDS.
• License type. Retail, OEM and volume licenses have different transfer rights. OEM stays with the original hardware.
• Records. Keep proof of purchase, keys and a server-to-license map. That’s what an audit asks for.

For many VMs, Datacenter is often the cheaper answer. Our page on VM limits in Windows Server 2022 Standard works through the numbers.

Standard or Datacenter as the target

Pick the edition before you run anything. Going from Standard up to Datacenter later is one more DISM command. Going down from Datacenter takes a clean install.

Converting the evaluation to Datacenter instead

The Datacenter route uses the same commands with a different edition name. We run them in an elevated Command Prompt with a retail Datacenter key:

DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerDatacenter /GetEula:C:\license.rtf
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

ServerDatacenter has to appear in the list of targets first. From a Standard trial it normally does; from a Datacenter trial it’s the only target.

The key must be a Windows Server 2022 Datacenter key. A Standard key fails on this target with “not valid for the target edition”, and the reverse is true as well.

Server Core trials follow stricter rules

Microsoft’s conversion page sets limits that catch Server Core installs in particular.

So a Standard Core trial can’t stay Standard. We’d either license it as Datacenter or reinstall from Standard retail media. Get-TargetEditions shows which case you’re in before anything changes.

The same steps on 2016, 2019 and 2025

Microsoft’s page applies to every release from 2016 to 2025, and the commands don’t change between them. We only change the key: it has to match both the release and the target edition.

Microsoft lists two checks for a server still on the trial. The edition name ends in Eval, or the license output contains EVAL:

DISM /online /Get-CurrentEdition
slmgr.vbs /dlv

We compare the editions themselves in Windows Server Standard vs Datacenter and the whole line-up in Windows Server editions explained.

Which editions a Windows Server evaluation can convert to

An evaluation Standard can become retail Standard or retail Datacenter. An evaluation Datacenter can only become retail Datacenter.

Since Windows Server 2016 you also can’t switch between Desktop Experience and Server Core during conversion. Anything outside these paths needs a fresh install. That’s why the target list comes first.

Evaluation copies run for 180 days. After that the server shows a warning and, in our experience, starts shutting itself down every hour. So convert well before the deadline.

Server 2022 evaluation to Standard: the short path

1. Back up, or take a checkpoint.
2. Confirm the trial edition and the list of targets.
3. Run the conversion with the key.
4. Restart when DISM asks.
5. Check the edition and the activation state.
6. Run Windows Update, then tidy up.

Microsoft’s own page for the procedure is Convert Windows Server editions and license types. We cover the other releases in our DISM activation guide, and the edition choice in Windows Server 2022 Standard vs Datacenter.

Before and after, in one table

If the watermark stays after the restart, the server hasn’t reached Microsoft yet; we check the network and run the activation again.

Quick answers

Related guides

• Windows vs Windows Server
• Slmgr commands with examples
• Windows Server KMS keys
• Windows Server 2019 ISO from Microsoft’s Evaluation Center