Fix it now
Microsoft publishes 0xC004FD01 as “Windows isn’t running on a supported Microsoft Hyper-V virtualization platform” and 0xC004FD02 as “Windows isn’t activated on the host machine.” Those are two different faults, and older guidance had them the wrong way round. Check the platform first, then the host’s own activation.
slmgr /dlv
- Establish what the guest is actually running on. Automatic Virtual Machine Activation works on Hyper-V only. A guest on VMware, KVM, a public cloud platform or a nested environment cannot use it, and in Azure it is not supported at all.
- On the host, confirm the edition and state with
slmgr /dlv. AVMA requires a Windows Server Datacenter edition with the Hyper-V server host role installed, and the host must itself be activated. - Confirm the Data Exchange integration service, also known as Key-Value Pair Exchange, is enabled for the virtual machine. Check with
Get-VMIntegrationService -VMName "YourVM"and enable it withEnable-VMIntegrationService -Name "Key-Value Pair Exchange" -VMName "YourVM". - In the guest, install the AVMA key published for that guest edition and Windows Server version with
slmgr /ipk <AVMA key>, then activate withslmgr /ato. - If the machine is in Azure, change the method rather than chasing the host:
slmgr /ipk <KMS client key>, thenslmgr /ckms,slmgr /skms azkms.core.windows.net:1688andslmgr /ato.
Install the correct key over the top with slmgr /ipk. Microsoft’s own remediation for this case changes the activation method by installing a new key rather than uninstalling the old one first.
If that fixed it you can stop here. If not, the next section covers the host and guest combinations that are supported and what the host edition actually decides.
Why it happens
Automatic Virtual Machine Activation lets a properly licensed Datacenter host activate the Windows Server guests running on it without any of them touching the network. The guest is installed with an AVMA key, which is not a licence but a marker telling the licensing service to ask the hypervisor rather than a key server, and the request travels over the Data Exchange integration component – the one also known as Key-Value Pair Exchange. Microsoft is explicit that this component must be enabled in the virtual machine’s settings for AVMA to work.
The two published codes in this record say different things, and this article previously had them swapped. Microsoft publishes 0xC004FD01 as Windows not running on a supported Microsoft Hyper-V virtualization platform – a statement about where the guest is, not about what the host can offer. It publishes 0xC004FD02 as Windows not being activated on the host machine, with the advice to contact your system administrator. So a 0xC004FD01 sends you to look at the platform, and a 0xC004FD02 sends you to the host’s own licence.
0xC004FD03 and 0xC004FD04 have no published meaning on learn.microsoft.com or support.microsoft.com, and the descriptions earlier versions of this article gave them were not sourced. Run slui.exe 0x2a 0xC004FD03 in the guest to read the text your build carries.
Two facts about editions are worth getting straight, because they are commonly reversed. The host must be running a Windows Server Datacenter edition with the Hyper-V server host role installed. The guests do not have to be Datacenter: Microsoft publishes AVMA keys for Datacenter, Standard and, on some versions, Essentials, and states that all editions of eligible versions are supported as guests. What restricts guests is version rather than edition – a host can activate its own version and older ones, never a newer one.
The case people miss entirely is Azure. Microsoft documents that AVMA is not supported there, and that a machine migrated in, or given an AVMA key after deployment, produces exactly these codes. The remedy is to move it to KMS rather than hunt for a host.
The guest is not on a platform that can serve AVMA
You have this one if 0xC004FD01, on a guest hosted by VMware, KVM or a nested environment – or in Azure, where Microsoft documents AVMA as unsupported.
- Confirm the platform from inside the guest before assuming anything about a host.
- Where the platform is not Hyper-V, license each Windows Server guest in its own right with the appropriate key.
- In Azure, change the method rather than the host:
slmgr /ipk <KMS client key>, thenslmgr /ckms,slmgr /skms azkms.core.windows.net:1688andslmgr /ato. - Confirm with
slmgr /dlvthat the method and status are what you expect.
AVMA is tied to Datacenter host licensing on Hyper-V and cannot be enabled elsewhere. In Azure this is not a fault to repair; it is the wrong method for the platform.
The host is not activated
You have this one if 0xC004FD02 specifically, with the host showing Datacenter but a licence status that is not Licensed.
- Activate the host first, by whatever method you use – a key with
slmgr /ipkandslmgr /ato, or KMS, or directory-based activation. - Confirm with
slmgr /dlvon the host that it reads Licensed before touching any guest. - In each guest, retry
slmgr /ato. - In a failover cluster, each host needs to be activated individually for guests to remain activated as they move.
The host is not Datacenter, or lacks the Hyper-V role
You have this one if slmgr /dlv on the host names Standard, and every guest on it fails the same way regardless of configuration.
- Confirm the edition rather than trusting memory:
slmgr /dlvon the host. - AVMA requires a Windows Server Datacenter edition with the Hyper-V server host role installed. There is no configuration that enables it on another edition.
- Either license the host as Datacenter, or license and activate each guest independently by KMS, directory-based activation or MAK keys.
- Install the appropriate key in those guests with
slmgr /ipk <key>and activate.
Data Exchange is disabled for this virtual machine
You have this one if The host is Datacenter and activated, other guests on it work, and this one does not.
- On the host, run
Get-VMIntegrationService -VMName "YourVM"and look at the Key-Value Pair Exchange entry. - Enable it:
Enable-VMIntegrationService -Name "Key-Value Pair Exchange" -VMName "YourVM". - In Hyper-V Manager the same setting is on the virtual machine’s Integration Services page, named Data Exchange.
- In the guest, confirm the corresponding service is running, then run
slmgr /ato.
Hardening baselines and virtual machine templates sometimes disable this component deliberately. If your guests come from a template, fix the template rather than each machine.
The AVMA key does not match the guest, or the host is older than the guest
You have this one if The key was accepted by slmgr /ipk and activation still fails, on a guest that is a different Windows Server release from the key.
- Confirm the guest’s exact edition and version with
slmgr /dlvin the guest. - Take the AVMA key published for that guest edition and version from Microsoft’s documentation, and install it with
slmgr /ipk. - Check the host and guest combination. A host can activate its own version and older ones; it cannot activate a newer guest.
- Retry
slmgr /atoand confirm withslmgr /dlv.
Full reference
What each code says
| Code | Status | Reading |
|---|---|---|
0xC004FD01 |
Published | Windows isn’t running on a supported Microsoft Hyper-V virtualization platform |
0xC004FD02 |
Published | Windows isn’t activated on the host machine. Please contact your system administrator |
0xC004FD03 |
No published meaning found | Read the machine’s own text with slui.exe 0x2a 0xC004FD03 |
0xC004FD04 |
No published meaning found | As above |
Which host can activate which guest
| Host version | Guests it can activate |
|---|---|
| Windows Server 2025 | 2025, 2022, 2019, 2016 and 2012 R2 |
| Windows Server 2022 | 2022, 2019, 2016 and 2012 R2 |
| Windows Server 2019 | 2019, 2016 and 2012 R2 |
| Windows Server 2016 | 2016 and 2012 R2 |
| Windows Server 2012 R2 | 2012 R2 only |
The rule that falls out of that table is simple: a host activates its own version and older ones, never a newer one. Upgrading the guests without upgrading the host is the usual way an estate arrives at these codes on a fleet that worked last quarter.
What the host must be, and what the guests may be
- The host must run a Windows Server Datacenter edition with the Hyper-V server host role installed, and it must be activated.
- In a failover cluster, each host requires activation individually for guests to remain activated as they move between nodes.
- The guests are not restricted to Datacenter. Microsoft publishes AVMA keys per version for Datacenter, Standard and, on some versions, Essentials, and states that all editions of eligible versions are supported as guests.
- The Data Exchange integration service, also known as Key-Value Pair Exchange, must be enabled in the virtual machine’s settings.
- AVMA activates Windows Server guests. Windows client guests use other methods.
Where the activity is logged
| Where | Event ID | What it records |
|---|---|---|
| The virtualisation host | 12310 | AVMA activity recorded on the host side |
| The guest virtual machine | 12309 | AVMA activity recorded inside the guest |
Between them those two answer the question people usually ask third: is the guest talking to the host at all. If the guest logs nothing, the conversation is not happening and Data Exchange is the first thing to check. If the host logs an attempt and the guest still fails, the problem is what the host answered rather than whether it was asked.
The Azure case, in full
- Confirm the virtual machine is in Azure and carries an AVMA key. Migration from on-premises is the usual route.
- Install a KMS client key for the installed edition:
slmgr /ipk <product key>. - Clear any pinned host:
slmgr /ckms. - Point at the Azure KMS host:
slmgr /skms azkms.core.windows.net:1688. - Activate:
slmgr /ato, then confirm withslmgr /dlv.
Do not open this work by uninstalling the current key. slmgr /upk drops the machine into an unlicensed state after a restart unless a new key is installed, and Microsoft’s own remediation for this exact case simply installs the new key with slmgr /ipk, which validates it against the installed edition and replaces whatever was there.
When a licence is the actual fix
AVMA is a licensing entitlement rather than a feature you switch on. Microsoft’s requirement is unambiguous: the virtualisation host must run a Windows Server Datacenter edition with the Hyper-V server host role installed, and it must itself be activated. A Standard host cannot serve automatic activation to its guests, and no configuration changes that. If you are consolidating a growing number of Windows Server guests onto one host, Datacenter is genuinely the fix rather than a workaround. We supply Windows Server Datacenter licences and will work out what your specific host needs, including whether licensing the host as Datacenter or licensing the guests individually is the better answer for the number of virtual machines you actually run.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004FD01 |
Windows isn’t running on a supported Microsoft Hyper-V virtualization platform | Microsoft Learn |
0xC004FD02 |
Windows isn’t activated on the host machine. Please contact your system administrator | Microsoft Learn |
0xC004FD03 |
Reported during AVMA activation alongside the codes above. No published meaning | not published by the vendor |
0xC004FD04 |
Reported during AVMA activation alongside the codes above. No published meaning | not published by the vendor |
Confirm the fix worked
- On the host,
slmgr /dlvreports a Datacenter edition with a licence status of Licensed. - On the host,
Get-VMIntegrationService -VMName "YourVM"shows Key-Value Pair Exchange enabled. - In the guest,
slmgr /dlvreports a licence status of Licensed with an automatic virtual machine activation description. - Event ID 12310 on the host and 12309 in the guest record the activity you expect.
- Reboot the guest and confirm it comes back activated without intervention.
Questions people ask about this
Which code means the host is not activated?
0xC004FD02. Microsoft publishes it as Windows not being activated on the host machine. 0xC004FD01 is the other one – Windows not running on a supported Microsoft Hyper-V virtualization platform. Older guidance, including earlier versions of this article, had the two reversed.
Do the guests have to be Datacenter?
No. The host must be Datacenter with the Hyper-V role. Microsoft publishes AVMA keys per Windows Server version for Datacenter, Standard and, on some versions, Essentials, and states that all editions of eligible versions are supported as guests.
Can Windows client guests use automatic activation?
No. It activates Windows Server guests. Windows 10 and Windows 11 virtual machines need KMS, Active Directory-based activation, MAK keys or a subscription entitlement.
Does the guest need network access?
No, and that is much of the point. The exchange runs over the Data Exchange integration component, so a guest with no network adapter can still activate – provided that component is enabled in its settings.
Why did this start after we upgraded the guests?
Because a host can activate its own version and older ones, never a newer one. Upgrading guests past the host version is the common way a working estate produces these codes, and the fix is the host rather than the guests.
