This XPS/PDF truncation is not currently listed as a known issue for KB5132061 or KB5131090, so there is no published fix, ETA, or supported Known Issue Rollback; open a Microsoft Support for Business case and provide the six-machine reproduction data so Microsoft can validate and service the regression.
Current documented status
- KB5132061: Microsoft documents a printing fix for adding an Active Directory-published printer failing with error 87. The notes explicitly say that issue did not generally affect existing printers or printing. They do not list XPS package truncation,
MS_XPS_PROCfailure, empty Print-to-PDF output, or a 256-KiB cutoff as a known issue.^1^ - KB5131090: Its documented printing item is the same AD-published-printer fix. Its known-issues section does not document this XPS/PDF failure or provide a related KIR.^2^
- The matching error number does not make these the same problem: the documented issue occurs while adding a printer; yours occurs while existing queues process print data.
- No publication date for a fix can be inferred until Microsoft acknowledges the regression. A KIR package from another issue or KB must not be deployed against this one.
The August 2026 .NET/WPF XPS issues are also a different failure mode: they involve System.IO.FileFormatException, specific fonts or in-memory PackageStore identities, and were resolved by September updates. Their AppContext switches should not be applied to this spooler/pipeline truncation.^3^
Escalate with a service-ready reproduction
Open a Support for Business request under Windows printing/servicing. Microsoft’s release-health guidance directs organizational IT administrators to that channel for immediate support.^4^
Attach:
- Before/after matrix
- OS edition, version, build and architecture.
- Installed KBs and installation timestamps.
- Last known-good build and first failing build.
- Results from KB5132061 and KB5131090 systems separately.
- Two minimal samples
- One job that succeeds.
- One larger multipage job that fails.
- Original source, spool file where permitted, received XPS stream, and expected output.
- SHA-256 hashes and exact byte counts, highlighting repeatable
262144-byte output.
- Print evidence
- Exported
Microsoft-Windows-PrintService/AdminandOperationallogs. - Events 372, 824 and 842, including timestamps and activity/job IDs.
- Queue configuration, driver/INF version, print processor, data type, port monitor version, and spooling setting.
- ProcMon or equivalent trace covering
spoolsv.exe,printfilterpipelinesvc.exe, the port monitor, and destination file.
- Exported
- Reproduction statement
- Same application and document succeeds before uninstalling the update.
- Fails after reinstalling it.
- Reproduces across the listed client and server builds.
- Small versus large-job boundary and whether failure is deterministic.
XPSDrv filters run in printfilterpipelinesvc.exe, separately from spoolsv.exe; therefore, pipeline tracing is particularly relevant to Event 824 and MS_XPS_PROC failures.^5^
If Microsoft asks for live debugging, the documented PipelineHostTimeout value can keep the transient pipeline process alive long enough to attach WinDbg. This requires a registry change and should be used only on an isolated reproduction machine under support guidance.^6^
Workarounds while retaining the update
No case-matched supported workaround is currently published. The practical options are:
- Route affected tax jobs through a non-XPS/GDI-based printer path, if the application and printer vendor provide one.
- Use the tax product’s native PDF/export function, if available, rather than Microsoft Print to PDF.
- Move production printing temporarily to a controlled machine that does not exhibit the regression, subject to organizational security policy.
Changing “Start printing after last page is spooled” is not useful here because it already prevents delivery to your port monitor. Reinstalling Print to PDF, restarting the spooler, or repairing the optional feature targets missing/corrupt queues—not a reproducible cross-machine post-update stream truncation—and would not address the evidence presented.
For the custom printer’s longer-term design, Microsoft recommends the modern print platform with the inbox IPP class driver and Print Support Apps instead of legacy XPSDrv development.^7^ That is a migration path, not an immediate fix for the November regression.
References
- November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974) | Microsoft Support
- November 10, 2026—KB5131090 (OS Build 20348.5870) | Microsoft Support
- August 11, 2026-KB5120710 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 | Microsoft Support
- Windows 10 Enterprise LTSC 2021 known issues and notifications
- Debugging XPSDrv Printer Drivers
- Attaching a Debugger to the Print Filter Pipeline Service
- XPS Filters