How to Activate Windows Server via DISM (2016 to 2025)

To activate Windows Server via DISM, change the edition and install the key in one DISM command, shown below. It also moves a licensed Standard server up to Datacenter in place. On Server Core, with no Settings app, we rely on it. Open an elevated prompt, check the edition, convert, restart.

1. Open an elevated prompt as administrator.
2. Read the current edition with Get-CurrentEdition.
3. List the target editions with Get-TargetEditions.
4. Set the edition and the key with Set-Edition and /AcceptEula.
5. Restart and check the activation.

Why activate Windows Server via DISM?

Three situations. The server runs an evaluation build. You need to change the edition, Standard to Datacenter. Or there’s no GUI at all.

Settings and the slmgr key install simply refuse a retail key on an evaluation. The edition itself has to change first. DISM does both jobs in one command: new edition, new key.

Typical situations where DISM is the right tool:

• Server Core installations with no desktop, only a command line.
• Evaluation copies, the 180-day trial, that have quietly become production.
• Scripted activation across many hosts.
• A perfectly valid key rejected by slmgr with “This edition cannot be upgraded”.
• A move from Standard to Datacenter after the VM count grew. The reverse direction isn’t supported.

What you need before you start

• A product key for the edition you’re converting to. A Standard key for Standard, a Datacenter key for Datacenter.
• Local administrator rights, in an elevated Command Prompt or PowerShell.
• Internet access to Microsoft’s activation servers, or a phone for offline activation.
• A snapshot or backup of the VM. Cheap insurance.

Check which version you run before buying anything. Keys aren’t interchangeable between releases. A Server 2019 key won’t activate Server 2022.

Which edition to convert to is settled in Windows Server 2022 Standard vs Datacenter; the full catalogue is under Windows Server.

Microsoft blocks evaluation-to-retail conversion on an Active Directory domain controller. Promote a second DC on a licensed server and transfer the FSMO roles. Remove AD DS from the evaluation DC, and only then convert it.

How to activate Windows Server via DISM step by step

The full sequence takes about ten minutes plus one restart. It follows the order Microsoft Learn documents for evaluation conversion and for Standard-to-Datacenter upgrades.

1. Open an elevated prompt. Press Win + X and pick the Terminal or PowerShell entry marked Admin. On Server Core the console you log into is already elevated.
2. Read the current edition.
3. List the allowed target editions and write down the exact edition ID you want.
4. Optionally, save the license terms to a file and read them first.
5. Set the edition and the key.
6. Restart when prompted. Expect one or two reboots.
7. Trigger activation, if it hasn’t happened by itself.
8. Verify the license status.

Steps 2 to 4, in order:

DISM /Online /Get-CurrentEdition
DISM /Online /Get-TargetEditions
DISM /Online /Set-Edition:ServerStandard /GetEula:C:\license.rtf

Evaluation builds show names like ServerStandardEval or ServerDatacenterEval. A licensed Standard shows ServerStandard.

Step 5, for Standard and then for Datacenter:

DISM /Online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
DISM /Online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

On a busy VM the second restart phase can sit at “Working on features” for several minutes. That’s normal.

Steps 7 and 8:

slmgr /ato
slmgr /dlv

Look for “License Status: Licensed”, and for a description with no “EVAL” in it.

We’d run the commands from a local console or a hypervisor console, with RDP as the second choice. The reboot drops your session. If something stalls, you want to see the screen.

DISM edition switches for Windows Server, one by one

DISM has four edition switches, and each one answers a different question. Mixing them up is the usual reason a command fails on a server.

Our habit: /Get-CurrentEdition and /Get-TargetEditions first, every time. The edition you bought isn’t in the target list? Then no key makes /Set-Edition work. And the error? Silent on the why. And DISM never moves a server down to a lower edition. Running a trial? That’s a different job, with its own walkthrough: converting a Windows Server 2022 evaluation to Standard.

DISM limits to know before you activate Windows Server

