Skip to content

November 2026 Windows Update Problems on Business PCs: Failed Printing, Broken Activation, and What Microsoft Has Fixed

Short answer

The November 10, 2026 Windows update caused 5 problems on business PCs: stuck installs, activation error 0x80041008, failed Word printing and slow SQL servers. Here is what Microsoft fixed and what you should do.

Origami Team

Editorial Team · · 6 min read

Share on WhatsApp
Like what we publish? Pin Origami as a preferred source on Google.Add as a preferred source on Google
November 2026 Windows Update Problems on Business PCs: Failed Printing, Broken Activation, and What Microsoft Has Fixed

The Windows update released on November 10, 2026 brought 5 problems that hit business PCs: installs that never finish, activation commands failing with error 0x80041008, Word documents that won't print, database connections piling up on servers, and signed PowerShell scripts that stop running. Microsoft has fixed two so far, and the rest have workarounds. Don't stop updating, because the update closes security holes, but test it first on a small group of PCs and find which problem applies to you in the list below.

This update does not cover Outlook: its exploited flaw is fixed by updating Office itself, which we explained in our article on the exploited Outlook flaw and how to update.

Which update reached your PCs?

On November 10, Microsoft released KB5132061 for Windows 11 versions 24H2, 25H2 and 26H2, and KB5131087 for version 23H2. Microsoft warns on the 23H2 update page that the Enterprise and Education editions of that version have reached end of updates, and that the November update is their last security update. If your company has 23H2 PCs on those editions, plan their upgrade now.

Microsoft also announced that there will be no non-security preview update in the second half of December 2026 because of the holidays, with the normal cycle returning in January 2027. So the next fix for this month's problems may come as an out-of-band update or with the December security update.

Problem one: the update won't finish installing

According to the KB5132061 update page, some devices may repeatedly retry the install or show error 0x80070306, 0x800f0989 or 0x800f0993, especially devices that installed the October preview update. The fix reaches internet-connected devices that update through Windows Update automatically, within 24 to 48 hours starting November 11.

  • If a PC is still stuck after 48 hours, contact Microsoft Support or follow the manual install instructions on the same page.
  • If your company manages updates through an internal server or a device management tool, make sure PCs can reach Windows Update to receive the repair.

Problem two: activation commands fail with error 0x80041008

This one hits companies that activate Windows through a KMS server or install product keys by command or automated script, such as slmgr.vbs. The reassuring part from Microsoft: devices that are already activated stay activated, and KMS devices typically remain activated for up to 180 days after their last successful activation. The device really affected is the new one you are setting up now.

On November 13, Microsoft released an out-of-band update that fixes it, according to the Windows message center:

  • Windows 11 version 23H2: KB5136483, which appears in Windows Update under optional updates.
  • Windows Server 2025: KB5136489.
  • Windows Server 2022: KB5136487.
  • Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5136490.
  • Windows 10 version 22H2 under ESU and Windows 10 Enterprise LTSC 2021: KB5136493.

These server and Windows 10 versions get the fix only from the Microsoft Update Catalog, so it will not appear on its own.

Problem three: Word documents won't print

BleepingComputer reported that Microsoft warned customers in the Microsoft 365 admin center (alert WI1549472) that printing may fail for documents containing images whose height or width becomes zero at the selected print resolution. These images are often invisible: a watermark, a layout anchor, or an object that document-generation software adds automatically. Word printing through the GDI interface is the most affected, and other apps may be too. Microsoft had not announced a fix date as of that report.

Why should you care? Because your invoices, contracts and quotes may come out of templates that contain a logo or watermark like that. If the accounting printer stops printing one specific document while printing others, a hidden object in the template is the likely cause. Review the template with whoever built it, and follow the alert's status on the release health dashboard in the Microsoft 365 admin center.

Problem four: database servers slow down over time

The Windows 11 25H2 release health page says that updates from October 13, 2026 onward leave SQL Server linked server connections to external databases, such as Oracle and PostgreSQL, open after the query finishes. Over time the connections pile up and the server slows down. This matters if your accounting system or ERP runs on a Windows server and reads from another database.

The temporary fix: close idle connections manually, or restart the SQL service, although that may interrupt running operations. The better move right now is to contact Microsoft Support for business, which offers a mitigation for affected devices. Microsoft has promised an out-of-band update within days.

Problem five: signed PowerShell scripts stop running

This update tightens encoding checks on signed scripts, so Windows may reject a script that used to run if its encoding is invalid. The fix, per the official page: save the script as UTF-8 with a byte order mark (BOM), then sign it again. This matters if your backup jobs or nightly reports run on signed scripts.

The Origami view

We see the real problem in most Saudi businesses not in the update itself, but in the fact that it lands on every PC on the same night with no testing. A company that first tries the update on 3 or 4 PCs representing its departments (accounting, printing, the server) catches the problem in one day before it reaches everyone.

We don't see stopping updates as the answer: the November update itself closes security holes, and an unpatched PC is more dangerous than a stalled printer. Better to keep a simple record: which version is on each PC, who watches the release health page, and who decides when to roll the update out.

Bottom line: what to do this week

  • Know the Windows version on your PCs, and plan to upgrade any 23H2 machine on Enterprise or Education.
  • If PCs have been stuck installing for more than 48 hours, check their connection to Windows Update.
  • If you are setting up new PCs with KMS activation, install the out-of-band update for your version first.
  • Test-print an invoice and a contract from your real templates after updating.
  • If you run a SQL server linked to external databases, watch the number of open connections until the fix ships.

If you need someone to organise your update management or review your systems before a rollout, get in touch.

  • #Windows Update
  • #Windows 11
  • #Printing Problems
  • #Business IT Management

Frequently asked questions

Should I stop Windows updates in my company until these problems are solved?

No. The November update closes security holes, and an unpatched PC is more dangerous. Better to test it first on a few PCs that represent your departments, then roll it out after a day or two.

I got error 0x80041008. Has my PC lost its activation?

No. According to Microsoft, devices already activated stay activated, and KMS devices typically stay activated for up to 180 days. The problem is in new activation commands, and the fix is the November 13 out-of-band update for your version.

Why do some documents print and others don't after the update?

According to BleepingComputer's report of Microsoft's alert, printing fails for documents with an image whose height or width is zero at the print resolution, such as a watermark or a hidden object in the template. Documents without one usually print.

My PC is stuck installing the November update. What do I do?

Microsoft is sending an automatic repair to devices connected to Windows Update within 24 to 48 hours starting November 11. If it is still stuck after that, contact Microsoft Support or install it manually following the update page instructions.

Have a project in mind?

We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.

See our services

Newsletter

New articles and series, in your inbox.

Follow Origami in Google

Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Add as a preferred source on Google