Quick fix: 5 steps
- Print the Windows test page. If it fails, this is a normal printer problem: use the checklist.
- Test a plain one-line Word document. If it prints, the issue is document specific.
- Save the failing document as PDF and print the PDF from Edge or Acrobat Reader.
- Still stuck: open Home, Select, Selection Pane in Word and remove hidden images or watermarks. Full steps.
- Uninstalling the update is a last resort because it removes security fixes. Read the tradeoff.
Can't print after the November 2026 Windows update: what Microsoft has confirmed
If you cannot print after the November 2026 Windows update, especially from Microsoft Word, you may be hitting a known printing problem that Microsoft has acknowledged. According to BleepingComputer, which reported on it on November 13, 2026, Microsoft published a Windows release health service alert numbered WI1549472 saying that "printing might fail for documents containing images rendered with a height or width value of zero." In plain language: a document can contain an image you never see, and that invisible image can stop the whole print job.
This guide explains who is affected, how to tell this bug from an ordinary printer problem, which workarounds are safe, and what to do if nothing helps. The first half is about this specific bug. The second half is a complete "printer stopped printing after a Windows update" checklist that stays useful long after this bug is fixed.
What we know and what is not confirmed yet (as of November 18, 2026)
Reported by the sources we opened:
- Microsoft's service alert is WI1549472. Per BleepingComputer (published November 13, 2026), it says printing might fail after installing the November 2026 Windows security update or later updates, for documents containing images rendered with a height or width of zero at the selected print resolution.
- Such images can be invisible: watermarks, layout anchors, spacers, or objects inserted by document-generation tools. The problem mainly affects Microsoft Word printing through the Windows Graphics Device Interface (GDI), but other applications may also be affected (BleepingComputer).
- BleepingComputer lists the affected systems as Windows 10 or later client devices and Windows Server 2016 or later.
- The November 2026 cumulative update for Windows 11 24H2, 25H2 and 26H2 is KB5132061, released November 10, 2026 (Microsoft Support). On Windows 10 22H2, Microsoft's release health page names KB5131096 as the November update.
Not confirmed or still changing:
- A fix. We found no fix and no release date in any source we opened. We found no official workaround either.
- Public documentation. When we opened Microsoft's public Windows release health pages for Windows 11 24H2 and Windows 10 22H2 on November 18, 2026, the printing alert was not listed there. Their Known issues tables showed other items (SQL Server linked server connections, USB audio, Remote Desktop). The KB5132061 support page lists only the SQL Server issue and an installation issue. The alert appears to live in the Microsoft 365 admin center service health view, so home users may not see it on the public pages.
- Exact scope. The error message, the precise list of originating KB numbers and which printers or drivers are affected are not given in the coverage we read. We will not guess.
Everything in the workaround sections below is practical troubleshooting, not an official Microsoft fix. We say so each time.
The short version in five points
- The bug is about documents, not about your printer hardware. A different document, such as a plain text page, usually still prints.
- Word is the most reported case, because Word documents commonly contain hidden watermarks, anchors and spacer images.
- The cheapest test is to save the document as a PDF and print the PDF from a PDF reader. PDF printing takes a different path from Word's GDI printing in many setups, though we cannot promise it works for everyone.
- Uninstalling the update is a last resort. It removes the security fixes of the November 2026 update, and you would need to hide or pause it afterwards.
- Watch Microsoft's release health page and Windows Update. If a fix ships, it will most likely arrive as a normal or out-of-band update.
Why an invisible image can stop a print job
When you print from Word, Windows often converts the page into drawing commands for the printer using GDI. Every image on the page is scaled to the printer's resolution. If an image is extremely small, for example a one-pixel-wide divider, a layout anchor or a transparent watermark placeholder, the scaled size can round down to zero in height or width. According to Microsoft's alert as reported, that zero-size result is what makes printing fail after the November 2026 updates.
A secondary report we read described narrow spacer or divider images as the most likely trigger, since a low print resolution can leave them at zero pixels wide. We treat that as plausible but not confirmed by Microsoft. It matches Microsoft's wording, which is why we mention it.
The practical consequence is useful: whether a document prints can depend on the print resolution and on what hidden objects the document contains. Two documents that look identical can behave differently, and the same document can behave differently on two printers.
How to tell if it is this bug or a normal printer problem
Printer trouble after a Windows update has many causes: a stalled print spooler, a driver that was replaced, a printer that changed IP address, or a network setting. Before you apply any workaround for the zero-size image issue, run this short sorting test. It takes about ten minutes.
| Test | Result that points to this bug | Result that points to something else |
|---|---|---|
| Print the Windows test page (Printer properties, Print Test Page) | Prints fine | Fails: driver, spooler, connection or printer problem |
| Print a new blank Word document with one line of text | Prints fine | Fails: not document specific |
| Print the failing document | Fails, or the job disappears or errors out | Prints: the earlier failure was a one-time glitch |
| Print the same failing document to Microsoft Print to PDF | Often still fails or behaves oddly, because the same engine draws the page | Works: the page content is not the problem, look at the printer path |
| Print the PDF you saved from that document, using a PDF reader | Prints fine | Fails: the printer or driver is the issue |
| Print the same document from a second computer that has not installed the November update | Prints fine | Fails the same way: the document itself or the printer is the cause |
The strongest signal is a pattern: the printer works for everything except certain documents, and the trouble started right after the November 2026 update. If the printer fails for everything, jump to the general checklist.
One honest caution about the Microsoft Print to PDF row: we did not find a source that tests that specific path against this bug, so treat our "often still fails" note as an expectation, not a fact. Its value is as a diagnostic, not as a fix.
Which Windows versions and updates are affected
Here is what we could verify and what we could not, so you can check your own PC.
| Windows version | November 2026 update (per Microsoft or press) | Status of verification |
|---|---|---|
| Windows 11 26H2, 25H2, 24H2 | KB5132061, released November 10, 2026. Builds 26300.9974 (26H2), 26200.9974 (25H2), 26100.9974 (24H2) | Confirmed on the Microsoft Support page we opened |
| Windows 11 23H2 | KB5131087 reported in press snippets | Not verified on a Microsoft page, treat as unconfirmed |
| Windows 11 26H1 | KB5132059 reported in press snippets | Not verified on a Microsoft page, treat as unconfirmed |
| Windows 10 22H2 | KB5131096 | Named on Microsoft's Windows 10 22H2 release health page. Windows 10 reached end of support on October 14, 2025, so only devices enrolled in Extended Security Updates receive it |
| Windows Server 2016 and later | Not listed by KB in sources we opened | Alert says Server 2016 or later is affected, per BleepingComputer |
Microsoft's alert, as reported, applies to the November 2026 security update "or later updates". That means that if you installed a December update in the future before a fix is shipped, the bug could still be present. Check the release health page again after each update.
How to check which update you have installed
- Press the Windows key, type winver, and press Enter. Note the version and the OS build (for example 26100.9974).
- Open Settings, Windows Update, Update history. Look under Quality Updates for the November 2026 entry and note its KB number.
- If your build number is lower than the one in the table above for your version, the November update is not installed on that PC and this bug is not your cause.

