"Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys," Microsoft said.
Microsoft service alert: what failed and who reported it
Microsoft confirmed in a service alert — reported to BleepingComputer — that the November Patch Tuesday security updates introduced a known issue that disrupts Windows activation and licensing. The failure manifests as error code 0x80041008 and the accompanying message "Invalid parameter (SWbemObjectEx)." Microsoft framed the problem as specifically affecting organizations that automate activation and licensing or that use the Software Licensing Management Tool (SLMGR) command-line utility.
Commands and OS versions where failures occur
According to Microsoft, activation failures occur after executing two SLMGR commands: slmgr.vbs /skms-domain <domain> and slmgr.vbs /ipk <key>. The company named the client and server releases involved: client systems running Windows 10 21H2, Windows 10 22H2, and Windows 11 23H2, and server systems running Windows Server 2019, Windows Server 2022, and Windows Server 2025.
This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildWho Microsoft says is unaffected
Microsoft qualified the scope explicitly. Devices that are already activated remain activated, the company noted. Customers that have the KMS client key already installed in their image and do not rely on SLMGR for licensing management are not expected to be impacted. In other words, organizations that do not need to run the affected slmgr.vbs commands and that already possess the appropriate KMS client key and configuration should not see an activation interruption.
Mitigation, support and Microsoft’s timeline
Microsoft said a fix will be made available "over the coming days." For organizations that need immediate mitigation, Microsoft advised contacting Microsoft Support for business. The alert also points out an operational buffer for many KMS-activated devices: "KMS-activated devices typically remain activated for up to 180 days following successful activation," which may lessen the urgency for some deployments but does not eliminate the need to resolve activation or configuration changes.
Context inside November 2026 update activity
Microsoft’s service alert sits alongside other update-related problems the company acknowledged this week. The vendor confirmed that November 2026 Windows 11 security updates fail to install on systems that have the October 2026 preview update installed, and that Windows updates released since the October Patch Tuesday are linked to SQL Server performance and stability issues. Earlier in the year, in January, Microsoft addressed a different known issue that caused Windows license migration failures during upgrades because affected devices could not register with the Windows Activation server for digital licenses.
What this means for technologists, procurement, and end users
- Technologists and security teams: Watch for error 0x80041008 and failures tied to the slmgr.vbs commands listed by Microsoft; avoid running those SLMGR operations when possible until the vendor’s fix is applied and engage Microsoft Support for business if immediate activation changes are required.
- Procurement and enterprise IT leaders: Inventory images for the presence of KMS client keys and assess whether your deployment workflows rely on SLMGR automation; devices that already carry the correct KMS client key and configuration are not expected to be affected.
- End users and administrators: Understand that devices already activated should remain functional and that KMS-activated devices typically retain activation for up to 180 days after a successful activation, but planned activation or reconfiguration tasks may need to wait until Microsoft’s patch or guidance arrives.
Microsoft’s acknowledgement narrows the problem to a specific set of commands and operating system builds, and it offers a short runway — days, not weeks — for a formal fix. Until then, organizations that automate activation or that rely on SLMGR face a clear operational choice: postpone SLMGR-driven changes or involve Microsoft Support for business to pursue immediate mitigation.
