A man studies printer error messages on dual monitors at his office desk.
Windows 11 administrators running Microsoft's rebootless hotpatch servicing have a new problem to look into. Since Microsoft released hotpatch KB5132043 on November 10, 2026, posts on Microsoft Q&A and Reddit have described the Print Spooler service stopping and every printer showing as "Not connected." In some cases that includes Microsoft Print to PDF, which has no cable or network connection that could fail.

Microsoft has not confirmed a printing bug. As of this writing, the KB5132043 release notes still say Microsoft is not currently aware of any issues with the update. What exists is a set of matching field reports, a common error code and some recovery paths that admins say worked for them. That is enough to start an investigation, but it is not a known issue.

A man studies printer error messages on dual monitors at his office desk. What KB5132043 is and who receives it​

KB5132043 is a security-only hotpatch for Windows 11 versions 24H2, 25H2 and 26H2. Hotpatches apply security fixes without a restart. They are not the normal monthly update for every PC. Hotpatch is aimed at managed fleets: according to Microsoft's Windows Autopatch documentation, devices need an eligible license (Windows 11 Enterprise E3/E5, Microsoft 365 F3, Education A3/A5, Microsoft 365 Business Premium or Windows 365 Enterprise), virtualization-based security enabled, Intune management with a hotpatch-enabled quality update policy, and the current quarterly baseline. For this release, that baseline is KB5127648. Devices that don't qualify get the standard cumulative update (LCU) instead.

A third-party guide makes the same point: KB5132043 is a Hotpatch for eligible Enterprise and Education devices managed with Intune or Windows Autopatch. If a home user says "the November update broke my printer," they almost certainly mean something else.

The build numbers are close enough to mix up in a support ticket:

Windows 11 versionKB5132043 hotpatch buildKB5132061 standard LCU build
24H226100.991126100.9974
25H226200.991126200.9974
26H226300.991126300.9974

In short: a build ending in .9911 means the device took the hotpatch. A build ending in .9974 means it took the standard November LCU. Check the build before you blame either package.

What admins are reporting​

The most detailed report is a Microsoft Q&A post dated November 11:

  • Environment: Intune-managed devices. One machine ran Windows 11 25H2, build 26200.9911, with KB5132043 and the PowerShell security update KB5135385 installed.
  • Symptoms: Settings showed every printer as "Not connected," including Microsoft Print to PDF. Printing is unavailable, and Add Printer reports that the local Print Spooler service is not running.
  • Diagnostics: Get-Printer returns "The spooler service is not reachable," HRESULT 0x800706BA. Running sc.exe queryex spooler showed the service STOPPED with WIN32_EXIT_CODE 1067 and PID 0. RPC-related services were still running.
  • What failed: updating Windows, restarting the computer and restarting the spooler.
  • What worked: Uninstalling KB5132043 restored printing on one affected computer. The poster said they had not found the underlying cause.

A second Q&A thread, opened the same day, gave the short version: after installing KB5132043, printers show 'Not connected' and cannot print. Uninstalling KB5132043 resolves the issue. Other users replied with the same problem. One asked whether Sharp MFP drivers might be involved. Another said installing the non-hotpatch KB5132061 fixed it for them.

On Reddit's r/sysadmin, a November 17 post described stopped spoolers on a group of devices from different manufacturers and regions, all on builds ending in .9911. The poster said removing the hotpatch restored printing and that moving to KB5132061 (.9974) fixed it in their testing. The cost was a manually installed 4.4 GB MSU and two automatic reboots, and they turned hotpatch off for now. Other people in the thread said they had no problem. One traced their own failure to Forcepoint still running on some PCs. That is one person's experience, but it shows other software on the machine could be involved.

What exit code 1067 tells you​

Exit code 1067 means the process ended unexpectedly. HRESULT 0x800706BA here simply means the spooler isn't there to answer. Neither error names a culprit. The spooler loads drivers, print processors, port monitors and vendor utilities into its own process, so a crash in any of them stops the whole service.

That is why the Print to PDF failure matters. It has no physical connection, so if it goes offline along with everything else, the spooler itself is down. You don't have dozens of separate printer faults.

Independent Advisor Jason Nguyen Tran made this argument in the Q&A thread: the update may be exposing an existing issue with a print driver, print monitor, printer management software, or spooler dependency rather than the update itself being the sole root cause. He is a community volunteer, not Microsoft, and he was offering a theory. Still, given the Sharp and Forcepoint comments, it fits what people are seeing.

There is also a detail other coverage has missed. November's security release patched the print subsystem itself. Vulnerability trackers list KB5132043 among the fixes for CVE-2026-113770 Windows Print Spooler Components Elevation of Privilege Vulnerability. The Patchocalypse tracker lists a second CVE (CVE-2026-112811), described as a stack-based buffer overflow in Windows Print Spooler Components allows an authorized attacker to elevate privileges locally. It shows KB5132043 builds .9911 and KB5132061 builds .9974 as the fixed versions for 24H2, 25H2 and 26H2.

