Windows Won’t Activate? The slmgr and GVLK Keys You’re Entering Wrong

Activating Windows from a command prompt sounds simple until you hit the part nobody warns you about: which key goes in, and in what order. Editions use different keys, and different commands demand different permissions. Get the sequence wrong and activation simply never starts.

The whole process comes down to two commands. From an administrator command prompt, you install the key with slmgr /ipk and then request activation with slmgr /ato. A KMS host listens on the default port 1688. Below, we lay out the GVLK keys, build numbers, and KMS renewal values for client and server editions in order — plus the one step most guides leave out.

1. The Two Axes of the slmgr Command

slmgr splits into one option that installs a key and one that requests activation. Because their roles and permission needs differ, swapping the order leaves activation stuck.

One thing the two-command summary leaves out: a KMS client has to know which KMS host to talk to. In domains that publish a _vlmcs DNS SRV record, Windows finds the host automatically. If yours doesn’t, point Windows at it before activation with slmgr /skms <kms-host> (for example slmgr /skms kms.corp.local). Run that between /ipk and /ato so activation has a host to reach.

KMS activation does not strictly require admin rights, but /ato can still throw an access-denied error under a standard account. To avoid that, open an administrator CMD first and run every slmgr command in the same window.

2. Windows 10 and 11 Pro and Enterprise Keys

For client editions, you only need to remember two. Pro and Enterprise use different GVLKs, and the values are shared between version 10 and 11.

Run it as slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX — type the hyphens in; the command accepts the full formatted key.

3. Server 2019 GVLK by Edition

On the server side, even the same year splits Standard from Datacenter. For 2019, keep the two values separate.

Do not mix the two keys — same 2019 family, different editions. The OS build for Server 2019 is 17763; that number is what separates the install image families when you pick a download.

4. Server 2022 and Build 20348

The 2022 family follows the same shape: a separate GVLK per edition, with the build number telling it apart from 2019.

Example: slmgr /ipk WX4NM-KYWYW-QJJR4-XV3QB-6VM33. The OS build for Server 2022 is 20348, so a build 20348 machine takes the 2022-family key.

5. KMS Port and Renewal Cycle

If the key is correct but activation still fails, the problem is usually on the network side. One port and two timers make up the default setup.

Both intervals can be set anywhere from 15 minutes to 30 days. If port 1688 is blocked, the activation request never reaches the host in the first place.

6. Updates and Image Integration

A GVLK is fixed per product and edition. Even when a patch bumps the minor build, the family split holds: Server 2019 stays on 17763 and Server 2022 on 20348. Installing from an MSDN image changes nothing about the KMS steps — the flow of installing the matching GVLK and requesting activation is identical.

For mass deployment across many machines, the common pattern is to pre-load the GVLK into the image and run only slmgr /ato after deployment.

3 Mistakes That Break Windows Activation

Summary

At its core it is two steps from an administrator command prompt: install the key, then request activation. Point the client at a KMS host if needed, and port 1688, a 7-day default renewal, and a 2-hour retry interval are the defaults. Because GVLK lists are updated against Microsoft’s official documentation, confirm the latest values before you type a key in.

• Open an administrator CMD before running slmgr /ipk — without the right permission you get an error with no obvious cause.
• Set the KMS host with slmgr /skms when your network has no _vlmcs SRV record.
• Match the key to the edition first. Same 2019, same 2022 — Standard and Datacenter keys differ.
• Use build 17763 for the 2019 family and 20348 for 2022 as your tie-breaker.

Quick reference

• Windows 10/11 Pro: W269N-WFGWX-YVC9B-4J6C9-T83GX
• Windows 10/11 Enterprise: NPPR9-FWDCX-D2C8J-H872K-2YT43
• Server 2019 Datacenter: WMDGN-G9PQG-XVVXX-R3X43-63DFG
• Server 2019 Standard: N69G4-B89J2-4G8F4-WWYCC-J464C
• Server 2022 Datacenter: WX4NM-KYWYW-QJJR4-XV3QB-6VM33
• Server 2022 Standard: VDYBN-27WPP-V4HQT-9VMD4-VMK7H

Frequently Asked Questions

What is a GVLK?

A Generic Volume Licensing Key — Microsoft’s public KMS client key for each Windows edition. It tells the machine to activate against a KMS host rather than a retail or MAK key.

Does slmgr /ato need admin?

KMS activation itself doesn’t strictly require admin rights, but /ato often throws access-denied under a standard account. Run every slmgr command from an elevated (admin) command prompt.

What port does KMS use?

TCP 1688 by default. Change it with slmgr /sprt. If that port is blocked, activation can’t reach the host.

Why does activation fail right after slmgr /ipk?

Usually the client can’t find a KMS host (no _vlmcs record and no /skms set), or port 1688 is blocked. The key installed fine — the request just isn’t getting through.

Can one GVLK activate both Windows 10 and 11?

Yes. The Pro GVLK (W269N-WFGWX-YVC9B-4J6C9-T83GX) and Enterprise GVLK (NPPR9-FWDCX-D2C8J-H872K-2YT43) are shared across Windows 10 and 11.

GVLK values are published by Microsoft and can change; always confirm against the official documentation before activating production systems.

Bookmark this page so you have the GVLK tables and the slmgr flow handy next time an activation stalls — and share it with whoever owns your imaging pipeline. For a related walkthrough, see our guide on clean Windows installs and build selection.