Skip to content
audiotale.net
Sign in
GuidesExplainer

slmgr.vbs and KMS activation explained: commands, 0x80041008 and how renewal works

What slmgr.vbs does, which options only read status, how KMS hosts activate Windows clients, and why November 2026's 0x80041008 error hit administrators' scripts.

audiotale.net team

· 7 min read

Written by AI from the sources linked below. How we use AI

On this page
  1. In short
  2. Why this is in the news
  3. What slmgr.vbs is
  4. Commands that only read information
  5. Commands that change things
  6. How KMS works
  7. The activation threshold
  8. Validity and renewal
  9. Finding the host
  10. How many hosts you need
  11. Setting up a KMS host
  12. A troubleshooting checklist
  13. What we don't know
  14. Sources

In short

slmgr.vbs is the Visual Basic script built into Windows for managing licensing and activation from the command line. In organisations, most machines do not activate against Microsoft directly: they are Key Management Services (KMS) clients that renew their activation from a KMS host on the local network. Microsoft's November 2026 security update briefly broke some slmgr operations with error 0x80041008, which is why many administrators are looking at these tools this week. This guide explains what each piece does, which commands are safe to run when you are only checking status, and how a KMS client stays activated.

Why this is in the news

On 13 November 2026 Microsoft published an out-of-band update to address an issue affecting a limited number of enterprise devices after the November 2026 Windows security update. According to Microsoft's Windows message centre, certain licensing and activation operations that use the Software Licensing Management Tool (SLMGR) might fail with error 0x80041008 (Invalid parameter). It mainly affects organisations using slmgr.vbs commands or automated processes to configure KMS activation, install product keys or manage Windows licensing. Microsoft says devices that are already activated remain activated.

The fixes are separate packages per platform: KB5136489 for Windows Server 2025, KB5136487 for Windows Server 2022, KB5136490 for Windows Server 2019 and Windows 10 Enterprise LTSC 2019, KB5136483 for Windows 11 version 23H2, and KB5136493 for Windows 10 version 22H2 ESU and Windows 10 Enterprise LTSC 2021. For most of these the update is available only from the Microsoft Update Catalog; the Windows 11 23H2 package is also offered through Windows Update, under Settings > Windows Update > Advanced options > Optional updates. Our news report on error 0x80041008 covers the incident itself; this guide covers the background you need to understand it.

What slmgr.vbs is

Microsoft documents slmgr.vbs as a Visual Basic script included in Windows that serves as a command-line tool for managing the operating system's licensing and activation. It can install and change product keys, activate Windows, check the current activation or licensing status, extend the activation grace period (rearm) and help troubleshoot activation problems. Its syntax is slmgr.vbs [<ComputerName> [<User> <Password>]] [<Options>].

For remote clients, Microsoft's documentation points to the Volume Activation Management Tool (VAMT) version 1.2 or later, or custom WMI scripts, and notes that slmgr.vbs is not intended to work across platforms.

Commands that only read information

These do not require elevation, according to Microsoft:

  • /dli displays licence information for the installed, active Windows edition. /dli All shows every applicable installed product.
  • /dlv displays detailed licence information; with an Activation ID it shows that edition only, and /dlv All covers everything installed.
  • /xpr displays the activation expiration date. Microsoft notes this is primarily useful for KMS clients, because activation by Multiple Activation Key (MAK) and retail activation is perpetual.

If you only want to know whether a machine is activated, slmgr.vbs /dlv and /xpr read information without changing anything. Activation IDs, which some options accept, can be listed with slmgr.vbs /dlv all.

Commands that change things

These need an elevated Command Prompt (or the Standard User Operations registry value set to allow extra access to the Software Protection Service), per Microsoft:

  • /ipk <ProductKey> installs a 5x5 product key. The key is checked for validity and applicability to the installed operating system; if a key is already installed, it is silently replaced. Microsoft advises restarting the system or the Software Protection Service afterwards to prevent instability in the license service.
  • /ato asks Windows to try activation. On retail editions and on volume systems with a KMS host key or MAK installed it tries online activation; on systems with a Generic Volume License Key (GVLK) it triggers a KMS activation attempt.
  • /upk uninstalls the product key of the current edition; after a restart the system is unlicensed unless a new key is installed.
  • /rearm resets the activation timers (the same call that sysprep /generalize makes).
  • /ilc installs a license file and /rilc reinstalls licenses stored in %SystemRoot%\system32\oem and %SystemRoot%\System32\spp\tokens.
  • /dti shows the installation ID for offline activation and /atp <Confirmation ID> activates using a confirmation ID you supply.