This is context, not a diagnosis. Patching spooler components is the kind of change that could expose a fragile third-party driver. But the same fixes also ship in KB5132061, and that package reportedly restores printing for some admins. If both contain the same security fixes, the hotpatch delivery mechanism could be the difference, or something else entirely. Nobody knows yet, and pretending otherwise would be fan fiction.

The KB5132061 printing fix is a different bug​

KB5132061 includes a printing fix, but not for this problem. It fixes an October regression where adding a printer published in Active Directory from Settings > Bluetooth & devices > Printers & scanners > Add device could fail with error 87, "The parameter is incorrect." Microsoft says that bug started with the October 2026 update and generally doesn't affect existing printers or printing. A crashed local spooler is a different issue, so don't treat that fix as Microsoft confirming this one.

KB5132061 also has its own notes: an installation problem that Microsoft says was repaired automatically through Windows Update starting November 11, and a known issue with SQL Server linked servers on server devices. Reports also differ. One third-party guide says printing failures are reported after Hotpatch KB5132043 and cumulative update KB5132061, both released on 10 November. So switching to the LCU should be tested, not assumed to work.

A step-by-step triage plan​

Microsoft's hotpatch documentation says automatic rollback isn't supported, but you can uninstall a hotpatch. If a hotpatch causes an unexpected problem, Microsoft says to uninstall it, install the latest LCU and restart. With that in mind, here is a sensible order of work.

1. Confirm the device is in scope

  • Record the Windows version, full OS build and update history. A build ending in .9911 means the hotpatch is installed.
  • Note the hotpatch policy assignment in Intune.

2. Confirm the symptom matches

  • Run Get-Service Spooler and sc.exe queryex spooler. You're looking for STOPPED with exit code 1067.
  • Start the service once and watch whether it dies straight away.
  • Compare Microsoft Print to PDF with a physical queue. If one printer is offline but the spooler is healthy, you have a different problem.

3. Collect evidence before changing anything

  • Check Event Viewer under Windows Logs > Application and System, and under Applications and Services Logs > Microsoft > Windows > PrintService, for spoolsv.exe crashes and faulting modules.
  • Compare an affected machine with a working one: printer drivers, print processors, language monitors, vendor print utilities and endpoint security agents.

4. Change one thing at a time on a pilot device

  • If you clear the spool folder (%WINDIR%\System32\spool\PRINTERS), remember it deletes pending jobs. One Q&A answer notes it discards pending print jobs, but does not remove installed printers.
  • If the crash points to the same third-party module every time, update or remove that component first. That may fix printing without removing a security update.

5. Test moving to the LCU

  • One Q&A answer suggests, as a contained test, that admins exclude a small affected-device group from the hotpatch-enabled policy or assign it a quality-update policy with hotpatch disabled. Then uninstall KB5132043 on one device, install KB5132061 and restart.
  • Success means the build ends in .9974, the spooler stays running, Get-Printer lists your queues, and both a physical printer and Print to PDF actually print.

6. Escalate with evidence

  • If the problem comes back reliably, open a Microsoft support case with event logs, the driver inventory, the builds of affected and unaffected machines, and before-and-after results showing what changed when KB5132043 was removed.

Don't leave devices unpatched​

Uninstalling KB5132043 and moving on leaves a machine without the November security fixes, which include patches to the same print components that are now crashing. Tran put it plainly: Microsoft explicitly recommends this path when a hotpatch causes an unexpected problem: uninstall the hotpatch, install the latest standard cumulative update (LCU), and restart. Strictly, that wording comes from an AI-generated answer in the same thread, but it matches Microsoft's Autopatch documentation. Treat uninstalling as a temporary workaround. The goal is either the LCU or a fixed driver.

What this means for hotpatch​

Hotpatch exists to avoid reboots, and recovering from this means taking two of them. This isn't a reason to give up on hotpatch: the evidence doesn't show a defect affecting every Windows 11 device, and plenty of admins say they aren't affected. It is a reason to make sure your pilot ring covers printing, including shared queues, Print to PDF and the old vendor driver that one department won't let go of. An update can install without errors and still stop people printing.

Summary: If you're on build .9911 and the spooler is crashing with 1067, the problem is real for you even though Microsoft hasn't acknowledged it. Collect crash data, test the LCU on one device, and watch the release notes in case Microsoft publishes a known issue.

Have you seen spooler crashes after KB5132043, or traced one to a specific driver or security agent? Post the faulting module in the forum's Windows Update and printing threads so others can compare.

 

References

  1. Windows 11 Hotpatch KB5132043 Sparks New Complaints - TechBarrista TechBarrista 2026-11-19T03:09:54+00:00
  2. November 10, 2026—Hotpatch KB5132043 (OS Builds 26300.9911. 26200.9911, and 26100.9911) | Microsoft Support support.microsoft.com
  3. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974) | Microsoft Support support.microsoft.com