Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / How Windows 11 Is Quietly Deprecating Enterprise Fonts
Transcript
- Lucas: So Microsoft quietly stopped supporting legacy font rendering in Windows 11, and if your enterprise still relies on a custom corporate typeface from 2015, you might already be seeing subtle rendering shifts in Office documents. Luna: Wait — are we talking about fonts breaking entirely, or just looking different? Lucas: Both, depending on the font format. Specifically, Microsoft deprecated the GDI font rendering engine for most Windows 11 apps. That means any font that relied on the old GDI rasterizer — especially those with OpenType CFF outlines, which are essentially PostScript-based — can now fall back to the default fallback font or render with incorrect metrics. Luna: And this is happening even in Office? Because I feel like Word and PowerPoint have their own rendering pipelines. Lucas: That's the tricky part. Office 365 apps like Word, Excel, and PowerPoint still use their own text layout engine, which is based on DirectWrite. But that engine, since Windows 11 version 24H2, no longer supports CFF — Compact Font Format — outlines. So if you have a font that's OpenType CFF, it will silently fall back to a default like Calibri or Times New Roman in your document, and you won't get a warning until you export to PDF and the layout shifts. Luna: Right, so a legal firm that uses a custom font for all their court filings could open a template in Word, see it render correctly due to cached metrics, but when they share it or print it, the font mapping changes. That's a compliance nightmare. Lucas: Exactly. And this isn't a niche case. A lot of brands commissioned custom fonts for their identity — think banks, insurance companies, consulting firms — and many of those were built as OpenType CFF because that was the standard for high-quality print fonts for years. Now those fonts are effectively second-class citizens on Windows 11. Luna: So what's the workaround? Are IT teams supposed to relicense all those fonts in TrueType format? Lucas: That's one route, but it's expensive and time-consuming. The immediate fix for many teams is to enable the 'Use GDI font rendering' group policy — it's a legacy policy that forces Windows to use the old rasterizer. But Microsoft has indicated that policy itself is deprecated and may be removed in a future release. So it's a band-aid, not a solution. Luna: And for apps that don't respect that policy — like Edge, or third-party apps that use Chromium's font engine — they'll still skip GDI and use DirectWrite anyway, right? Lucas: Exactly. Chromium's font rendering is completely independent. So even if you set the policy, a user opening a PDF in Edge will see a different rendering than someone opening the same PDF in Acrobat. That's where the real pain comes in — cross-application consistency. Luna: That sounds like a support ticket factory. 'My document looks different in Chrome than in Word.' Lucas: And that's exactly what we're hearing from IT admins on forums and at conferences. The Windows 11 24H2 update has been the biggest trigger. Microsoft's own documentation says CFF support was removed because of 'low usage and security concerns' — but for enterprises that built their identity around a CFF font, that's cold comfort. Luna: I'm curious — is there a way to detect which fonts in your environment are cff based without manually inspecting each file? Lucas: There are tools. You can use PowerShell to enumerate installed fonts and check the 'CFF' table using the Windows API. Or use a third-party font manager like FontExplorer X or NexusFont to export a list of fonts with their outline format. But the real challenge is knowing which of those fonts are actually used in critical documents. Luna: And that requires a content audit — scanning document repositories for font references. That's a bigger project than most IT teams have budgeted for this year. Lucas: Especially because the fix isn't just technical. If you decide to convert a font from CFF to TrueType, you need the font vendor's permission — or you need to relicense the font in TrueType format. Some foundries charge for format conversion. Others, like the open-source community, have tools like fonttools that can do it, but then you're managing legal risk. Luna: And if the font is used in marketing collateral, legal documents, or SEC filings, you can't just swap it without legal review. So we're talking about a multi-department project: IT, legal, marketing, compliance. Lucas: Right. And the clock is ticking because Microsoft isn't rolling back this change. In fact, they've already removed CFF support from the Windows 11 kernel, so it's not even a fallback — it's gone. The only reason it still works in some scenarios is because older apps carry their own font engines. Luna: Like Adobe Creative Cloud apps — InDesign and Illustrator have their own rendering, so they'll still handle CFF fonts correctly for now. Lucas: But even Adobe has signaled they're moving toward an OpenType svg based approach. So the window is closing. If I were an IT manager at a large enterprise, I'd start a font inventory this quarter. Luna: And that's the kind of concrete, actionable advice that makes this show valuable, and it's why we keep these conversations ad-free. You know, we don't run ads on the Windows Podcast because we want to be able to talk about exactly these kinds of issues without any sponsor pressure. Lucas: Yeah, it's a deliberate choice. If you find these deep dives useful and want to support that independence, the easiest way is buy me a coffee dot com slash fexingo. It's literally the price of a coffee, and it helps us keep the show exactly as it is. Luna: Okay, back to fonts — one more thing I want to cover: what about the enterprise that's already standardized on TrueType? Are they in the clear? Lucas: Mostly, yes. TrueType outlines are supported natively in DirectWrite. But there's a subtlety: even TrueType fonts can have hinting issues in DirectWrite if they were designed for GDI. The new renderer is more aggressive about anti-aliasing, so text can appear blurry at small sizes on high dpi screens. Luna: So the problem isn't just CFF — it's the whole rendering pipeline shift. Any font that was tuned for GDI might look different now. Lucas: Exactly. And that's why I recommend IT teams do a visual audit — literally have someone open key documents on a Windows 10 machine and a Windows 11 machine side by side, and compare. If the kerning or weight looks off, that's a red flag. Luna: And if they find issues, what's the timeline? How long do they have before this becomes a crisis? Lucas: Well, Windows 10 goes end of life in October 2025, so by June 2026, many enterprises are already in the process of migrating. If they haven't started the font audit yet, they're in a race against their own deployment deadline. Luna: And if they ignore it, they'll have a support nightmare once users start reporting 'my document looks weird' en masse. Lucas: Right. And the fix becomes more expensive the longer you wait, because you might have to relicense fonts under time pressure, or deal with broken PDFs that need to be regenerated. So the takeaway: audit your fonts now, test on Windows 11, and plan for either a GDI policy workaround or a font migration. Luna: Great advice. And as always, we'll put links to the font auditing tools in the show notes. Lucas: Next episode, we're looking at another quiet deprecation: Windows 11 is also removing the legacy 'Snipping Tool' clipboard format — so if your enterprise HR system relies on pasting screenshots into forms, stay tuned.