0xc004fd01

1/6/2022by admin

0xC004FD01: Windows isn't running on a supported Microsoft Hyper-V virtualization platform. 0xC004FD02: Windows isn't activated on the host machine. Please contact your system administrator. 0xC004FD03: The host machine can't activate the edition of Windows on the virtual machine. 0xC004FD04: Windows isn't activated.

Automatic Virtual Machine Activation (AVMA) was first introduced in Windows Server 2012 R2. This technology allows to automatically activate all virtual machines with guest Windows Server running on the Hyper-V host with the Windows Server Datacenter edition. Thus, any new virtual machine running Windows Server will be automatically activated when started with no need to use a MAK key, activate a VM on the KMS server, connect to the Internet or manually activate a product.

0xc004fd01

0xc004fd01 Windows Server 2019

Remember that Windows Server Datacenter allows to legally run unlimited number of virtual machines with Windows Server (Windows Server Licensing and Virtualization) and due to AVMA, VM activation can get much easier.

AVMA System Requirements

0xc004fd010xc004fd01

These are the main requirements, aspects and restrictions to bear in mind to automatically activate VMs using AVMA:

  • An activated Hyper-V host running Windows Server 2016 / 2012 R2 Datacenter edition must be used as a hypervisor ( Windows Server 2012, 2008 R2 and 2008 do not support AVMA activation)
  • Windows Server 2016/2012 R2 Datacenter, Standard or Essentials editions may be used as guest OSs on the virtual machines (desktop Windows versions cannot be activated this way)
  • Windows Server 2012 R2 host cannot activate a VM running any Windows Server 2016 edition
  • The public key of AVMA (listed below) must be specified as the product key on guest OSs
  • Integration Services must be installed on a VM, and Data Exchange (Management -> Integration Services) option must be enabled in the VM properties
  • A guest OS must have Microsoft Hyper-V Activation Component (installed during Integration Services setup)

The guest OS of the virtual machine exchanges data about AVMA activation with the Hyper-V host over VMbus using KVP objects (key + value) located in the following registry key: HKLMSoftwareMicrosoftVirtual MachineGuest.

  • Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration.
  • 0xC004FD01: The symbol SLEIAINVALIDVIRTUALIZATIONPLATFORM means 'Windows isn't running on a supported Microsoft Hyper-V virtualization platform.' COM/OLE Interface management.
  • The only way I've found to fix it is to call Microsoft Support at 800-642-7626 and follow the prompts. You'll want technical support, business or private use, etc.
  • I have performed the following steps 1. Slmgr /ipk dbgbw-npf86-bjvtx-k3wkj-mtb6v - this command gets a confirmation message that the key was accepted - i got the key from 2. Slmgr /ato - this command gets an error: 0XC004FD01 On a computer running Microsoft Windows non-core edition.

AVMA Keys for Windows Server 2016 / 2012 R2

To activate guest OSs using AVMA, they must have special AVMA keys which differ depending on the version and edition of the OS.

Here is the list of AVMA keys for different Windows Server versions:

Windows Server 2012 R2

0xc004fd01
EditionAVMA Key
DatacenterY4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
StandardDBGBW-NPF86-BJVTX-K3WKJ-MTB6V
EssentialsK2XGM-NMBT3-2R6Q8-WF2FK-P36R2

Windows Server 2016

EditionAVMA Key
DatacenterTMJ3Y-NTRTM-FJYXT-T22BY-CWG3J
StandardC3RCX-M6NRP-6CXC9-TW2F2-4RHYD
EssentialsB4YNW-62DX9-W8V6M-82649-MHBKQ

An AVMA key has to be specified during guest OS installation or any time after it using the following command run elevated:

0xc004f014

slmgr –ipk <AVMA_Key>

For example,

0xc004f014

slmgr –ipk C3RCX-M6NRP-6CXC9-TW2F2-4RHYD

When activating an OS using AVMA, the event with EventID 12309 appears in the application log of the guest OS, and the event with EventID 12310 — in the hypervisor log. Thus, an administrator can track the licenses issued on a Hyper-V host.

The current activation status of the guest OS can be seen using this command:

slmgr /dli

If a VM is activated using AVMA, you will see the following line: VIRTUAL_MACHINE_ACTIVATION channel.

After activation, guest OSs renew their activation every 7 days.

How to Extend or Shrink Virtual Hard Disks...

December 10, 2020

Take a Screenshot of a User’s Desktop with...

December 8, 2020

0xc004f015

Zerologon (CVE-2020-1472): Critical Active Directory Vulnerability

December 4, 2020

How to Run CMD/Program under SYSTEM (LocalSystem) in...

December 3, 2020

How to Disable/Change User Account Control with Group...

December 1, 2020
Comments are closed.