Windows Activation Error 0x80041008 Breaks KMS Setup Scripts
Microsoft says November's Patch Tuesday breaks 2 slmgr commands on Windows 10, 11 23H2 and Server. Activated PCs are safe, but new rollouts could stall.
Hakkı ALKANPublished 4 min read
A new Windows activation error is breaking scripted license setup on business PCs and servers. Microsoft confirmed on Nov. 11, 2026, that its Nov. 10 Patch Tuesday updates can make two slmgr.vbs commands fail with error 0x80041008, "Invalid parameter (SWbemObjectEx)", on Windows 10, Windows 11 23H2 and Windows Server 2019, 2022 and 2025.
The good news for most users is in the same notice: devices that are already activated stay activated. The people who will feel this are IT admins who image new machines, point clients at a KMS server or swap product keys with scripts. Microsoft lists the problem as a known issue in its KB5131087 release notes and says a fix is coming "in the coming days."
What Causes the Windows Activation Error 0x80041008?
The failure sits in the Software Licensing Management Tool, better known as slmgr.vbs, the built-in script admins use to install keys and manage activation from the command line. After the November 2026 security update, Microsoft says activation, Key Management Service (KMS) configuration and product key operations run through slmgr "might fail." KMS is the on-premises activation server many companies use to license volume copies of Windows without contacting Microsoft for every PC.
Microsoft names two commands that trigger the error:
- slmgr.vbs /skms-domain, which tells a PC which DNS domain to search for the company's KMS host.
- slmgr.vbs /ipk, which installs a product key on the device.
Microsoft has not said what in the update causes the bug.
Which Windows Versions and Updates Are Affected?
According to Microsoft's service alert, first reported by BleepingComputer on Nov. 12, the issue is tied to these November cumulative updates. Windows 11 24H2, 25H2, 26H1 and 26H2 are not on the list.
| Windows version | November 2026 update |
|---|---|
| Windows 11 23H2 | KB5131087 |
| Windows 10 22H2 and 21H2 | KB5131096 |
| Windows Server 2025 | KB5131080 |
| Windows Server 2022 | KB5131090 |
| Windows Server 2019 | KB5131085 |
The timing is awkward for Windows 11 23H2. Microsoft's release notes say the November update is the last one for 23H2 Enterprise and Education, so these fleets were already due to move to a newer version.
Will Activated PCs Lose Their License?
No. Microsoft says, "Devices that are already activated remain activated." Machines that already have the right KMS client key and configuration, and do not need to run the affected commands, are not expected to see the error. The same goes for companies that bake the KMS client key into their image and do not use slmgr afterwards.
KMS activations also have a long buffer. Microsoft notes that KMS-activated devices typically stay activated for up to 180 days after a successful activation, so existing PCs are not about to show activation warnings. The risk is new deployments, rebuilt machines and key changes that stall until the fix arrives.
How Can Admins Work Around It Now?
Microsoft has not published a public workaround. It says a mitigation "is available for organizations that need an immediate mitigation" through Microsoft Support for business, and no fix KB number had been posted as of Nov. 13, 2026. Until then, this checklist keeps the damage small:
- Check which deployment, imaging and provisioning scripts call slmgr.vbs /ipk or /skms-domain.
- Pause key changes and KMS reconfiguration on machines that are already activated.
- For new images, consider a build with the KMS client key already embedded, the setup Microsoft says is unaffected.
- Log any 0x80041008 failures by device and update so they can be re-run once the fix ships.
- Open a Microsoft Support for business case if a rollout cannot wait.
Our Take
For home users, this is a non-event: nobody runs slmgr to keep a laptop activated. For IT teams, it is another hit in a rough Patch Tuesday that also produced the KB5132061 install failures on Windows 11. The relative test is simple: if you never touch activation after a PC is set up, you can ignore this. If your onboarding pipeline installs keys by script, treat the November update as a blocker for new machines until Microsoft ships the fix.
Users who only see a desktop watermark have a different problem; our guide on removing the Windows activation watermark covers that case. For the feature side of this month's release, see what the Windows 11 November update added.