As reported by BleepingComputer, Microsoft has pushed emergency out-of-band (OOB) updates to resolve Windows activation and licensing failures stemming from its November 2026 Patch Tuesday releases. The issue specifically impacts organizations that rely on the Software Licensing Management Tool (SLMGR) command-line tool for automated activation workflows — a common pattern in enterprise imaging, provisioning pipelines, and configuration management tooling.
What Happened and Who Is Affected
The root cause appears to be a regression introduced by the November 2026 cumulative security updates that disrupted SLMGR-based licensing operations. Devices already activated remain unaffected, and environments with KMS client keys preinstalled in their golden images — and that do not invoke the affected Slmgr.vbs commands — are not expected to experience problems.
This narrows the blast radius considerably, but the affected cohort is significant: enterprises using scripted or automated licensing during deployment, organizations managing large fleets through SCCM or similar tools, and environments performing image-based provisioning where activation happens post-deploy. In these scenarios, newly imaged or repaired machines may fail to complete activation, potentially disrupting downstream services, compliance reporting, and KMS-licensed application stacks.
Emergency OOB Updates by Platform
| Platform | KB Article | Distribution Channel |
|---|---|---|
| Windows Server 2025 | KB5136489 | Update Catalog only |
| Windows Server 2022 | KB5136487 | Update Catalog only |
| Windows Server 2019 / Win10 Enterprise LTSC 2019 | KB5136490 | Update Catalog only |
| Windows 11, version 23H2 | KB5136483 | Windows Update + Catalog |
| Windows 10 22H2 ESU / Win10 Enterprise LTSC 2021 | KB5136493 | Update Catalog only |
Notably, most of these OOB packages are available exclusively through the Microsoft Update Catalog — they will not appear in WSUS or standard update channels without manual import. This is a critical operational detail for environments with disconnected or air-gapped update infrastructures.
Why This Matters Beyond the Immediate Fix
This is the third notable Windows update quality issue in recent weeks: January saw similar license migration failures during upgrades, October's updates triggered SQL Server performance problems, and now November's Patch Tuesday has broken SLMGR-based activation. A pattern of regressions in core Windows servicing is emerging, and it has direct implications for how security teams should approach patch management.
The cumulative nature of these OOB updates — they bundle the November security fixes with the licensing repair — means there is no way to address the licensing breakage without also accepting November's security patches. For organizations that had intentionally deferred the November cycle (perhaps due to the SQL Server issues), this compresses their decision window: accept the full November payload or remain exposed to whatever the security fixes address.
Shield53 Recommendations
Immediate Actions
slmgr.vbs /dli and slmgr.vbs /ato on a sample of devices per platform to confirm licensing recovery before broad rollout.Strategic Posture
- Establish patch-canary testing: Given the repeated regressions across October–November, designate a pilot ring of non-critical systems to absorb new cumulative updates for 48–72 hours before broad deployment — especially for server SKUs.
- Diversify activation resilience: Where feasible, preinstall KMS client keys in master images and configure KMS host caching so newly deployed machines can activate without immediately requiring SLMGR operations against a licensing endpoint.
- Catalog-only dependency mapping: Maintain documented procedures for importing Catalog-only OOB updates into WSUS or your endpoint management platform — this is now a recurring pattern and teams should not be improvising the import process under pressure.
For organizations already impacted, the OOB updates should restore normal licensing behavior promptly. For those who had not yet deployed the November cycle, the OOB packages effectively replace the problematic baseline — deploy them directly rather than the original November release to avoid the intermediate break state.