Microsoft disclosed this month that its August 2026 Patch Tuesday.NET Framework cumulative update breaks printing and PDF export in applications built on Windows Presentation Foundation, the graphical subsystem used to build Windows desktop client software. Affected apps throw a System.IO.FileFormatException when printing or generating PDF or XPS content that uses certain fonts, with Calibri—one of the most widely deployed default fonts in corporate documents—explicitly named in Microsoft's Windows release health alert.
The scope runs across Microsoft's installed base. On the client side, the issue hits Windows 10 and Windows 11. On the server side, the breakage extends from Windows Server 2012 through Windows Server 2025, covering more than a decade of infrastructure still running in enterprise data centers. KB5120708, the Windows 11 25H2.NET Framework cumulative update, is the confirmed trigger; Microsoft ships the same underlying security fix under different KB numbers for other Windows versions.
Microsoft is still investigating and has not shipped a permanent fix. The company published a workaround requiring an AppContext switch—Switch.MS.Internal.TtfDelta.DisableCmapAndSbitOverflowProtection—in the affected application's config file. The name makes the trade-off explicit: it disables the TrueType font delta subsetting overflow protection that the August update introduced.
Microsoft's release health guidance warns that the workaround strips the protections the August update was designed to install, leaving systems exposed to the vulnerabilities the patch addressed. The company recommends using the workaround only temporarily and only when printing failure directly requires it—forcing enterprise IT teams to choose between broken workflows and reduced security until a proper fix ships.
A second workaround has circulated in Microsoft's Q&A forums: substituting Calibri in documents and templates with fonts such as Arial or Times New Roman that still subset cleanly under the patched code. That approach restores print and XPS output without requiring patch removal, though it requires manual document remediation across any template using Calibri as a body font.
Covetrus, which makes the ImproMed veterinary practice management platform ranked 593 on the Fortune 1000, confirmed the update broke the software's Print Reminder Reports feature, a workflow used daily in veterinary practices across the country. ImproMed's reliance on WPF for its print stack is representative of a broad category of line-of-business applications—accounting packages, legal document software, healthcare records platforms—built on WPF precisely because it handles complex document rendering natively on Windows. CCH, a tax and accounting software maker, is also among confirmed affected applications.
This is not the first time a Microsoft cumulative update has grounded WPF-dependent software. In February 2021, Windows 10 cumulative updates caused WPF applications and Visual Studio to crash outright. The recurring pattern points to an inherent tension in shipping security fixes for a font-subsetting stack that enterprise software vendors have built complex print pipelines on top of—changes to the TrueType handling layer ripple into applications that never expected the underlying behavior to shift.
For enterprise IT and managed service providers, the decision tree is constrained. Organizations where printing and PDF generation are revenue-critical—law firms, medical practices, accounting firms—face a direct choice: apply the config-file workaround and accept reduced security coverage, substitute fonts across document templates, or wait for Microsoft to ship a permanent fix on a timeline the company has not disclosed.