Home users on Windows 11 usually receive KB5132061 automatically. If you postponed updates, you may be unaffected for now, but you also lack the security fixes in that update, so do not stay on an old build just to avoid a printing bug unless you have to.
Safe workarounds while Microsoft has not published a fix
As of November 18, 2026, we found no official workaround for alert WI1549472. The steps below are common-sense troubleshooting based on how Microsoft describes the trigger. They are not endorsed by Microsoft, and results will vary. They are ordered from least invasive to most invasive, and none of them removes security protection.
Workaround 1: save as PDF, then print the PDF
This is the fastest test and a workaround suggested in reader comments on BleepingComputer's report of this bug. It does not change your system.
- In Word, open File, Save As (or Export, Create PDF/XPS Document) and choose PDF as the type.
- If Word itself fails or crashes when exporting, try File, Print, Microsoft Print to PDF instead, and see whether that completes.
- Open the PDF in Edge, Adobe Acrobat Reader or another PDF reader, and print from there.
Why it might help: once the page is a PDF, the PDF reader renders it by its own method, and Word's drawing of the hidden zero-size image is no longer part of the print job. Why it might not: a PDF reader can still send content through Windows printing components, and we have no Microsoft statement that this route is immune. If the PDF prints, you have your answer. If it fails the same way, move on.
Workaround 2: find and remove the hidden zero-size objects
If you must keep printing directly from Word, remove what Microsoft says triggers the failure.
- Open the Selection Pane. In Word, go to Home, Select, Selection Pane (or Layout, Selection Pane in some builds). It lists every floating object on the page, including hidden ones. Look for images, shapes and text boxes you do not recognize.
- Check headers and footers. Double-click the top or bottom margin to open the header. Watermarks and logos often live there. In Word, Design, Watermark, Remove Watermark deletes a standard watermark.
- Turn on formatting marks. Press Ctrl+Shift+8 to show paragraph marks and anchors. A tiny image sitting in an empty paragraph is a likely suspect.
- Replace tiny spacer or divider pictures with a paragraph border (Home, Borders) or table spacing. Real-world templates that use one-pixel images as lines are common.
- Try again, printing one page at a time to find which page causes the failure.
For documents produced by another system (invoice generators, reporting tools, web-to-Word exports), the zero-size images may be inserted automatically each time. In that case fix the template once, or generate PDFs instead of Word files if the tool allows it.
Workaround 3: change the print quality or resolution
Microsoft's wording ties the failure to the "selected print resolution". That suggests an image can be zero-sized at one resolution and non-zero at another. So changing the printer's resolution is a cheap experiment, with the caveat that we found no source confirming it works.
- In Word choose File, Print, Printer Properties (or open Settings, Bluetooth and devices, Printers and scanners, pick the printer, then Printing preferences).
- Look for Quality, Resolution or Print quality. Move from Draft or 300 dpi to 600 dpi, or the reverse.
- Print the failing page again.
If it works, note the setting so you can restore it when a fix arrives. Higher resolution uses more ink and takes longer, so do not leave it on for everything without a reason.
Workaround 4: print from a different application or a different printer path
- Open the file in another program. Word documents can be opened in LibreOffice or in Word for the web, then printed from there. Layout can shift slightly, so check the preview. We did not find a source that tests this route against the bug.
- Use a different printer or driver. If you have another printer, or the printer offers more than one driver (for example a PCL and a PostScript version), try the other. Because the issue is described as a Windows GDI problem, a different driver may or may not help. Test before you rely on it.
- Print from another computer. Send the file to a colleague whose PC has not installed the November update yet. This is a one-off bridge for urgent documents only. It is not a reason to postpone security updates for long.

