Windows server 2025 standard VM licensing

Question

Hi,

I have a Dell physical server supplied with Windows Server 2025 Standard (OEM, Desktop Experience) pre-installed and activated (OEM_DM channel).

Hyper-V is installed and I have deployed two Windows Server 2025 Standard VMs (Desktop Experience). This is within the Standard edition entitlement of 1 physical + 2 virtual instances.

However, the VMs are not activating.

What has been tested:

Host is fully activated (slmgr /dlv confirms Licensed, OEM_DM)

VM networking and internet connectivity confirmed

Attempted AVMA activation → fails (0xC004F035)

• Attempted OEM key in VM → fails (0xC004F050) - which I expected.

VM edition matches host (Server 2025 Standard, 24H2)

These VMs were initially on Evaluation edition, and were upgraded to standard using the ISO provided.

Given that the host is licensed and we are within the 2-VM entitlement, what is the supported activation method for the two entitled VMs under an OEM Standard host?

We are not exceeding virtualization rights and want to ensure proper activation in line with Microsoft policy.

Thank you.

Answer 1

AFAIK, Windows Server OEM (OEM_DM channel) licensing activates only the physical host. The OEM key embedded in the Dell server's BIOS is valid for that hardware only. The virtualization rights included with Windows Server Standard (1 physical + 2 virtual instances when the host is used only for Hyper-V) are usage rights, not activation rights. They allow you to legally run two Windows Server Standard VMs, but they do not automatically activate them and they do not provide transferable product keys for those VMs.

AVMA fails with 0xC004F035 because Automatic Virtual Machine Activation requires the host to be activated with a Volume License key (Datacenter or Standard) and be operating as a volume activation host. OEM activation does not support AVMA. AVMA is only supported when the host itself is activated via Volume Licensing (MAK or KMS) and is running Datacenter or Standard under Volume License.

Using the OEM key inside the VM fails with 0xC004F050 because OEM_DM keys are locked to the physical motherboard firmware and cannot be used in virtual machines.

You should use Volume Licensing activation for the guest VMs. That means using either a MAK key or a KMS infrastructure from a Volume Licensing agreement. The VMs would be installed with a Windows Server 2025 Standard Volume License key and activated via:

slmgr /ipk <Volume_MAK_or_KMS_Key>
slmgr /ato

If using KMS, the VM would use the generic volume license key (GVLK) for Windows Server 2025 Standard and activate against your KMS host automatically once DNS and connectivity are correct.

If you do not have Volume Licensing, you could purchase additional retail/volume licenses specifically for the VMs.

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin