IT Infrastructure

Windows November Update Issues: Activation Fixes Are Out, Printing Is Still Broken

A flat vector illustration in slate blue, mustard and off-white of a long curving line of dominoes on a wooden floor, where one domino in the middle has toppled sideways and stopped the chain, a visual for the Windows November update problems that halted some activation and printing tasks

Microsoft’s Windows November update from November 10, 2026 broke some activation and licensing tasks. Microsoft shipped out-of-band fixes on Friday, November 13. A printing problem with certain complex documents is still open, according to BleepingComputer. Microsoft also says it is working on a SQL Server problem tied to updates since October.

None of this means you should skip the November security update. It fixes flaws that attackers are using, including the Outlook zero-day we covered in Outlook Zero-Day Leaks NTLM Hashes. This post covers which problem hits whom and which out-of-band KB to install. It also shows how to check a machine and how to slow your rollout in Intune. It also covers the phishing that followed last week’s Microsoft 365 outage. Facts are as of November 16, 2026.

The short version: if you script activation with slmgr.vbs, install the out-of-band KB for your Windows version. Most of them come only from the Microsoft Update Catalog. If staff print Word documents with watermarks or hidden images, test printing now. Watch your SQL servers. And warn staff about fake Microsoft 365 "outage" emails.

What went wrong with the Windows November update

Four separate issues showed up after the Windows November update. They affect different people.

Issue Who is affected Status as of November 16
Activation fails with 0x80041008 Orgs that run SLMGR commands, mostly KMS and image builds Fixed by out-of-band updates on November 13
Printing fails for some complex documents Windows 10 and later, Windows Server 2016 and later Open, per BleepingComputer
SQL Server linked server connections stay open Servers on updates since October 13 Confirmed; fix promised
November update fails to install Some Windows 11 devices Listed as a known issue

The activation bug and who it hits

Microsoft’s Windows message center says "certain Windows licensing and activation operations using the Software Licensing Management Tool (SLMGR) might fail with error 0x80041008 (Invalid parameter)" after the Windows November update.

It says this "primarily affects organizations using slmgr.vbs commands or automated processes to configure Key Management Service (KMS) activation, install product keys, or manage Windows licensing" in its notice. Microsoft says the fix is for "a limited number of enterprise devices" that hit the bug.

The important line for most readers is this one: "Devices that are already activated remain activated" after the update. If your PCs were activated before November 10 and nothing re-runs SLMGR on them, you are likely fine.

Who should care:

  • Teams that build or reimage PCs with scripts that set a KMS host or install a product key.
  • MSPs whose onboarding scripts run SLMGR.
  • Anyone moving servers to KMS or changing product keys this month.

BleepingComputer reported that Microsoft first confirmed the issue in a service alert on Wednesday, November 11. It names slmgr.vbs /skms-domain and slmgr.vbs /ipk as commands that trigger it.

Which out-of-band KB to install

Microsoft released these out-of-band updates on November 13, per its message center. Each is cumulative and includes the November security fixes.

Windows version Out-of-band KB Where to get it
Windows Server 2025 KB5136489 Microsoft Update Catalog only
Windows Server 2022 KB5136487 Microsoft Update Catalog only
Windows Server 2019 and Windows 10 Enterprise LTSC 2019 KB5136490 Microsoft Update Catalog only
Windows 11, version 23H2 KB5136483 Catalog, or Optional updates in Windows Update
Windows 10, version 22H2 ESU and Windows 10 Enterprise LTSC 2021 KB5136493 See the KB article

Windows 11 versions 24H2, 25H2 and 26H2 are not on Microsoft’s list. If you are on those versions, there is no out-of-band activation update to install.

For Windows 11 23H2, the KB5136483 article gives OS Build 22631.7714. It shows up under Settings, Windows Update, Advanced options, Optional updates. Microsoft says it is "not currently aware of any issues with this update" so far. Devices need an update from July 8, 2025 or later already installed.

Note that 23H2 Enterprise and Education got their last regular update on November 10. Our post on Windows 11 23H2 end of servicing covers the upgrade.

Because most of these are Catalog-only, they will not reach machines on their own. If you need the fix, download it and push it with WSUS, Configuration Manager or your RMM tool.

How to check a machine after the Windows November update

Start with the build. Open Settings, Windows Update, Update history, and look for the November KB or the out-of-band KB. For Windows 11 23H2, the fixed build is 22631.7714.

Then test the thing that broke. Run your normal activation or KMS script on one test machine and confirm it finishes without 0x80041008. If it still fails, check that the out-of-band KB is actually installed on that machine. Approved in your tool is not the same thing.

If you run Windows Server 2016 anywhere, it is not on the out-of-band list. It also reaches end of extended support on January 13, 2027, per Microsoft’s message center. Our Windows Server 2016 end of support post covers your options.

Printing problems after the Windows November update

BleepingComputer reported on November 13 that Microsoft sent customers a service alert about printing. It quotes Microsoft: "printing might fail for documents containing images rendered with a height or width value of zero at the selected printing resolution" after the Windows November update.

Microsoft says these zero-size images show up in complex formatting. Examples are "invisible" watermark images, layout anchors, and document tools that insert empty image objects. BleepingComputer says the bug mainly hits Word documents printed through the Windows Graphics Device Interface (GDI). Other apps can fail too. It affects Windows 10 and later, and Windows Server 2016 and later.

