Microsoft has issued emergency out-of-band updates for a limited Windows licensing and activation issue affecting certain SLMGR-based workflows after the November 2026 security update. UK buyers running Windows Server volume licensing estates with scripted activation need to check compliance now.
What actually broke
Microsoft's November 2026 security updates introduced a regression in Windows activation and licensing operations that rely on the SLMGR (Software Licensing Management Tool) command-line utility. Specifically, commands such as /skms-domain and /ipk — commonly used in automated KMS configuration and product-key workflows — began returning error 0x80041008 ("Invalid parameter") instead of completing normally.
Microsoft's out-of-band releases cover five platform groups: Windows 10 21H2/22H2, Windows 11 23H2, Windows Server 2019, Server 2022 and Server 2025. Broader coverage has also named Windows 10 Enterprise LTSC 2016 among affected versions, though it is not among the platforms covered by the listed OOB packages. For organisations running imaging pipelines, provisioning scripts or scheduled reactivation jobs, this is not a cosmetic bug — it is a direct hit on license compliance evidence.
The fix: five KBs, two delivery routes
Microsoft released five OOB packages on November 13, matched to 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.
Distribution differs by platform. The Server 2025, Server 2022, Server 2019 and Windows 10 packages are available only via the Microsoft Update Catalog — they won't arrive through normal Windows Update channels, so administrators must pull them manually. The Windows 11 23H2 fix is the exception: it's an optional update reachable through Settings > Windows Update > Advanced options > Optional updates, as well as the Catalog. Microsoft says the cumulative OOB packages include the November security-update improvements alongside the licensing and activation fix.
Who is actually at risk
Not every LTSC or Server deployment loses activation. Microsoft has been explicit that devices already activated remain activated, and that customers with the correct KMS client key and KMS configuration preset in their image — who never invoke the affected SLMGR commands — are not expected to be affected. Successfully KMS-activated clients are generally valid for up to 180 days, but this does not protect new devices that have not activated.
Particular risk falls on new provisioning, reimaging, key changes and other automated licensing workflows that invoke affected SLMGR operations after the November patches landed. That is precisely the workflow pattern common in volume-licensed estates following Windows Server 2025 licensing models, and in organisations exercising Windows Server downgrade rights to run older editions under current agreements.

Why this matters beyond a single bug fix
This activation failure did not arrive in isolation. The same November Patch Tuesday cycle delivered 1,235 fixes, including an Outlook zero-day, as counted by BleepingComputer, while separate acknowledged issues covered SQL Server performance and stability problems, printing failures, and installation errors (0x800F0993 and 0x800F0989) on systems carrying the October 2026 preview update. Treating the activation fix as a stand-alone item risks missing the pattern: November's update train has already prompted several corrective releases and issue acknowledgements.
That makes a disciplined rollout posture more important, not less. Organisations should avoid blanket deferral: Microsoft describes the activation issue as affecting specific SLMGR-based operations, while delaying security updates leaves systems without the November protections, including against the Outlook zero-day. The safer path is applying the corrective package through a controlled validation ring under standard enterprise patch management discipline, confirming both patch compliance and activation status before wider release.
What UK buyers should do this week
Procurement and infrastructure teams running LTSC, Server 2019/2022/2025 or ESU-covered Windows 10 fleets should treat this as an operational checklist item rather than a routine patch note.
- •Inventory every automated job, provisioning script or image build that calls SLMGR, specifically /skms-domain or /ipk
- •Pull the relevant KB from the Microsoft Update Catalog for Server and Windows 10/LTSC builds; use the optional Windows Update path for Windows 11 23H2
- •Verify activation status on freshly provisioned or reimaged devices after patching, not just on already-running systems
- •Hold off relying solely on the 180-day KMS grace period for new builds — it does not help machines that haven't activated yet
- •Confirm the fix doesn't need to be chased through Microsoft Support for Business, which was the interim route before the OOB release landed
- 01BleepingComputer — Microsoft pushes Windows emergency updates to fix activation failures · 16 November 2026
- 02BleepingComputer — Microsoft confirms Windows activation failures after November updates · 11 November 2026
- 03The Register — Microsoft's Patch Tuesday can't break stuff if it won't install · 11 November 2026
- 04The Register — Microsoft has an image problem with November's Windows security update · 12 November 2026
- 05BleepingComputer — Microsoft November 2026 Patch Tuesday fixes 1,235 flaws, Outlook zero-day · 10 November 2026
- 06bleepingcomputer.com
- 07bleepingcomputer.com
- 08bleepingcomputer.com
