Fix Font Substitution Issues After Installing Custom Fonts on Windows 11

Quick fix: Sign out and sign back in (or restart Explorer) after installing custom fonts. If documents still show wrong fonts: open Settings → Personalization → Fonts. Verify font is listed. Open the document in Word → check the font name — if it shows in brackets like “{Roboto}”, font isn’t available. Reinstall via right-click → Install for all users.

Installing custom fonts can trigger substitution issues: Word documents using the custom font may render in a default font. Or specific apps don’t recognize the new font. Cause: per-user vs all-users install mismatch, font file corruption, or font cache.

What causes this

Windows uses two font locations: per-user (%LOCALAPPDATA%\Microsoft\Windows\Fonts) and system-wide (C:\Windows\Fonts). Apps look in different places depending on configuration. Mismatches cause substitution. Other causes: font cache corruption, font file is .otf but app needs .ttf, font missing some required name table entries.

Method 1: Sign out and back in

The first step.

1. Custom fonts installed per-user need session refresh.
2. Save your work. Sign out (Start menu → profile picture → Sign out).
3. Sign back in.
4. Open the app. Font should now appear in font lists.
5. For full reset: reboot PC.
6. For per-app refresh: close and reopen the app. Some apps cache font lists at startup.
7. For Office: File → Account → Office Insider → if available, sign out/in to Office.

This is the simple fix.

Method 2: Reinstall font as “all users” instead of per-user

For wider availability.

1. Open Settings → Personalization → Fonts.
2. Click the font → Uninstall.
3. Confirm.
4. Now reinstall: right-click the original .ttf/.otf file.
5. Pick Install for all users (not just “Install”). Requires Admin.
6. UAC. Yes.
7. Font now installed system-wide: C:\Windows\Fonts.
8. Available to every user account on PC.
9. Sign out / in. Test in app.
10. For multi-user PCs: ensures all users see the font.
11. For per-user requirement: some scenarios prefer per-user (sandboxed app deployment). Keep per-user but ensure sign-out/in.

This is the standard reinstall.

Method 3: Clear and rebuild font cache

For font cache corruption.

1. Font cache speeds up app font loading. Corruption causes incorrect rendering.
2. Open Services (services.msc).
3. Find Windows Font Cache Service. Right-click → Stop.
4. Find Windows Presentation Foundation Font Cache (if present). Right-click → Stop.
5. Open File Explorer. Show hidden files.
6. Navigate to: C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache.
7. Delete all .dat files in this folder.
8. Navigate to: C:\Users\[username]\AppData\Local\Microsoft\Windows\Fonts (per-user font cache, if applicable).
9. Delete cache files.
10. Restart the services.
11. Sign out / in or reboot. Fonts re-cache from disk.
12. Apps should now render fonts correctly.

This is the cache rebuild.

How to verify the fix worked

• Settings → Personalization → Fonts: custom font listed.
• In Word / app: font appears in font picker and renders correctly.
• Documents made with that font don’t show substitute glyphs.
• Browser: web pages requesting the font render with it.

If none of these work

If font still substituted: Font file corruption: re-download font. Verify file with FontForge or other tool. Reinstall. For .otf vs .ttf: some old apps prefer .ttf. Convert .otf to .ttf via online converter or FontForge. For Office-specific issue: Office may use a different rendering path. Check Office’s Font tab in document or via File → Account → Update Options → Update Now (refresh Office). For specific app refusing: app has its own font registry. May need to re-launch with admin rights. For variable fonts: older apps don’t render. Install static variant instead. For licensed fonts (Adobe Fonts): managed via Adobe Creative Cloud. Different install mechanism. For Linux / web fonts: TTF/OTF expected on Windows. Avoid WOFF/WOFF2. Last resort: clean install Windows: rare; usually not the right answer for font issues.

Bottom line: Sign out and back in after install. Reinstall as “Install for all users” for system-wide. Clear font cache (FontCache service + .dat files in FontCache folder) for corruption.