November 17, 2026

Microsoft Ships Emergency Windows Fixes for November’s Activation Bug: The Spec Sheet and an Install Checklist

Microsoft has released out-of-band updates for Windows 10, Windows 11 23H2 and Windows Server 2019 through 2025 to fix activation and licensing errors caused by this month’s security updates. Here are the KB numbers, where to get them, who actually needs them, and a short checklist.

An IT technician in a charcoal polo shirt checking a tablet in a bright office IT room lined with computers

Earlier this month we covered the run of side effects that followed Microsoft’s November Patch Tuesday, including activation failures. Microsoft has now shipped the fix. According to BleepingComputer, out-of-band (emergency) updates released on Friday, November 13, fix the licensing errors for organizations that script Windows activation. The KB numbers below are taken from that report and Microsoft’s linked support articles.

The problem, in one paragraph

After installing November’s security updates, some devices returned error 0x80041008 (Invalid parameter, SWbemObjectEx) when administrators ran the Software Licensing Management Tool, slmgr.vbs, to set a KMS server or install a product key. That broke automated activation and licensing steps in imaging and deployment workflows. Microsoft said devices that were already activated stayed activated.

Spec sheet

  • Error seen: 0x80041008 when running activation, KMS configuration or product key commands with SLMGR.
  • Commands named: slmgr.vbs /skms-domain and slmgr.vbs /ipk.
  • Who was affected: organizations that use SLMGR to automate activation and licensing.
  • Who was not: devices already activated, and environments whose images already contain the correct KMS client key and KMS configuration and that do not need to run the affected commands.
  • Fix released: Friday, November 13, 2026, as out-of-band cumulative updates that also include the November security fixes.

Updates by version

  • Windows Server 2025: KB5136489
  • Windows Server 2022: KB5136487
  • Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5136490
  • Windows 11, version 23H2: KB5136483
  • Windows 10, version 22H2 (ESU) and Windows 10 Enterprise LTSC 2021: KB5136493

Where to get them

  • Windows Server 2025, 2022, 2019 and the Windows 10 packages: Microsoft Update Catalog only. They will not appear automatically in Windows Update.
  • Windows 11 23H2: Microsoft Update Catalog, or Windows Update under Settings > Windows Update > Advanced options > Optional updates.

Install checklist

  1. Confirm whether you are affected at all: do your deployment scripts, imaging task sequences or onboarding runbooks call SLMGR to set KMS or install keys? If not, and devices are activating normally, you can wait for the regular cycle.
  2. If you are affected, download the matching KB from the Microsoft Update Catalog and import it into whatever you use to approve updates. Catalog-only packages are easy to miss if you rely on automatic approval.
  3. Test on one machine per Windows version, re-run your activation script, and check that it completes without 0x80041008.
  4. Roll out to the rest, starting with build images and machines that are mid-deployment.
  5. Note the dependency: Microsoft says the out-of-band packages include the November security update, so installing one also brings in this month’s security fixes. Do not uninstall November’s security update to work around the bug.
  6. Keep an eye on the other November issues Microsoft has acknowledged, including printing problems and installation failures on some Windows 11 systems.

What this means for your company

Most small offices that buy PCs with built-in licenses will never notice this bug. It bites organizations that build and activate machines with scripts, which is exactly the process that matters when you are onboarding staff or rebuilding a server in a hurry. The broader lesson is about patch management: some fixes only exist in the Update Catalog, so a process that only watches automatic updates can miss them. Someone should own reading Microsoft’s known-issues notes every month and deciding which optional fixes apply to you.

If your team found out about this month’s Windows problems from users instead of a patch report, it may be time for a steadier update process. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author