Microsoft’s page on DISM edition-servicing options ends with a short list of limits. Worth a read before a maintenance window. Here they are, in plain words.

Need the syntax on the server itself? Add /? right after a switch. Then this:

DISM /Online /Get-CurrentEdition /?
DISM /Online /Set-Edition /?

We’d also snapshot before the change, every time. DISM won’t roll an edition back, and a restore point is the only undo you get.

No internet? Offline activation after DISM

Air-gapped servers still activate. DISM sets the edition and the key first. Then slmgr displays the Installation ID.

slmgr /dti
slmgr /atp XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX

1. Run the first line to see the Installation ID.
2. On any device with internet, open Microsoft’s Product Activation portal at aka.ms/aoh.
3. Pass the CAPTCHA. Sign in with a Microsoft account, or a work or school one.
4. Pick Activate a Microsoft Product, then your Windows Server version.
5. Type in the Installation ID and note the Confirmation ID the portal gives back.
6. Enter that Confirmation ID on the server with the second line.

Microsoft moved the old telephone activation online to this portal. Signing in only opens the portal, by Microsoft’s own wording it doesn’t tie your account to the license. Details on the Product Activation portal page.

Annoying? A bit. Reliable? Yes. The Confirmation ID is tied to that hardware, so a reinstall means another round on the portal. The background is in our guide to activate Windows by phone.

Errors when you activate Windows Server via DISM

Most failures come from three things. A key that doesn’t match the target edition. A blocked path to the activation servers. Or a pending servicing operation.

One more classic: the activation command seems to show nothing. The Windows Script Host dialog often hides behind other windows. Wait half a minute, then check the license summary.

For the KMS code in particular, our KMS error 0xC004F074 walkthrough covers the DNS and firewall side.

KMS and MAK volume licensing

Volume licensing follows the same pattern. Convert the evaluation to retail with DISM first. Then switch channels with slmgr.

Microsoft documents channel changes as slmgr operations that keep the edition. That covers retail, volume and OEM. Need the public client keys? See Windows Server KMS keys.

slmgr /ipk YOUR-MAK-KEY
slmgr /ato

MAK keys activate online once. KMS clients renew every 180 days against your KMS host.

For KMS, point the client at the host if DNS auto-discovery isn’t set up:

slmgr /skms kms01.contoso.local:1688
slmgr /ato

A KMS host activates servers only after it has seen at least five requesting machines. For Windows client devices the number is 25.

Below that threshold you get 0xC004F038. In most cases it simply tells you to wait for more clients.

Batch script to activate Windows Server via DISM on many servers

A short batch file that takes the key as a parameter covers most small rollouts. The same lines run fine through PowerShell remoting or your RMM tool.

@echo off
DISM /Online /Get-CurrentEdition
DISM /Online /Set-Edition:ServerStandard /ProductKey:%1 /AcceptEula /NoRestart
echo Restart the server, then run: slmgr /ato and slmgr /dlv

Save it as activate.bat and pass the key as the only argument.

• Keep the key out of the script itself.
• Log the output.
• Reboot under control. Don’t let DISM restart hosts at random times.

With the NoRestart switch you choose the maintenance window yourself.

Verify the DISM activation worked

slmgr /xpr
slmgr /dlv

On Desktop Experience servers we also open Settings, System, Activation. Auditors like a screenshot. Every switch used here is in our slmgr commands list.

Which version to choose in 2026

For older hosts, our Windows Server 2016 guide to the risks and the migration options covers the choices.

Converting a 2016 evaluation in late 2026 still works technically. A 2022 or 2025 install is usually the better spend.

Keys for both sit in our store: Windows Server 2025 Standard and Windows Server 2022 Standard.

What Microsoft allows, in one table

Microsoft’s page Convert Windows Server editions and license types sets the rules. We copied them here.

If the edition you want isn’t in the Get-TargetEditions list, Microsoft’s answer is a fresh installation of that retail edition.

Quick answers