Windows Server 2025 / 2022 / 2019 / 2016 Product Keys

Windows Server 2025 is the latest Long-Term Servicing Channel (LTSC) release, featuring hotpatching support, advanced Active Directory improvements, and tighter Azure hybrid integration. Use these GVLKs for KMS activation in volume licensing deployments.

Windows Server 2022 introduced secured-core server capabilities, TLS 1.3 by default, and Azure Arc integration. It remains widely deployed in production environments worldwide and is a solid choice for organizations not yet ready to migrate to Server 2025.

Windows Server 2019 remains in mainstream support and is one of the most common server OS versions in enterprise data centers globally. These are the official KMS client keys for all three editions.

Windows Server 2016 is in extended support until January 12, 2027 — security patches only, no new features. If you’re still running Server 2016, now is the time to plan your migration to Server 2025 or 2022.

There are four primary methods to activate Windows Server using KMS client setup keys. Choose the method that best fits your deployment scenario.

When installing Windows Server from volume licensing media (ISO), the installer prompts for a product key. Enter the appropriate GVLK from the tables above. The server will automatically attempt KMS activation once it connects to your network and discovers a KMS host via DNS SRV auto-discovery.

Open an elevated Command Prompt or PowerShell on the server and run:

# Install the product key (replace with your edition GVLK)
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

# Trigger activation against the KMS host
slmgr /ato

The /ipk command installs the product key. The /ato command triggers activation against your KMS server.

If the server cannot auto-discover the KMS host via DNS SRV records, point it manually:

# Manually point to your KMS host
slmgr /skms your-kms-server.domain.com

# Trigger activation
slmgr /ato

# Verify full license details
slmgr /dlv

The slmgr /dlv command displays the KMS server name, activation status, remaining grace period, and next renewal timestamp — useful for troubleshooting.

For scripted or remote activation across multiple servers in your environment:

# Bulk activate via PowerShell remoting
$servers = @("WS2025-DC01", "WIN11-CLIENT01", "WIN11-CLIENT02")

foreach ($srv in $servers) {
    Invoke-Command -ComputerName $srv -ScriptBlock {
        $key = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
        cscript //nologo C:\Windows\System32\slmgr.vbs /ipk $key
        cscript //nologo C:\Windows\System32\slmgr.vbs /ato
    }
}

Choosing the right Windows Server edition depends on your virtualization density, workload requirements, compliance needs, and budget.

If Windows Server activation fails, these are the most common error codes and how to resolve each one quickly:

Always purchase Windows Server licenses through legitimate channels. Using pirated or illegitimate keys violates Microsoft licensing terms and exposes your organization to legal and security risks.