Windows Server 2025/2022 Product Keys — All Editions, KMS & GVLK (2026)


Need KMS client setup keys (GVLKs) to activate Windows Server in your enterprise environment? Below is the complete, verified list of KMS client keys for Windows Server 2025, 2022, 2019, and 2016 — covering Standard, Datacenter, Datacenter: Azure Edition, and Essentials.
Table of Contents
- Windows Server 2025 KMS Client Keys
- Windows Server 2022 KMS Client Keys
- Windows Server 2019 KMS Client Keys
- Windows Server 2016 KMS Client Keys
- How to Activate Windows Server with KMS
- Server Edition Comparison — Standard vs Datacenter vs Essentials
- Common Server Activation Error Codes & Fixes
- Where to Buy Genuine Windows Server Licenses
- FAQ
Windows Server 2025 KMS Client Setup Keys
Windows Server 2025 is the latest long-term servicing channel (LTSC) release, featuring hotpatching, advanced Active Directory improvements, and tighter Azure hybrid integration. Use these GVLKs for KMS activation in volume licensing deployments.
| Edition | KMS Client Setup Key (GVLK) | Copy |
|---|---|---|
| Windows Server 2025 Standard | TVRH6-WHNXV-R9WG3-9XRFY-MY832 | |
| Windows Server 2025 Datacenter | D764K-2NDRG-47T6Q-P8T8W-YP6DF | |
| Windows Server 2025 Datacenter: Azure Edition | XW7K9-N9MYT-GJCMG-3GXF8-2849D |
Windows Server 2022 KMS Client Setup Keys
Windows Server 2022 introduced secured-core server, TLS 1.3 by default, and Azure Arc integration. Still widely deployed in production environments worldwide.
| Edition | KMS Client Setup Key (GVLK) | Copy |
|---|---|---|
| Windows Server 2022 Standard | VDYBN-27WPP-V4HQT-9VMD4-VMK7H | |
| Windows Server 2022 Datacenter | WX4NM-KYWYW-QJJR4-XV3QB-6VM33 | |
| Windows Server 2022 Datacenter: Azure Edition | NTBV8-9K7Q8-V27C6-M2BTV-KHMXV |
Windows Server 2019 KMS Client Setup Keys
Windows Server 2019 remains in mainstream support and is one of the most common server OS versions in enterprise data centers. These are the official KMS client keys for all three editions.
| Edition | KMS Client Setup Key (GVLK) | Copy |
|---|---|---|
| Windows Server 2019 Standard | N69G4-B89J2-4G8F4-WWYCC-J464C | |
| Windows Server 2019 Datacenter | WMDGN-G9PQG-XVVXX-R3X43-63DFG | |
| Windows Server 2019 Essentials | WVDHN-86M7X-466P6-VHXV7-YY726 |
Windows Server 2016 KMS Client Setup Keys
Windows Server 2016 is in extended support (ending January 2027). If you're still running 2016, consider planning your migration to Server 2025 or 2022. Need help? Our server support team can assist with upgrades.
| Edition | KMS Client Setup Key (GVLK) | Copy |
|---|---|---|
| Windows Server 2016 Standard | WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY | |
| Windows Server 2016 Datacenter | CB7KF-BWN84-R7R2Y-793K2-8XDDG | |
| Windows Server 2016 Essentials | JCKRF-N37P4-C2D82-9YXRT-4M63B |
How to Activate Windows Server with KMS
Method 1: Install Key During Setup
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.
Method 2: Install Key via Command Line (After Installation)
Open an elevated Command Prompt or PowerShell on the server and run:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
Replace XXXXX-XXXXX-XXXXX-XXXXX-XXXXX with the GVLK for your server edition. The first command installs the product key, and the second command triggers activation against your KMS server.
Method 3: Set KMS Server Manually
If the server cannot auto-discover your KMS host via DNS SRV records:
slmgr /skms your-kms-server.domain.com
slmgr /ato
To verify the KMS host is configured correctly:
slmgr /dlv
This displays detailed license information, including the KMS server name, activation status, and license expiry.
Method 4: PowerShell Activation
For scripted or remote activation across multiple servers:
# Install the product key
Install-WindowsProductKey -ProductKey "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
# Or use slmgr via PowerShell remoting for multiple servers
$servers = @("SRV01","SRV02","SRV03")
foreach ($srv in $servers) {
Invoke-Command -ComputerName $srv -ScriptBlock {
cscript //nologo C:\Windows\System32\slmgr.vbs /ipk "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
cscript //nologo C:\Windows\System32\slmgr.vbs /ato
}
}
Server Edition Comparison — Standard vs Datacenter vs Essentials
Choosing the right Windows Server edition depends on your virtualization needs, workload requirements, and budget. Here's how they stack up:
| Feature | Standard | Datacenter | Essentials |
|---|---|---|---|
| License Model | Core-based (16-core min.) | Core-based (16-core min.) | Server-based (1 license per server) |
| Virtualization Rights | Up to 2 VMs (or Hyper-V containers) | Unlimited VMs | Not licensed for virtualization host |
| Max RAM | 24 TB | 24 TB | 64 GB |
| Max Users (CALs) | Unlimited (with CALs) | Unlimited (with CALs) | 25 users / 50 devices (no CALs needed) |
| Storage Spaces Direct | No | Yes | No |
| Software-Defined Networking | No | Yes | No |
| Shielded VMs | No | Yes | No |
| Hot Patching (Server 2025) | No | Yes (with Azure Arc) | No |
| Azure Edition Features | N/A | SMB over QUIC, extended network for Azure | N/A |
| Best For | Physical servers, light virtualization | Heavily virtualized environments, HCI | Small businesses (up to 25 users) |
| Approximate Cost | $1,069 (16-core) | $6,155 (16-core) | $501 (per server) |
Common Server Activation Error Codes & Fixes
| Error Code | What It Means | How to Fix |
|---|---|---|
0xC004F074 |
KMS server not found — the server cannot contact a KMS host for activation. | Check DNS for the _vlmcs._tcp SRV record. Manually set the KMS host with slmgr /skms kms-server.domain.com then run slmgr /ato. Verify port 1688 is open on the firewall between the client and the KMS host. |
0xC004F038 |
KMS host count insufficient — the KMS host hasn't reached the minimum activation threshold. | KMS requires at least 5 unique server activation requests within 30 days. If you have fewer than 5 servers, consider using MAK activation or Active Directory-based activation instead. |
0xC004C003 |
The activation server determined the specified product key has been blocked. | The product key has been blocked by Microsoft (possibly due to misuse). Contact Microsoft Volume Licensing support to resolve, or use a different MAK key from the Volume Licensing Service Center (VLSC). |
0xC004F069 |
Product key not found — the GVLK doesn't match the installed server edition. | Verify you're using the correct key for your exact edition (Standard vs Datacenter). Run DISM /online /Get-CurrentEdition to check, then install the matching GVLK with slmgr /ipk. |
0x8007232B |
DNS name does not exist — KMS SRV record not found in DNS. | Your DNS doesn't have the KMS auto-discovery record. Either create a _vlmcs._tcp.domain.com SRV record pointing to your KMS host on port 1688, or manually specify the KMS host with slmgr /skms. |
0xC004F056 |
Edition mismatch — you're trying to activate with a key that doesn't match the installed edition. | If you need to switch editions (e.g., Standard to Datacenter), use DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX /AcceptEula. This performs an in-place edition upgrade. |
0xC004E015 |
SL_E_EUL_CONSUMPTION_FAILED — license has expired or is corrupt. | Clear the current license with slmgr /upk (uninstall product key), then reinstall with slmgr /ipk YOUR-KEY and activate with slmgr /ato. If the issue persists, rebuild the token store: stop the Software Protection service, delete C:\Windows\System32\spp\store\2.0\tokens.dat, restart, and re-key. |
0xC004F042 |
KMS host key count has dropped below the threshold. | KMS activations expire after 180 days. If machines have been decommissioned, the count drops. Re-activate additional machines, or switch to Active Directory-based activation (ADBA) which doesn't require thresholds. |
slmgr /dlv on any server to see its full activation status, including the KMS host it's contacting, the activation count, and the next renewal time. For bulk troubleshooting across multiple servers, our server support engineers can audit and remediate activation issues across your entire fleet.
Where to Buy Genuine Windows Server Licenses
- Microsoft Store — Direct purchase at retail pricing. Includes Windows Server 2025 Standard and Datacenter editions with full support.
- Volume Licensing (EA/MPSA/CSP) — For organizations with multiple servers, Microsoft offers volume licensing through Enterprise Agreements, MPSA, or Cloud Solution Provider (CSP) programs. This is the most cost-effective option at scale.
- OEM Licensing — Windows Server licenses bundled with hardware from Dell, HPE, Lenovo, etc. Typically the cheapest per-server option, but locked to that physical hardware.
- Medha Cloud (Microsoft Solutions Partner) — We provide Windows Server licensing through CSP at partner pricing, including deployment, migration, and ongoing server management. Whether you need on-premises Server 2025 or Azure hybrid infrastructure, we handle the full stack. Get a quote.
Frequently Asked Questions
Are these Windows Server product keys legal?
Yes. These are KMS client setup keys (GVLKs) publicly documented by Microsoft for volume licensing environments. Microsoft publishes them in their official documentation. They are intended for enterprise KMS activation, not for piracy.
Do I need a KMS server to use these keys?
Yes. GVLKs require a KMS host server running on your network. The KMS host must have a valid KMS host key (CSVLK) installed and must meet the minimum activation threshold of 5 servers. Without a KMS host, these keys will install but will not activate. For environments without KMS, use MAK keys or Active Directory-based activation.
What's the difference between KMS, MAK, and ADBA activation?
KMS (Key Management Service) uses GVLKs and a local KMS host server. Activations renew every 180 days. Best for large environments with 5+ servers. MAK (Multiple Activation Key) activates directly with Microsoft's activation servers — each key has a limited number of activations. Best for small environments or disconnected machines. ADBA (Active Directory-Based Activation) uses Active Directory Domain Services to activate domain-joined machines automatically. No thresholds required. Best for domain environments running Server 2012 R2 or later.
Can I upgrade from Standard to Datacenter without reinstalling?
Yes. You can perform an in-place edition upgrade using DISM:
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
Replace the product key with the Datacenter GVLK (or your MAK key). The server will restart and upgrade the edition while preserving all roles, features, and data.
How often does KMS activation renew?
KMS-activated servers renew their activation every 180 days (6 months) automatically. The server attempts renewal every 7 days. If the KMS host is unreachable for 180 days, the server enters a 30-day grace period before deactivating. This means you have a total of 210 days before any impact if your KMS host goes offline.
Do I need Client Access Licenses (CALs) with Windows Server?
For Standard and Datacenter editions, yes — every user or device that accesses the server needs either a User CAL or Device CAL. Essentials does not require CALs but is limited to 25 users and 50 devices. CALs are a separate purchase from the server license.
What is Datacenter: Azure Edition?
Datacenter: Azure Edition is a special version that runs only on Azure or Azure Stack HCI. It includes exclusive features like SMB over QUIC (for VPN-less file access), hotpatching (apply updates without rebooting), and extended networking for Azure hybrid scenarios. You get Datacenter: Azure Edition through your Azure subscription — no separate purchase needed.
Is Windows Server 2016 still supported?
Windows Server 2016 is in extended support until January 12, 2027. This means it receives security updates only — no new features or bug fixes. We strongly recommend planning your migration to Server 2025 or 2022 before support ends. Our server support team can handle the migration with minimal downtime.
Can I use these keys for Azure VMs?
Azure VMs are automatically activated through Azure's built-in KMS service. You generally don't need to manually enter a product key for Windows Server VMs in Azure. If you do encounter activation issues on an Azure VM, ensure the VM can reach kms.core.windows.net on port 1688 and use the standard GVLK for your edition.
Migrate servers, databases, and applications to Azure with zero downtime guaranteed.
Professional Azure MigrationTopics

Sreenivasa Reddy G
Founder & CEO • 15+ years
Sreenivasa Reddy is the Founder and CEO of Medha Cloud, recognized as "Startup of the Year 2024" by The CEO Magazine. With over 15 years of experience in cloud infrastructure and IT services, he leads the company's vision to deliver enterprise-grade cloud solutions to businesses worldwide.