Last resort: uninstalling the November update, and the security tradeoff
Because the zero-size image failure started with the November 2026 security update, uninstalling it would be expected to remove the cause. We have not found a source that confirms that outcome for this specific alert, so even this step is not guaranteed. More importantly, it has a real cost.
Understand the tradeoff first
The November 2026 update contains security fixes. According to Microsoft's KB5132061 page, it includes security improvements listed in the Security Update Guide for November 2026, among other changes. Removing it takes those protections away until you install a later update. That matters most for business PCs, computers that browse the web and open email attachments, and any PC exposed on a network. Try workarounds 1 to 4 first, and keep uninstalled time as short as possible.
How to uninstall the update on Windows 11 (the standard method)
- Open Settings, Windows Update, Update history.
- Scroll to Uninstall updates under Related settings and select it.
- Find the November 2026 entry (for example KB5132061 on Windows 11 24H2, 25H2 or 26H2) and select Uninstall, then confirm and restart.
- Pause updates (Settings, Windows Update, Pause updates) so Windows does not reinstall it immediately.
On Windows 10 with Extended Security Updates, the same screen is reached through Settings, Update and Security, View update history, Uninstall updates. If the uninstall option is missing or greyed out, the update may be bundled with a servicing stack update that cannot be removed, which is a common situation on newer Windows 11 builds. Do not try random scripts from forums in that case. See our guide on Windows Update stuck or failing if Windows misbehaves during the process.
After you uninstall: write down the date, set a reminder to check Microsoft's release health page weekly, and install the next cumulative update when Microsoft says printing is fixed. Do not leave a PC on an old update for months.
If Windows will not start after an update change, use our Windows won't boot after update guide. Before any uninstall on a PC with important files, make a backup first. Our page on data recovery after a Windows update explains what can go wrong.
Other November 2026 Windows issues you might confuse with this one
Several problems were reported in the same weeks. If your symptoms differ from the printing alert, one of these may be the real cause. We list only what we could verify. For the full list see our Windows 11 November 2026 Patch Tuesday known issues and fixes guide.
| Issue | What it looks like | Source and status as of November 18, 2026 |
|---|---|---|
| Installation failures on Windows 11 24H2 Enterprise and Education | Update repeats or fails with 0x80070306, 0x800f0989 or 0x800f0993 | KB5132061 support page lists it; the change log says an automatic repair was applied on November 16, 2026, but the entry still appears under known issues |
| Activation and licensing failures | Error 0x80041008 during activation | Reported by BleepingComputer in connection with the November updates; we did not find a Microsoft workaround to quote |
| SQL Server linked server connections stay open | Server slowdown over time | Listed on Microsoft's release health page as Confirmed, affects servers, mitigation through Microsoft Support for business |
| Printing from Active Directory-published printers fails with error 87 | Add-printer in Settings fails | Per the KB5132061 page, this earlier October bug is fixed by the November update |
That last row matters: some printer problems in October were different bugs, and the November update fixed at least one of them. If your problem is "cannot add a network printer" rather than "documents fail to print", read the cannot connect to printer guide instead.
Printer not printing after any Windows update: the full checklist
If the sorting test showed that your printer fails for every document, or if the failure has nothing to do with Word, work through this list in order. It applies to any Windows update, now or in the future. For a deeper dive on a particular symptom, our main printer not working fix guide covers more cases.
1. Check the basics (two minutes)
- Power the printer off, wait 30 seconds, power it on. Restart the PC too.
- Look at the printer's own screen for paper, ink, cover or error messages.
- Confirm the printer is the default: Settings, Bluetooth and devices, Printers and scanners. Make sure it is not set to "Use Offline".
- Open the print queue and cancel stuck jobs. A single bad job can block everything behind it.
2. Restart the Print Spooler and clear the queue
- Press Windows key + R, type services.msc, press Enter.
- Find Print Spooler, right-click, choose Stop.
- Open File Explorer and go to
C:\Windows\System32\spool\PRINTERS. Delete the files inside (not the folder). - Return to Services, right-click Print Spooler, choose Start. Confirm Startup type is Automatic.
If the spooler keeps stopping, see our printer spooler error page.
3. Fix "printer offline" and network printers
After an update, a network printer can change IP address or lose its port. Print the printer's network configuration page and compare its IP with the port used in Windows (Printer properties, Ports). If they differ, edit the port or reserve a fixed IP in your router. Our printer offline page gives the steps. Wi-Fi printers that lost their connection after an update may need to be rejoined to the network from the printer's panel.
4. Update, reinstall or roll back the driver
- Download the current driver from the printer manufacturer's support site. Use the model number on the printer label, not a driver site found through search ads.
- In Settings, Printers and scanners, remove the printer. Open Print server properties (under Related settings) and, on the Drivers tab, remove the old driver package.
- Install the new driver, restart, and add the printer again.
Our how to update drivers guide covers the safe way to do it. If a driver update itself caused the break, Device Manager offers Roll Back Driver on the driver's Properties page for devices where it was updated recently.
5. Use the built-in printer troubleshooter
In Windows 11: Settings, System, Troubleshoot, Other troubleshooters, Printer, Run. It resets the spooler, checks the driver and can fix simple port problems. It is not a magic wand, but it costs nothing and sometimes saves an hour.
6. Check for specific error codes
- 0x00000709 when connecting to a shared printer: see error 0x00000709.
- PCL XL error: see PCL XL error. This one is also tied to a document with something the printer cannot render, so it can look similar to the zero-size image problem.
- Paper jam message with no jam: see paper jam, no jam.