Be careful with /ipk and /upk on production machines, especially in scripts: the first replaces a key without asking, and the second leaves the system unlicensed after a restart.

How KMS works

KMS is Microsoft's volume activation method for networks. Its clients connect to a server called the KMS host on your local network. The host itself must be activated with a special key, formally a Customer Specific Volume License Key (CSVLK), which you obtain from the Product Keys section of the Volume Licensing Service Center for agreements such as Open, Open Value, Select, Enterprise and Services Provider License, or via a local Microsoft Activation Center.

Computers running volume-licensing editions of Windows Server and Windows client are KMS clients by default, with no extra configuration. If you are converting a machine from a KMS host, MAK or retail edition to a KMS client, you install the applicable KMS client setup key.

The activation threshold

KMS only activates clients once enough computers have asked for activation. Microsoft calls this the activation threshold: clients activate if the count the host returns is 25 or higher, and servers and volume editions of Office activate if it is five or greater. The host counts unique connections from the past 30 days and stores the 50 most recent contacts.

Validity and renewal

A KMS activation is valid for 180 days (the activation validity interval). Clients must contact the KMS host at least once in that period to stay activated; by default they try to renew every seven days, and after a renewal the 180-day clock starts again. Using /sai you can set the interval, between 15 minutes and 30 days, at which an unactivated client retries; the default is two hours, which Microsoft recommends.

Finding the host

By default, KMS hosts publish Service (SRV) resource records in DNS through dynamic updates, so clients find them without any configuration. Communication uses TCP, on port 1688 by default. You can instead point a client at a specific host with /skms <Name[:Port]>, which disables auto-detection; use /skms-domain <FQDN> to tell the client which DNS domain holds the SRV records (it has no effect when a single host is set with /skms); and /ckms clears the setting and restores autodiscovery. With host caching (/skhc, the default), a client that has found a working host sticks with it until it can no longer be reached; /ckhc disables caching so DNS priority and weight apply each time. Microsoft recommends disabling caching when you use priority and weight.

How many hosts you need

A single KMS host can support an unlimited number of clients. Microsoft recommends at least two hosts if you have more than 50 clients, so activation continues if one is unavailable, and says most organisations can operate with as few as two for their whole infrastructure. A CSVLK can activate up to five more hosts for a total of six, and a host can be reactivated up to nine times with the same key.

Setting up a KMS host

Microsoft's guide for Windows Server describes the steps. You need a computer running a supported Windows Server or Windows client, an Administrators account, a KMS host key and internet access (or phone activation) to activate the host. A host on Windows Server can activate both server and client operating systems; a host on a Windows client can only activate other clients, and the version of Windows on the host determines which versions it can activate.

  1. Install the role from an elevated PowerShell session: Install-WindowsFeature -Name VolumeActivation -IncludeManagementTools.
  2. Allow KMS traffic through Windows Firewall. To limit it to Domain and Private profiles: Set-NetFirewallRule -Name SPPSVC-In-TCP -Profile Domain,Private -Enabled True.
  3. Run vmw.exe to open the Volume Activation Tools wizard, choose Key Management Service (KMS), enter localhost for the local server, install your KMS host key, then activate it online or by phone.

A troubleshooting checklist

  • Check status first. Run /dlv and /xpr before changing anything; they need no elevation.
  • Check the network. Confirm the client can reach the host on TCP 1688, and that DNS returns the SRV records, or that /skms points to the right name.
  • Check the count. If the host's count is below the threshold (25 for clients, five for servers), clients will not activate.
  • Check KMS host updates. Microsoft warns that Windows updates might be required on the KMS server to support activation of newer clients, so check the activation-versions table in its planning guide.
  • After the November 2026 update, if slmgr fails with 0x80041008, install the package listed above for your platform. Microsoft says activated devices remain activated, so a failing script does not by itself mean machines lost activation.

What we don't know

Microsoft's message says the issue affects "a limited number" of enterprise devices and does not give a count. We have not confirmed which specific slmgr options fail, beyond Microsoft's description of KMS configuration, product keys and licensing management.

Sources

Written by

audiotale.net team

The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.