AVMA Explained — Automatic Virtual Machine Activation on Windows Server

How AVMA works

A Datacenter-edition Hyper-V host carries the entitlement for the guests it runs. When a supported guest boots with an AVMA key installed, it activates through the hypervisor's integration channel rather than over the network. The guest needs no internet access at all.

Requirements

AVMA only applies in a specific configuration.

• The Hyper-V host must run Windows Server Datacenter and be activated itself
• The guest must be a supported Windows Server edition for that host generation
• The guest must have an AVMA key installed, not a KMS or retail key
• Client editions of Windows are not covered by AVMA

AVMA versus KMS versus MAK

KMS activates clients against a host on the network with a renewing 180-day lease. MAK activates once against Microsoft and consumes a seat from a fixed count. AVMA activates a guest against its hypervisor and re-validates while the VM keeps running on a licensed host. Datacenter licensing is what makes the third option possible.

Verifying a guest

Confirm the result inside the VM.

• Run `slmgr /xpr` to see whether the licence is permanent or has an expiry date
• Run `slmgr /dli` for the licence channel (Retail, OEM, Volume) and the last five key digits
• Open Settings › System › Activation for the plain-language activation state
• For Office, run `ospp.vbs /dstatus` from the Office install folder

Legal ways forward

Whatever the environment, the compliant options are the same.

• A valid Microsoft licence, digital licence or volume agreement is the only fully compliant route
• Windows runs without activation — you get a watermark and locked personalisation, security updates still install
• Office without a licence opens files read-only; the free web and mobile apps stay fully usable
• Business, school and production machines should use the organisation's own licensing agreement

AVMA System Requirements & Compatibility (2026)

AVMA is engineered for the modern Microsoft activation stack. The tool runs on Windows 7 SP1, Windows 8.1, Windows 10 (all builds from 1507 to 22H2) and every Windows 11 release including 23H2 and 24H2. Both x64 and ARM64 hardware are supported, and the activator also recognises Server SKUs such as Server 2016, 2019 and 2022. On the Office side, Click-to-Run installations of Office 2013, 2016, 2019, 2021, 2024 and Microsoft 365 are detected automatically — including LTSC channels. You do not need to uninstall a previous KMS client or remove an existing product key: the script reads the current edition through slmgr and routes it to the correct activation method (HWID for Windows, Ohook for Office).

• Windows 7 SP1 / 8.1 / 10 / 11 — all editions (Home, Pro, Education, Enterprise, IoT, LTSC)
• Windows Server 2008 R2 through Server 2025
• Office 2010, 2013, 2016, 2019, 2021, 2024 and Microsoft 365 Apps
• Architectures: x86, x64, ARM64
• .NET Framework 4.6+ (preinstalled on Windows 8.1 and later)

AVMA Troubleshooting: Common Errors & Fast Fixes

Most AVMA failures fall into three buckets: antivirus interference, missing administrator rights, or a corrupted Software Protection Service. If you see error 0xC004F074 the KMS host could not be contacted — disable Defender real-time scanning for two minutes, then re-run the activator. Error 0xC004C003 means the product key is blocked by Microsoft; switch to the HWID method, which bypasses key validation entirely by binding the licence to your motherboard's hardware ID. Error 0x80070005 (Access Denied) is always a UAC issue — right-click the executable and select "Run as administrator". If activation succeeds but reverts after reboot, open services.msc, set "Software Protection" to Automatic, and restart sppsvc.exe. For Office, run the Office Click-to-Run repair from Settings → Apps → Microsoft 365 → Modify → Quick Repair before retrying Ohook.

• 0xC004F074 — pause antivirus, re-run as administrator
• 0xC004C003 — switch to HWID (no key required)
• 0x80070005 — UAC denied, use "Run as administrator"
• Activation reverts on reboot — set "Software Protection" service to Automatic
• Office not detected — run Quick Repair, then re-run Ohook