Microsoft has released five out-of-band updates to fix Windows activation error 0x80041008, which its November 2026 security update introduced. The packages shipped on 13 November 2026 for Windows 11 23H2, Windows 10 22H2 ESU and three Windows Server releases. A second fault from the same update, which stops some documents printing, is still unfixed.

What Fails and Which Commands Trigger It

The bug breaks scripted activation, not activation itself. Microsoft’s known-issue entry says that after installing the November 2026 security update, some licensing operations run through the Software Licensing Management Tool fail with error 0x80041008, “Invalid parameter (SWbemObjectEx)”. The tool, known as SLMGR, runs as the script slmgr.vbs and is how administrators configure licensing from a command line.

Microsoft names two commands as examples:

  • slmgr.vbs /skms-domain: Points a device at a Key Management Service domain for volume activation.
  • slmgr.vbs /ipk: Installs a product key on the device.

Key Management Service, or KMS, is the server that large organisations run to activate Windows across many machines at once rather than entering a key on each one. Devices being configured for KMS activation may fail when they try to start activating.

Most people will never see this. Microsoft is explicit that “devices that are already activated remain activated,” and that customers whose machines already carry the right KMS client key and configuration, and who do not need to run the affected commands, are not expected to be affected. Images that ship with the KMS client key built in and do not call SLMGR afterwards are also clear. BleepingComputer reported that KMS-activated devices typically stay activated for up to 180 days after a successful activation, which gives administrators room before a re-activation cycle comes round.

Microsoft tracks the problem as service alert WI1549486.

Which Versions Are Affected and Which Have a Fix

The two November faults hit different and only partly overlapping sets of Windows releases, and only the activation one has a fix.

Windows versionActivation error 0x80041008Printing failureOut-of-band fix
Windows 11 26H2, 25H2 and 24H2Not affectedAffectedNone issued
Windows 11 23H2AffectedAffectedKB5136483
Windows 10 22H2 ESU and Enterprise LTSC 2021AffectedAffectedKB5136493
Windows 10 Enterprise LTSC 2019 and Windows Server 2019AffectedAffectedKB5136490
Windows Server 2022AffectedAffectedKB5136487
Windows Server 2025AffectedAffectedKB5136489
Windows 10 Enterprise LTSC 2016 and Windows Server 2016Not affectedAffectedNone issued

The absence of Windows 11 24H2, 25H2 and 26H2 from the activation list is not an oversight. Microsoft’s support page for KB5132061, the November security update for those three releases, lists no activation or licensing known issue at all. Its one known issue is different: the November security update might fail to install on Windows 11 24H2 Enterprise and Education devices, which may retry repeatedly or report error 0x80070306, 0x800f0989 or 0x800f0993. Microsoft said a repair would run automatically through Windows Update on connected devices within 24 to 48 hours from 11 November 2026 at 10am Pacific Time, with no user action needed.

How to Get the Out-of-Band Update

These packages are optional and non-security, and they do not arrive the way a Patch Tuesday update does. The route differs by product.

  1. Windows 11 23H2: KB5136483 appears under Settings, then Windows Update, then Advanced options, then Optional updates. It is also in the Microsoft Update Catalog.
  2. Windows Server and Windows 10 builds: Microsoft says the four server and Windows 10 packages are available only from the Microsoft Update Catalog, where an administrator downloads the standalone package and deploys it.
  3. Windows Update for Business: Not a route. Microsoft’s page for KB5136483 marks it unavailable there and says the changes will arrive in the next security update instead.
  4. WSUS: Not a direct route either. The update has to be imported manually from the Microsoft Update Catalog.

Two prerequisites apply before KB5136483 will install: a Windows update released on or after 8 July 2025, such as KB5062552, and the latest servicing stack update. The out-of-band package is cumulative and includes the November 2026 security update it corrects, so it replaces rather than supplements that update.

Administrators who can wait have a reasonable case for doing so. Microsoft’s own framing is that the problem affects “a limited number of enterprise devices,” and the fix is folded into the next scheduled security update, which removes the manual deployment work entirely.

The Printing Bug From the Same Update Has No Fix

The second fault is broader in reach and, as of today, unresolved. After the November 2026 security update, printing can fail when a document contains an image whose height or width renders as zero at the chosen print resolution.

Microsoft said the issue “was observed when printing Microsoft Word documents using the Windows Graphics Device Interface (GDI),” and that “printing from other applications might also be affected.” The Graphics Device Interface is the older Windows component that many desktop applications still use to draw and print pages.

The trigger is not a printer, a driver or a queue. It is an invisible object inside the file. Zero-size images commonly arrive in documents as watermark remnants, layout anchors, or artefacts left by software that generates documents automatically, which means the person printing has usually never seen the object and has no reason to suspect it. One malformed image can stop the whole job.

Reporting by The Register, which first published Microsoft’s notice WI1549472, puts the reach across most supported releases, from Windows 11 26H2 back to Windows 10 Enterprise LTSC 2016, and across Windows Server 2016 to 2025. Microsoft has published no workaround, has not advised uninstalling the update, and has not given a date for a fix. The Register reported that affected customers were being directed to Microsoft Support for Business.

Readers who follow this cycle will recognise the shape of it. The security content of the same release is covered in our report on Patch Tuesday November 2026, and an update breaking licensing is not new ground either — KB5002907 deactivated Office 2016 and 2019 installations in September 2026 before Microsoft paused it.

Where Things Stand as of 16 November 2026

As of 16 November 2026, the activation error is resolved and the printing failure is not. Microsoft’s KB5131087 page marks the licensing issue fixed in updates released on or after 13 November 2026, and the five out-of-band packages carry that fix. No resolving update has been published for the printing issue, and Microsoft’s notice still describes it as under investigation.

Two things could change before the next working day. Microsoft has not said whether the printing fix will wait for December’s Patch Tuesday or ship as its own out-of-band package, and the automatic repair for the failed installations on Windows 11 24H2 Enterprise and Education devices was due to complete within 48 hours of 11 November, which has now passed without a published completion notice. Organisations still buying extended support for Windows 10 should note that the 22H2 ESU channel is among those that needed the fix; the cost of staying on that channel is set out in our guide to Windows 10 ESU year two pricing.

Frequently Asked Questions

Will My PC Deactivate Because of This Bug?

No. Microsoft states that devices already activated remain activated, and no re-activation is required. The fault appears only when licensing commands are run through SLMGR, which is an administrator task rather than something a home user does.

Is Windows 11 24H2 or 25H2 Affected by Windows Activation Error 0x80041008?

No. Microsoft’s support page for KB5132061, which covers Windows 11 24H2, 25H2 and 26H2, lists no activation or licensing known issue, and those releases are absent from the out-of-band fix list.

Why Will the Fix Not Appear in WSUS or Windows Update for Business?

Because Microsoft shipped it as an optional, non-security out-of-band package. Those are not distributed through Windows Update for Business, and WSUS requires an administrator to import the package manually from the Microsoft Update Catalog.

Can I Stop Documents Failing to Print Before Microsoft Fixes It?

Microsoft has published no workaround and has not recommended uninstalling the update. It has directed affected business customers to Microsoft Support for Business, so there is no sanctioned self-service fix at present.

Do I Need to Install the Out-of-Band Update Immediately?

Only if your organisation runs scripted or automated activation and is hitting the error. Microsoft describes the impact as limited to a small number of enterprise devices, and the same fix is due to arrive in the next scheduled security update without manual deployment.