7. Rule out Word itself
If only Word fails, check whether Word is stuck rather than the printer. If Word freezes when you print, see Word not responding. If Word crashed with an unsaved document, our recover unsaved Word and Excel document guide can help you get your work back before you experiment further.
Two quick Word experiments: start Word in Safe Mode by holding Ctrl while opening it (add-ins are disabled), then try printing; and turn off File, Options, Advanced, Print, Use draft quality and Print background colors and images to see whether the problem changes. These do not fix the known Microsoft issue, but they help isolate a different cause.
Realistic scenarios (illustrative)
These are made-up examples built from common support situations, not real client cases.
Scenario 1: the office with invoice templates. A small contractor's office of six people prints invoices from a Word template that includes a thin line image under the header. After the November update, invoice printing fails on three PCs but works on one that has not rebooted since updating. The owner uses the sorting test, sees that a plain document prints, and replaces the thin line image with a paragraph border. All six PCs print again in about 15 minutes of work, with no update removed.
Scenario 2: the home user with one urgent form. Someone must print a signed school form by 5 PM. The Word file fails every time. She saves it as a PDF, opens it in Edge and prints successfully. She leaves the update installed. Total time: five minutes.
Scenario 3: the false alarm. A dentist's receptionist blames the Windows update because the printer stopped right after patching. The printer's test page fails too, so it is not the zero-size image issue. The cause is that the printer received a new IP address and Windows kept the old port. Updating the port in Printer properties fixes it. Lesson: do the sorting test before blaming the headline bug.
Printable checklist
Printing after a Windows update: checklist
- ☐ Windows test page prints (printer and driver are fine)
- ☐ Plain one-line document prints (not a general failure)
- ☐ Failing document saved as PDF and printed from a PDF reader
- ☐ Selection Pane checked for hidden images, watermark removed, tiny spacer pictures replaced
- ☐ Print resolution changed and retested
- ☐ Second printer, second app or second PC tested for urgent jobs
- ☐ Spooler restarted, queue cleared, port and IP checked
- ☐ Driver reinstalled from the manufacturer's site
- ☐ Backup done before any update uninstall
- ☐ Date noted, release health checked weekly, update reinstalled once Microsoft announces a fix
Cost: doing it yourself versus calling a technician
| Option | Typical cost | Time | Best for |
|---|---|---|---|
| Print via PDF, remove hidden objects | 0 CAD | 5 to 30 minutes | One user, one or two documents |
| Reinstall driver and reset spooler | 0 CAD | 20 to 45 minutes | Printer fails on all documents |
| Uninstall update (last resort) | 0 CAD, but weakens security | 20 to 40 minutes with restart | Business-critical printing with no other route |
| Remote technician session | Our standard 119.99$ CAD, 60 minute Expert Consultation, if you choose it | Usually one session | Several PCs, shared printers, or when you are unsure what is safe to change |
Waiting is also an option. Microsoft normally ships fixes for confirmed known issues in later updates, and the bug does not damage your files or printer.
Official resources
- Windows release health: Microsoft Learn, Windows release health, with separate pages for Windows 11 26H2, 25H2, 24H2 and Windows 10 22H2.
- KB5132061: the November 10, 2026 update page on support.microsoft.com, with the list of known issues for that update.
- Microsoft 365 admin center, Service health: where administrators can read alert WI1549472 directly.
- Feedback Hub: the Windows app for reporting problems to Microsoft.
- BleepingComputer: the news report that first summarized the alert for the public.
When to call a pro
- Several PCs or a shared office printer are affected and you cannot afford downtime.
- You are considering uninstalling the update on business computers and want someone to weigh the security risk.
- The sorting test does not match the known bug and you cannot find the real cause.
- A document you need contains hidden objects you cannot locate or remove.
IT Cares has provided remote support, and on-site help across Quebec, since 2014. Call 1 (888) 711-9428. We connect remotely, find out whether it is this bug or a normal printer fault, and fix it while you watch. Rated 4.9 stars on Google.
Last verified: November 18, 2026. We will update this page when Microsoft publishes a fix or workaround for alert WI1549472.
Still stuck? Get a technician on it now
Remote support from IT Cares: we connect to your device, fix it with you watching, and explain what happened.
Frequently asked questions
Related guides
- Printer not working: complete fix guide
- Windows 11 November 2026 Patch Tuesday issues
- Cannot connect to printer: fix
- Printer spooler error
- Printer offline: fix
- Windows Update stuck or failing
- Windows won't boot after update
- How to update drivers
- Recover an unsaved Word or Excel document
Sources and official references
Last verified: November 18, 2026
- BleepingComputer: Microsoft says November security updates cause printing issues (opened 2026-11-18)
- Microsoft Support: KB5132061, November 10, 2026 update (opened 2026-11-18)
- Microsoft Learn: Windows 11, version 24H2 known issues (opened 2026-11-18)
- Microsoft Learn: Windows 10, version 22H2 known issues (opened 2026-11-18)
