
On Tuesday, November 10, Microsoft shipped the biggest Patch Tuesday of the year: 1,094 CVEs, including one Outlook zero-day attackers were already using. By Thursday, the patch itself was the incident. The licensing tool admins use to activate Windows was failing, the update itself would not install on some machines, and printers were choking on ordinary documents.
The patch was necessary. It was also broken in a few small, specific ways, and each one has a different fix. That is the part worth sitting with: Patch Tuesday does not end when the install finishes. The known-issues page is part of the patch, and it keeps changing for days after release. Microsoft added both of the issues below on November 11, a day after the release. If your rollout plan stops at "deployed," you are flying blind for the rest of the week.
What broke, and where
| Problem | Error | Affected | Microsoft's position |
|---|---|---|---|
slmgr.vbs activation commands fail |
0x80041008, "Invalid parameter (SWbemObjectEx)" | Windows 10 21H2/22H2, Windows 11 23H2, Windows Server 2019/2022/2025 | Known issue added Nov 11; fix "in the coming days"; contact Microsoft Support for an immediate mitigation |
| KB5132061 fails to install | 0x80070306, 0x800f0989, 0x800f0993 | Windows 11 26H2/25H2, 24H2 Enterprise and Education | Automatic repair through Windows Update, within 24–48 hours from Nov 11, 10am PT |
| Printing fails on documents with zero-size images | None given | Windows 10, Windows 11, Windows Server | Acknowledged (service alert WI1549472); no fix timeline |
| SQL Server linked-server connections fail | None given | Systems on updates from Oct 13, 2026 onward | Confirmed on Windows release health, Nov 11 |
The slmgr failure is the one that matters most
The Software Licensing Management Tool is the script behind volume activation. After the November update, two of its commands fail: slmgr.vbs /skms-domain to set the KMS host, and slmgr.vbs /ipk to install a product key. Both return 0x80041008. Microsoft lists the issue on five KB pages: KB5131087, KB5131096, KB5131080, KB5131090 and KB5131085.
Who is hit: anyone who automates activation. Imaging pipelines, deployment scripts, and new-machine builds that run those commands as part of setup. Who is not hit: machines that are already activated. Microsoft is explicit that devices that are already activated remain activated, and KMS activations typically last up to 180 days. If your images already carry the correct KMS client key and configuration, and you do not re-run those commands, nothing changes for you.
I wrote in September that slmgr.vbs has an expiry date and the first step was an inventory, not a rewrite. The inventory advice still stands. But this week the tool itself is the fault, not your scripts, and there is one thing worth knowing before you start troubleshooting: the failure is deterministic, not flaky. Re-running the command will not help. Do not wrap it in a retry loop and do not rebuild an image around it. The fix is Microsoft's, and it is coming in days, not hours.
The KB5132061 install failure fixes itself, mostly
On Windows 11 26H2, 25H2 and 24H2 Enterprise and Education, the November update itself can fail to install, retrying over and over or showing error 0x80070306, 0x800f0989 or 0x800f0993. The reports so far tie the failures to machines that had the October preview update installed. Microsoft's resolution is hands-off: a repair rolls out automatically to affected devices that are connected to the internet and use Windows Update in Settings, with all affected devices repaired within 24 to 48 hours from November 11, 10am PT. That window ran through November 13.
If a machine still fails after that, install the package manually from the Microsoft Update Catalog rather than forcing Windows Update to retry in a loop. And if the machine is managed through WSUS or Intune, remember the automatic repair comes through Windows Update in Settings. A device that never talks to Windows Update directly will not get it.
What to do this week
- Grep your deployment and imaging scripts for
slmgr.vbs /ipkandslmgr.vbs /skms-domain. Pause those steps on machines with the November update until Microsoft ships the fix. Where you can, bake the correct KMS client key and configuration into the image so the commands never need to run. - Check activation state before changing anything. A read-only check that does not touch licensing:
Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select-Object Name, LicenseStatus
LicenseStatus 1 means licensed. Do not "fix" a machine that is already activated. There is nothing to fix. 3. For KB5132061 install failures, wait out the automatic repair window first. It ran through November 13. If a machine still fails, install the package manually from the Microsoft Update Catalog. 4. Do not roll back the November update to fix activation. The same release carries fixes for 1,094 flaws, and the exploited Outlook bug, CVE-2026-124194, is patched through the separate Office update, not the Windows package. Rolling back trades a licensing annoyance for real exposure. 5. If print jobs are failing, check whether the documents contain images with zero height or width, and hold those jobs until Microsoft publishes a fix. Watch the Windows release health dashboard rather than re-testing the same document. 6. If you run SQL Server linked servers, test them before widening the rollout. Release health lists the issue as confirmed, covering updates from October 13 onward. 7. Test your signed PowerShell scripts. The November packages enforce stricter UTF-8 signature validation, and scripts with invalid UTF-8 can fail validation. Microsoft's guidance is to save as UTF-8 with BOM and re-sign. 8. Do not let the activation noise hide the lifecycle deadline. November was the last update for Windows 11 23H2 Enterprise and Education. Plan the move to a supported version.
The part worth remembering
A patch that fixes 1,094 flaws can still break the tool you use to license the machine it runs on. That is not a reason to skip patching. The exploited Outlook flaw in the same release is the reason you patch. It is a reason to treat the known-issues page as part of the deployment: check it on day one, day two and day three, because that is when it changes. Your pilot ring catches what breaks on install. The known-issues page catches what breaks after.
One planning note for the calendar: Microsoft says there will be no December non-security preview update, with normal servicing resuming in January 2027. December 8 is the last Patch Tuesday of the year, and the next preview will not arrive until after the holidays. Get the November fallout cleaned up now, while the calendar is still on your side.
Sources
- Microsoft Confirms November 2026 Windows Updates Are Causing Activation and Licensing Errors — PBXScience, November 13, 2026
- KB5132061, KB5131087: November 2026 Patch Tuesday — AdminSignal, updated November 12, 2026
- Windows 11 KB5132061 Fails To Install: Fix Errors 0x800f0989, 0x80070306, 0x800f0993 — BD Tech Support, November 13, 2026
- November 2026 Patch Tuesday: Outlook Zero-Day, KBs, Builds — OSBBD, November 12, 2026
- November Patch Tuesday boasts over 1,000 bugs, one already under attack — The Register, November 10, 2026