As of November 16, we could not find this issue on Microsoft’s public release health pages. We checked Windows 11 and Windows Server 2025. BleepingComputer gives the alert ID as WI1549472, which suggests it is posted in the Microsoft 365 admin center. Check there under Windows release health.

Microsoft has not published a workaround in what we could read. Two things you can do now:

  • Test the documents your staff print most. Start with letterhead templates, forms with watermarks and mail-merge output.
  • Remove the empty images if a document fails. Based on Microsoft’s description, deleting a hidden watermark or empty image should let the file print. That is our reading, not Microsoft guidance.

Do not uninstall the Windows November update to fix printing problems. It carries security fixes for flaws in active use.

The SQL Server and install issues

Microsoft’s Windows 11 26H2 release health page lists a confirmed issue opened November 11. After updates from October 13 and later, "connections created by SQL Server linked server queries might remain open after the queries complete" on servers. Over time that "can slow or degrade server performance" as connections pile up. Microsoft names Oracle and PostgreSQL connections as affected.

Microsoft says a mitigation is available through Microsoft Support for business, and that it will release an out-of-band update "in the next few days" to fix it. Restarting the SQL service gives temporary relief but can interrupt active queries. If you run linked servers, watch connection counts this week.

The KB5132061 article for Windows 11 24H2, 25H2 and 26H2 also lists a known issue titled "November security update might fail to install on some devices" as well. BleepingComputer reports this hits devices that installed the October 2026 preview update.

One fix landed too. The same KB fixes error 87 when adding a printer published in Active Directory. The October update caused that one.

How to pause or slow the rollout in Intune

If you use Intune, Windows update rings are where you control timing. Microsoft’s page on managing update rings gives the path. Go to Devices, By platform, Windows, Manage updates, Windows updates, then the Update rings tab. Select a ring to see its policy actions: Delete, Pause, Resume, Extend and Uninstall.

A few practical steps for small teams:

  1. Keep a pilot ring. Put five or ten machines that print a lot in a ring that updates first. Add one server.
  2. Pause only where needed. If printing breaks for a group that cannot work around it, pause quality updates for that ring only. Resume once Microsoft ships a fix.
  3. Set a short deferral. Microsoft’s update ring settings reference allows a quality update deferral of 0 to 30 days. A few days gives your pilot ring time to find problems.

Plan around one gap. Microsoft says there will be no non-security preview update in the second half of December 2026. The January 2027 security update is the next regular one after December’s.

Microsoft rules out an attack in last week’s outage

Separately, Microsoft has said last week’s Microsoft 365 outage was not an attack. In a post on X on November 13, Microsoft said it was "a technical issue not related to cyber or AI / agents" and apologized. It traced the incident to an earlier network capacity upgrade that surfaced after a network change. SecurityWeek reported the statement on November 16. Our Microsoft 365 outage recovery post covers the cleanup.

Watch for fake Microsoft 365 outage emails

Microsoft Threat Intelligence warned of phishing that pretends to be Microsoft 365 service health notices. The emails cite the real incident ID, EX1550543. Some claim mail held during the outage "will be deleted within 24 hours unless recipients click to restore them" in the email.

What to look for, per Microsoft:

  • Subjects that follow the pattern "Outage – [six-character code]."
  • Sender names ending in "Outage Notification" or "Service Health."
  • Sending domains moments-notice[.]com, planetmaison[.]com and newbooker[.]com.

Microsoft says the activity "is consistent with credential phishing" so far. It later said Defender blocks the domains and quarantines the emails. Its advice is to check Safe Links policies, look into any clicks, and confirm any outage "directly through the Microsoft 365 admin center" rather than from an email. Tell staff that Microsoft does not delete held mail through a link in an email. Our phishing attacks explainer has more to share.

Frequently Asked Questions

Which Windows November update caused the activation errors?

The November 10, 2026 security updates. Microsoft says SLMGR activation and licensing operations can fail with error 0x80041008 afterward.

Will my PCs become unactivated?

No. Microsoft says devices that are already activated stay activated. The problem hits new activation, KMS setup and product key changes.

Which out-of-band KB do I need?

KB5136489 for Server 2025, KB5136487 for Server 2022, KB5136490 for Server 2019, KB5136483 for Windows 11 23H2 and KB5136493 for Windows 10 22H2 ESU and LTSC 2021.

Will Windows Update install the fix on its own?

Mostly no. The server and Windows 10 updates are in the Microsoft Update Catalog only. The Windows 11 23H2 one appears under Optional updates.

Are Windows 11 24H2, 25H2 and 26H2 affected by the activation bug?

They are not on Microsoft’s out-of-band list. Microsoft has not released an activation fix for those versions.

Is the printing problem fixed?

Not as of November 16, according to BleepingComputer. Microsoft has not published a fix date or a workaround in what we could read.

Should I uninstall the Windows November update?

No. It fixes security flaws that attackers are using. Install the out-of-band update if you need the activation fix, and test printing instead.

Was last week’s Microsoft 365 outage a cyberattack?

No. Microsoft said it was “a technical issue not related to cyber or AI / agents,” tied to an earlier network capacity upgrade.

How do I spot the fake outage emails?

Microsoft says the subjects start with “Outage -” and a six-character code, and the sender names end in “Outage Notification” or “Service Health.”

Digital Matters

IT Infrastructure Desk