A print job that dies without a clear reason after the Nov. 10 Windows patches may have a specific trigger sitting inside the document: an image. Microsoft has told administrators that the November 2026 security updates can stop a document from printing when it contains a picture whose height or width works out to zero at the chosen print resolution.
Read next on Morning Overview: A handful of car transmissions are so tough that mechanics say they almost never die
Microsoft’s notification carries the tracking ID WI1549472 and says printing “might fail” after the November 2026 security update or any later one. The company confirmed the failure with Word documents printed through GDI, the long-standing Windows graphics layer, and says other applications might also be affected. As of Nov. 13, no fix and no official workaround had been published.
Zero-height images and the GDI print path
The wording in WindowsForum’s account of the notice is narrow. The trigger is an image with zero height or zero width at the selected print resolution, the kind of near-invisible object that can hide in a template, a letterhead or a document pasted together from several sources. A page with no such image should print as before, which is why the reports so far describe a failure that hits some users rather than everyone running the patch.
Microsoft has not said how many devices are affected, and it has not told customers to remove the update. Its guidance, as relayed by The Backroom Tech, is that affected customers should contact Microsoft Support for Business for workarounds. That site also notes The Register reported the problem on Nov. 12 and that Microsoft had given no fix date or KB number at that point.
BleepingComputer’s report on the acknowledgment, published Nov. 13, was the first mainstream write-up to carry the news to a general audience.
Which November updates carry the problem
The notice spans nearly every supported Windows branch, because the bug follows the November cumulative update rather than one product. For Windows 11 versions 26H2, 25H2 and 24H2 the originating update is KB5132061, released Nov. 10. Windows 11 26H1 uses KB5132059, and Windows 11 23H2 uses KB5131087. On Windows 10 versions 22H2 and 21H2 the update is KB5131096.
The server and long-term-servicing lines are covered as well. Windows 10 Enterprise LTSC 2019 and Windows Server 2019 receive KB5131085, while LTSC 2016 and Windows Server 2016 receive KB5131291. Windows Server 2025 uses KB5131080, and Windows Server 2022 uses KB5131090. Devices on the 2016 branch only receive that patch with Extended Security Updates, because mainstream support for that release ended on Oct. 13.
Microsoft’s own page for KB5132061 lists no image-printing problem among its known issues. It records a different problem, an installation failure that can show error codes 0x80070306, 0x800f0989 or 0x800f0993, with an automatic repair promised within 24 to 48 hours of Nov. 11 for internet-connected devices. Because the printing notice sits in Microsoft’s separate message system, administrators looking only at the KB page can miss it.
The reach of the problem depends on how often documents carry stray images. Word files built from older templates, scanned letterheads and content pasted from web pages are the likeliest places for an image object to end up with a collapsed dimension. Microsoft has published no count of affected documents, so the size of the affected group is unknown.
Two printing bugs, one fixed and one open
The zero-dimension bug is not the only printing item in this month’s notes. The same KB5132061 page describes an October 2026 regression in which adding a printer published in Active Directory through Settings could fail with error 87, “The parameter is incorrect.” Microsoft lists that one as fixed in the November update, and says it does not generally affect existing printers or printing. The Backroom Tech traces the same fix to the Improvements section of KB5131085.
That split matters for triage. A user who cannot add a shared printer is dealing with the repaired Active Directory defect and should already have the correction. A user whose existing printer works for most files but rejects one particular Word document is describing the open image bug, and installing more patches is unlikely to help until Microsoft ships something for it.
What administrators can check while Microsoft investigates
Microsoft says it is still investigating. Until it does more, the practical test is to open the failing document, find any image sized at or near zero, and remove or resize it. That step is general troubleshooting, not Microsoft guidance, and WindowsForum labels its triage suggestions as such.
Status updates are posted to Microsoft’s Windows message center, the page The Backroom Tech points readers to for the current state of the notice. The open questions are the ones Microsoft has not answered: which update will carry the correction, whether it arrives as an out-of-band release or with the December patches, and how many documents in ordinary business use contain such an image.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- The Justice Department asked courts to undo approvals for three offshore wind farms, one already making power
- Over 20 trillion gallons of rain fell on the Four Corners states and Nevada in two weeks
- 11 engines built to run well past 200,000 miles
- Two Kentucky residents died when a small plane crashed at Missouri’s Lake of the Ozarks, and the NTSB is investigating