Microsoft issues emergency Windows updates for activation failures caused by November patches
Microsoft says November's security updates broke activation for organisations that script licensing with SLMGR, and has shipped out-of-band fixes for Windows 10, Windows 11 and Windows Server.
By Mr Elite Published 5 min read
- Severity
- Low
- Status
- Confirmed by the organisation
- Sources
- 1
- Last checked
The short version
- Microsoft released out-of-band updates, according to BleepingComputer, to fix activation and licensing failures caused by November 2026 security updates.
- The known issue affects organisations that use the SLMGR command-line tool to automate activation, Microsoft said.
- Devices that are already activated remain activated, Microsoft said.
- Most of the fixes are available only through the Microsoft Update Catalog; the Windows 11 23H2 update is optional via Windows Update.
What happened
Microsoft has released emergency updates to fix Windows activation and licensing failures that its own November 2026 security updates caused, BleepingComputer reported on 16 November.
The company confirmed the problem in a service alert on a Wednesday. It said the issue affects organisations that use the Software Licensing Management Tool, known as SLMGR, a command-line tool that administrators use to automate activation and licensing.
On Friday, Microsoft released several out-of-band updates, meaning fixes issued outside the normal monthly Patch Tuesday cycle. They cover Windows 10 21H2 and 22H2, Windows 11 23H2, and Windows Server 2019, 2022 and 2025, BleepingComputer said.
Two of the named packages are KB5136490, for Windows Server 2019 and Windows 10 Enterprise LTSC 2019, and KB5136493, for Windows 10 22H2 ESU and Windows 10 Enterprise LTSC 2021. For Windows Server 2025, 2022 and 2019 and for Windows 10, the updates are available only through the Microsoft Update Catalog.
The Windows 11 23H2 update is optional. It is offered through Windows Update under Settings, Windows Update, Advanced options, Optional updates, and also through the Catalog. Microsoft said the cumulative update includes the improvements from the November 2026 security update.
Why it happened
Microsoft has attributed the failures to this month's security updates, according to BleepingComputer. The reported detail stops there: the coverage does not describe which change broke activation or why SLMGR commands were affected.
Microsoft said 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. It also said activated devices stay activated.
Microsoft has not published, in the material BleepingComputer cites, the exact error users see or a technical explanation of the fault.
How this kind of failure works
Large organisations rarely type product keys into each PC. They run a Key Management Service (KMS) server inside the network, and Windows machines contact it to activate themselves. Administrators then use scripts and SLMGR to install client keys, point machines at the server and check licence status.
A security update replaces system files, and a change in one component can break behaviour that another tool depends on. Activation is a good example because it sits in a rarely tested corner: it runs when a machine is built or re-licensed, not every day.
Picture an IT team rebuilding forty laptops on a Monday. Their build script calls SLMGR to set the client key. After a patched image goes out, that step fails, and the laptops are left unlicensed. Nothing was attacked, but the team cannot finish the job.
This is why patch quality matters to security teams as well as to administrators. A bad update that blocks deployment pushes people to delay patching, and unpatched systems stay exposed to the vulnerabilities the update was meant to close.
Who is affected
Microsoft said the issue affects organisations that use SLMGR to automate activation and licensing. Home users who activate through normal means are not described as affected in the reporting.
The fixes cover Windows 10 21H2 and 22H2, Windows 11 23H2, and Windows Server 2019, 2022 and 2025. You can tell whether you are in scope by checking whether your build or imaging scripts run Slmgr.vbs commands after the November update is installed.
In practice, already-activated devices keep working. The exposure falls on new builds, reimaged machines and any workflow that must run the affected commands.
How to defend against it
Tick each step as you check it. Your progress is saved on this device.
What to learn from this
The concept: Patch management with staged rollout
Patching has two risks: leaving a known flaw open, and installing a fix that breaks something. Staged rollout, where updates reach a small test group before everyone else, handles both. You still patch quickly, but a fault hits ten machines instead of ten thousand.
The same idea applies to endpoint agent updates, firmware and cloud configuration changes. Any change pushed widely benefits from a canary group that mirrors real workloads, including the unglamorous tasks such as building and licensing a new machine.
Test updates on a small, representative group first so a faulty patch costs you hours, not a whole fleet.
Quick check
Sign in to earn 10 XP for a right answer
Why does a staged rollout help when an update turns out to be faulty?
A pilot group exposes problems early, so only a few machines are affected before you widen deployment.
Timeline
- October 2026 Windows updates released since October Patch Tuesday later linked by Microsoft to SQL Server performance and stability issues.
- November 2026 Microsoft's November security updates cause activation and licensing failures for SLMGR users.
- Wednesday (before 16 November) Microsoft confirms the known issue in a service alert.
- Friday (before 16 November) Microsoft releases out-of-band updates for Windows 10, Windows 11 and Windows Server.
- 16 November 2026 BleepingComputer reports the emergency updates.
What is not known yet
- Which specific change in the November updates caused the failures, as Microsoft has not said in the reported material.
- How many organisations were affected.
- Whether fixes will be offered through Windows Update for the platforms limited to the Update Catalog.
Questions people ask
Do I need the emergency Windows update?
Only if your organisation uses SLMGR to automate activation and licensing. Microsoft said devices with the right KMS client key and configuration, which do not need the affected Slmgr.vbs commands, are not expected to be affected.
Will my activated PCs stop working?
No. Microsoft said devices that are already activated remain activated. The problem concerns running the affected commands, for example when building or relicensing machines.
Where do I download the fix?
For Windows Server 2025, 2022 and 2019 and for Windows 10, the updates are available only from the Microsoft Update Catalog. The Windows 11 23H2 update is optional and appears under Settings, Windows Update, Advanced options, Optional updates.
Is this a security vulnerability?
Microsoft described it as a known issue that causes activation and licensing failures, not as an attack or a security flaw. The fix includes the improvements from the November 2026 security update.
Sources
- BleepingComputer: Microsoft pushes Windows emergency updates to fix activation failures