
Microsoft releases fixes for Windows activation error 0x80041008
Microsoft has released fixes for error 0x80041008 affecting some Windows activation and licensing operations after the November 2026 security updates. Support documentation revised on November 13 now points to corrective updates, replacing the earlier position that a resolution was still being developed.
Separate packages for Windows 11 and Windows 10
For Windows 11 version 23H2, KB5136483 advances the operating system to build 22631.7714. This cumulative, non-security out-of-band release also includes the contents of the earlier KB5131087 update. Windows 10 receives KB5136493, producing builds 19044.7850 and 19045.7850 for eligible 21H2 and 22H2 installations.
The Windows 10 scope covers supported configurations such as ESU and Enterprise LTSC 2021, including IoT Enterprise LTSC 2021. It should not be interpreted as an unconditional extension of update eligibility to every Windows 10 computer.

Licensing commands, not universal deactivation
The fault concerned certain operations performed through the Software Licensing Management Tool. Microsoft identified commands used to configure a KMS domain or install product keys among the affected actions. KMS stands for Key Management Service, which organisations use to manage activation.
The main exposure was in organisations relying on command-line tools or automated licensing workflows. Previously activated devices stayed activated. Systems with the correct KMS client key and configuration already in place, and no need to run additional licensing commands, were not expected to be affected. The issue therefore did not mean that every Windows device had lost its licence.
Deployment requires the correct version
The Windows 11 23H2 release is offered through Optional updates in Windows Update and as a standalone download in Microsoft Update Catalog. Organisations using WSUS can import it manually. Microsoft says the changes will reach Windows Update for Business in the next security update.
Administrators should check version compatibility, prerequisites and organisational deployment policies before selecting a package. Microsoft lists no currently known issues for the two new releases; that describes the documentation’s present status rather than guaranteeing compatibility with every environment.
Sources: Microsoft KB5136483, Microsoft KB5136493, Microsoft issue and resolution record.


