← All Guides
📄

Generic and KMS Product Keys Explained

Why deployment tools use product keys that don’t activate anything: generic edition-selection keys vs. KMS client (GVLK) keys vs. retail/OEM keys, and which one belongs in an answer file.

The product key in an answer file usually isn’t there to activate Windows — it’s there to pick which edition installs. Confusing the three key types leads to wrong-edition installs and “why isn’t it activated?” tickets. Here’s the two-minute version.

The three kinds of keys

  • Generic installation keys — published by Microsoft purely to select an edition (Home/Pro/Enterprise) during setup. They install Windows but never activate it. Perfect for answer files.
  • KMS client setup keys (GVLKs) — also published by Microsoft. They select the edition *and* tell Windows to activate against your organization’s KMS host or Active Directory-Based Activation. Only useful if you actually run volume activation.
  • Retail / OEM / MAK keys — the ones you pay for. They select the edition and activate it. Fine in an answer file for one-off builds, but never bake a paid key into media you’ll reuse broadly.

Why multi-edition media needs a key at all

Official ISOs contain several editions in one image. Setup decides which to install from, in order:

1. The product key in the answer file (or a PID.txt file) 2. Firmware-embedded OEM keys (most laptops carry one — this is why a bare ISO auto-installs Home on consumer hardware!) 3. Asking you interactively

That firmware key is the classic trap: you want Pro, the machine’s embedded Home key wins, and setup never asks. Putting a generic Pro key in the answer file overrides it.

The edition can’t exceed the image

A key can only select an edition that exists in the ISO. Consumer media doesn’t contain Enterprise — an Enterprise GVLK against a consumer ISO sends setup interactive (gotcha #6 in the Answer File Gotchas guide).

What activates the machine, then?

After a generic-key install, activation comes from wherever it normally would:

  • Digital license — hardware previously activated for that edition re-activates automatically once online
  • Firmware OEM key — activates the matching edition it embeds
  • KMS / AD-based activation — for GVLK installs in volume-licensed environments
  • Manually entering a purchased key after install: Settings → System → Activation
Check activation state after install
# Quick activation status
Get-CimInstance SoftwareLicensingProduct -Filter "PartialProductKey IS NOT NULL" |
    Select-Object Name, LicenseStatus   # 1 = activated


# Full details (edition, channel, grace period)
cscript //nologo C:\Windows\System32\slmgr.vbs /dlv

Where to find the official key lists

Don’t copy keys from random forums — Microsoft publishes both lists:

Our Answer File Generator accepts any key type in the product-key field, and the Server Build Wizard pre-fills the correct KMS client key for the Windows Server version you select.

Tools used in this guide

📄

Answer File Generator

Create customized autounattend.xml files for automated Windows 11 installations. Configure privacy, remove bloatware, and customize the interface.

🚀

Step-by-Step Deployment

Complete Windows 11 deployment wizard. Combines answer files with post-installation scripts in a guided workflow.

💻

Windows Server Build Wizard

Guided wizard for automated Windows Server 2019/2022/2025 deployments. Generates answer files, PowerShell configuration scripts, and a ready-to-use ZIP package.