Windows 2019 server activation in the Hyper-V VM , with the Host 16 core windows server 2019 licenses

WindowsForum AI

AI

Staff member

Robot

Joined

Mar 14, 2023

Messages

114,209

• Feb 13, 2026

#2

That error 0xC004F069 during slmgr /ipk almost always means the product key you’re entering does not match the Windows Server edition/channel that’s installed in the VM (for example: Standard vs Datacenter, Retail/OEM vs Volume, or you installed an Evaluation edition).
Also, an OEM key that came with a physical Dell server typically won’t activate a VM the way you expect. Even if your license rights allow running 2 VMs (Windows Server Standard licensing does), activation still needs a key/method that matches the guest OS (often Volume MAK/KMS, or AVMA if the host is Datacenter).

1) First: confirm what edition is installed inside the VM​

Inside the VM, run these in an elevated Command Prompt:

Code:

DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
slmgr /dli

Please paste the output here (you can redact partial key data).

If you see “Eval” (Evaluation)​

Example: ServerStandardEval or ServerDatacenterEval
Then you must convert the VM to a non-eval edition before it will activate:

Code:

DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
shutdown /r /t 0

(Use ServerDatacenter instead of ServerStandard if that’s what your key actually is for.)
After reboot:
slmgr /ato

2) If it’s NOT evaluation: it’s likely the wrong key for the installed edition​

Common cases:

• VM installed as Datacenter, but key is Standard (or the reverse)
• VM installed from Volume License media, but you’re using an OEM key (or vice‑versa)

Fix: Either install the VM with the correct edition ISO, or use a key that matches the VM’s installed edition/channel.

3) Important licensing/activation note for Hyper‑V + OEM​

• Windows Server 2019 Standard licensed on the host (all cores) gives rights for up to 2 Windows Server VMs if the host OS is used only to run Hyper‑V.
• But activating those VMs with the same OEM key often fails, because OEM activation is tied to the physical machine and isn’t intended to be reused in guests.

The “normal” ways people activate the VMs are:​

• Volume Licensing (MAK or KMS) for the guests, or
• AVMA (Automatic VM Activation) only if the Hyper‑V host is Windows Server Datacenter (Standard host does not provide AVMA)

Quick question (so I can give the exact fix)​

1) What does DISM /online /Get-CurrentEdition show in the VM (does it include Eval)?
2) Is your Hyper‑V host OS Server 2019 Standard or Datacenter?
3) Are you trying to use the Dell OEM key inside the VM (the one that activates the physical server)?
Reply with those details and I’ll tell you the exact activation path (convert edition vs correct key type vs AVMA/MAK/KMS).

 

Upvote 0 Downvote

Sadhikary15

Member

Joined

Feb 13, 2026

Messages

5

• Feb 13, 2026

Thread Author #4

I am getting this information when I have used this code : DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula<br>shutdown /r /t 0
P
lease advice

 

Upvote 0 Downvote

WindowsForum AI

AI

Staff member

Robot

Joined

Mar 14, 2023

Messages

114,209

• Feb 13, 2026

#5

Your screenshot confirms the VM is running ServerStandardEval (Evaluation). That’s why activation fails.
The Error 87 you’re seeing now is simply because you pasted two commands on the same line, so DISM is trying to interpret shutdown and 0 as DISM options.

Fix (run as TWO separate commands)​

1) Open Command Prompt as Administrator inside the VM.
2) Run only this (one line):
DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

• Wait for it to finish (can take a few minutes).
• It should eventually say the operation completed successfully and that a reboot is required.

3) After DISM finishes, run the reboot command separately:
shutdown /r /t 0
4) After reboot, try activation:
slmgr /ato

If it still won’t activate after conversion​

Then the key you’re using is likely not valid for Server 2019 Standard (or it’s a key type that won’t activate this install, e.g., a KMS setup key without a KMS server).
Reply with:

• The output of: slmgr /dli
• And tell me: is your Hyper‑V host Server 2019 Standard or Datacenter, and are you trying to use the Dell OEM key inside the VM?

Then I’ll tell you the correct activation method (OEM vs MAK/KMS vs AVMA).

 

Upvote 0 Downvote

Sadhikary15

Member

Joined

Feb 13, 2026

Messages

5

• Feb 13, 2026

Thread Author #6

 

Upvote 0 Downvote

WindowsForum AI

AI

Staff member

Robot

Joined

Mar 14, 2023

Messages

114,209

• Feb 13, 2026

#7

You successfully converted from Eval to full Server 2019 Standard—good.
Now the VM shows:

• Edition: Windows(R), ServerStandard
• Channel: OEM_COA_NSLP
• Activation fails: 0xC004F034 (License status: Notification)

What 0xC004F034 means in your case​

This usually happens when the key cannot be activated on this installation, and with an OEM_COA key the most common reason is:
That OEM key is meant to activate Windows on the physical server hardware, not inside a VM.
(OEM keys are often tied to physical hardware / OEM licensing rules, so using them in a VM frequently fails even if your “core licensing rights” cover VMs.)

---

Step 1 — Confirm the VM is no longer Evaluation​

In the VM run:
DISM /online /Get-CurrentEdition
It should say ServerStandard (not ServerStandardEval).

---

Step 2 — Try Phone Activation (this is the only “maybe” path with OEM keys)​

Sometimes Microsoft will allow activation by phone if it’s legitimate usage.
In the VM:

• Press Win + R
• Type:

slui 4

• Choose your country/region and follow the phone prompts.

If phone activation works, you’re done.
If phone activation is rejected, then that OEM key cannot be used in the VM.

---

Step 3 — The real solution if phone activation fails​

You need one of these supported activation methods for the guest VM:

Option A (most common): Use a separate key for the VM​

• Buy another Windows Server 2019 Standard license/key for the VM, or
• Use a Volume License MAK/KMS key for the VM (if your organization has VL).

Option B: If you want easy VM activation, use Datacenter on the host (AVMA)​

If the Hyper-V host is licensed/installed as Windows Server Datacenter, you can use AVMA keys to activate VMs automatically (Standard host does not provide AVMA).

---

Quick questions (so I can tell you the best option)​

• What is installed on the Hyper‑V host: Server 2019 Standard or Datacenter?
• Is the key you’re using inside the VM the Dell OEM key that came with the physical server?
• How many Server VMs do you plan to run (1, 2, more than 2)?
  Answer those and I’ll tell you the cleanest/cheapest compliant activation approach for your setup.

 

Upvote 1 Downvote

Solution

Sadhikary15

Member

Joined

Feb 13, 2026

Messages

5

• Feb 13, 2026

Thread Author #8

Thank You very much. I have activated my product successfully

 

Upvote 0 Downvote

WindowsForum AI

AI

Staff member

Robot

Joined

Mar 14, 2023

Messages

114,209

• Feb 13, 2026

#9

Glad to hear you got it activated successfully, Sadhikary15.
If you’d like, tell me which method worked (online activation, slui 4 phone activation, different key, etc.). That way I can suggest the best approach for activating any future Server 2019 VMs on the same Hyper‑V host and help you avoid the Eval/OEM mismatch issues again.

 

Upvote 0 Downvote