Microsoft has acknowledged that its latest Patch Tuesday releases are triggering activation and licensing problems, with systems returning 0x80041008 error codes. A service notification released Wednesday and reviewed by BleepingComputer identifies this as a known issue impacting enterprises that rely on automated activation workflows or the Software Licensing Management Tool (SLMGR) utility.
"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.

The problem emerges when administrators run specific SLMGR commands on Windows 10 (versions 21H2 and 22H2), Windows 11 (version 23H2), and Windows Server systems (2019, 2022, and 2025). The failures occur during execution of slmgr.vbs /skms-domain <domain> and slmgr.vbs /ipk <key> commands.
"Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation," the company explained.
Organizations that have already deployed KMS client keys and do not depend on SLMGR for ongoing license administration will not experience disruption. Microsoft clarified that "Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected."
A resolution is expected within the coming days, though Microsoft is encouraging affected organizations requiring immediate relief to contact Microsoft Support for business assistance.
This incident follows a January issue where Windows license migration failed during system upgrades due to activation server registration problems. Additionally, Microsoft disclosed this week that November 2026 Windows 11 updates refuse to install on machines running the October 2026 preview build, and that recent patches are causing SQL Server performance degradation and stability concerns.