KB5132061 / KB5131090: XPS print jobs truncated (last page missing) – tax software fails on Microsoft Print to PDF and mxdwdrv.dll-based printers

Pavel Tsimokhautsau 0 Reputation points
2026-11-20T10:08:44.34+00:00

Since the November 2026 updates, printing from tax preparation software (confirmed: Drake Tax, TaxAct) is broken on Microsoft Print to PDF and on virtual printers built on the XPS Document Writer driver. We see it on six machines.

Affected builds (all x64)

  • Windows 11 26100.9974 (KB5132061 + KB5132688, installed Nov 11, 2026; our repro machine, KB5132043 is not installed)
  • Windows 11 26200.9974 (KB5132061)
  • Windows 11 26300.9974 (KB5132061)
  • Windows Server 2022 20348 (KB5131090)

On one machine, all jobs printed fine the day before the update was installed, and most jobs failed right after it.

1. Microsoft Print to PDF

The PDF is created empty (0 bytes). PrintService events:

  • Event 372: "The document ... failed to print on printer Microsoft Print to PDF ... Data type: RAW. Size of the spool file in bytes: 504804. Number of bytes printed: 504804. Total number of pages in the document: 5. Number of pages printed: 0. Win32 error code returned by the print processor: 87. The parameter is incorrect."
  • Event 824: "The print filter pipeline process was terminated", 0x80070057
  • Event 842: MS_XPS_PROC returned 0x57

2. Custom virtual printer based on the XPS Document Writer driver

v3 driver: DriverFile=mxdwdrv.dll, ConfigFile=UniDrvUI.dll, depending on the in-box Unidrv and XPSDrv core drivers; a port monitor receives the XPS output.

  • The job completes in the spooler (Event 842 for winprint returns 0x0), but the XPS package the port monitor receives is corrupted: it can't be opened as a ZIP/OPC package, and the last page is missing.
  • On our repro machine (26100.9974) the output always stops at 262,144 bytes (exactly 256 KiB). The exact power-of-two size suggests the last buffer of the spool data is never flushed to the port.
  • With "Start printing after last page is spooled" enabled, the job never reaches the port monitor at all.
  • Small jobs (under ~1 MB) usually still go through. Larger multi-page jobs, such as a full return or a client copy, fail most of the time.

Workaround

Uninstalling the update is the only workaround we have, and it is not acceptable because it also removes the security fixes.

Questions

  1. Is this a known issue with KB5132061 / KB5131090? Is it tracked on the Windows release health dashboard?
  2. When can we expect a fix or a Known Issue Rollback?
  3. Is there a supported workaround that keeps the update installed?
Windows for business | Windows Server | User experience | Print jobs
0 comments No comments

2 answers

Sort by: Most helpful
  1. Hoang Le Huy 2,240 Reputation points Independent Advisor
    2026-11-20T10:42:44.0733333+00:00

    Hello Pavel Tsimokhautsau,

    Based on Microsoft's published November 2026 release information, I can confirm that KB5132061 (Windows 11) and KB5131090 (Windows Server 2022) document a printing-related issue involving error 87, but that issue concerns adding printers published through Active Directory, not the XPS rendering, PDF generation, or spooler corruption you are reporting. Your symptoms, particularly 0x80070057, Event IDs 824/842, and the consistent 262,144-byte output truncation, are not currently identified as a documented Microsoft known issue.

    The Windows 11 Release Health dashboard and the Windows Server 2022 dashboard do not currently list your specific failure, and Microsoft has not published a confirmed fix, Known Issue Rollback (KIR), or ETA for it.

    For Windows Server 2022, KB5136487 (November 13) is available, but its documented fixes do not address this printing problem.

    I recommend keeping the security updates installed, testing an alternative PDF rendering solution supported by Drake and TaxAct, and temporarily avoiding the affected virtual printer pipeline; do not modify XPSDrv or spooler registry settings without Microsoft's confirmation. Since the issue affects six machines and is reproducible, open a Microsoft Unified Support case and provide the spooler logs, failing RAW spool files, driver versions, and a minimal reproduction package, explicitly requesting investigation by the Windows Printing team. I would not promise a fix date or recommend uninstalling security updates as a permanent solution.

    If my answer is useful for you, please hit Accept** the **answer for me please.

    HL.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-20T10:10:01.38+00:00

    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_PROC failure, 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:

    1. 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.
    2. 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.
    3. Print evidence
      • Exported Microsoft-Windows-PrintService/Admin and Operational logs.
      • 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.
    4. 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

    1. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974) | Microsoft Support
    2. November 10, 2026—KB5131090 (OS Build 20348.5870) | Microsoft Support
    3. August 11, 2026-KB5120710 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 | Microsoft Support
    4. Windows 10 Enterprise LTSC 2021 known issues and notifications
    5. Debugging XPSDrv Printer Drivers
    6. Attaching a Debugger to the Print Filter Pipeline Service
    7. XPS Filters
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.