How to Fix Missing or Corrupted Fonts on Your Windows Computer
Published 2026-10-16 · Marion Remote Fix
Text on your screen displays as empty boxes, question marks, or completely wrong characters. Documents that looked fine before now show placeholder symbols instead of the expected fonts. Some applications display text normally while others show garbled or missing characters. Missing and corrupted fonts are a common Windows problem caused by damaged font files, incomplete installations, failed updates, or system file corruption that affects the font cache.
How Windows handles fonts
- Windows stores system fonts in the Fonts folder within the Windows directory. These include core fonts like Arial, Times New Roman, Calibri, Segoe UI, and Consolas that the operating system and most applications depend on
- Applications reference fonts by name. When an application requests a font that Windows cannot find or cannot read, it either substitutes a different font (changing the appearance of text) or displays placeholder characters like empty rectangles or question marks
- Windows maintains a font cache that speeds up font loading. If this cache becomes corrupted, fonts may fail to render even though the font files themselves are intact on disk
- Third-party fonts installed by the user or by applications are also stored in the system Fonts folder or in per-user font directories. These fonts are more susceptible to corruption during installation or system updates
Rebuild the font cache
The font cache is the most common cause of font display problems. Rebuilding it forces Windows to re-read all font files and create a fresh cache.
Stop the font cache service
- Open the Services application by searching for Services in the Start menu. Find Windows Font Cache Service in the list
- Right-click the service and select Stop. Also stop the Windows Presentation Foundation Font Cache service if it appears in the list
- Set both services to Manual startup temporarily so they do not restart before you finish the cleanup
Delete the cache files
- Open File Explorer and navigate to the ServiceProfiles folder inside the Windows system directory, then LocalService, then AppData, then Local. Look for files that start with FontCache
- Delete all FontCache files in this directory. There may be several files with different extensions
- Also check the Windows directory for a file called FNTCACHE.DAT and delete it if present
Restart the services
- Go back to the Services application. Set Windows Font Cache Service back to Automatic startup and start it. Do the same for the WPF Font Cache service
- Restart the computer. Windows rebuilds the font cache automatically on the next boot. The first startup after clearing the cache may be slightly slower as Windows re-indexes all installed fonts
Restore default Windows fonts
- If system fonts are missing or corrupted, restoring the default font set replaces damaged files with clean copies
- Open Settings, Personalization, Fonts. Scroll down or look for a link that says Restore Default Font Settings. Click it to reset the font configuration to the Windows default
- This option restores font registration and visibility settings but does not re-download missing font files. If the actual font files are deleted from the Fonts folder, you need to restore them from another source
Reinstall missing fonts from Windows installation media
- If core system fonts are missing from the Fonts folder entirely, you can extract them from the Windows installation files
- The System File Checker tool can restore missing system fonts. Open Command Prompt as Administrator and run the system file checker scan command. This scans all protected system files, including fonts, and replaces missing or corrupted ones from the component store
- If the component store itself is damaged, run the Deployment Image Servicing tool with the restore health option first, then run the system file checker again. The servicing tool repairs the component store using Windows Update as a source
Fix fonts showing as boxes or squares
- When text appears as empty rectangles or squares, the application is requesting a font that is either not installed or not compatible with the characters being displayed
- This commonly happens with multilingual text. If a document contains Chinese, Japanese, Korean, Arabic, or other non-Latin characters and the required font pack is not installed, Windows shows boxes instead
- Install the optional font features for the languages you need. Open Settings, Apps, Optional Features (Windows 10) or Settings, Time and Language, Language and Region (Windows 11). Add the language pack or supplemental font pack for the script that is not displaying correctly
- Common supplemental font packs include fonts for Pan-European scripts, Chinese (Simplified and Traditional), Japanese, Korean, Thai, Arabic, Hebrew, and Devanagari. Each pack adds the fonts needed to display that writing system
Fix fonts that look wrong or substituted
- When text displays in a different font than expected (a document designed in Calibri shows in Arial, for example), the expected font is missing and Windows is using a substitute
- Check whether the expected font is installed. Open the Fonts folder in Settings or Control Panel and search for the font name. If it is not listed, the font needs to be installed
- Font substitution can also happen when a font file is present but corrupted. The font appears in the font list but does not render correctly. Remove the corrupted font (right-click and delete in the Fonts folder) and reinstall it from the original source
- Some applications bundle their own fonts and do not use the system font directory. If a font looks wrong in one specific application but fine everywhere else, check the application settings for a font configuration option or reinstall the application
Fix fonts after a Windows Update
- Windows Updates occasionally cause font problems by updating font files, changing font registration, or resetting the font cache. If fonts broke after an update, the update likely modified or replaced font components
- First try rebuilding the font cache using the steps above. Many post-update font issues are cache-related rather than actual font file damage
- If rebuilding the cache does not help, run the system file checker. The update may have left font files in an inconsistent state that the checker can repair
- As a last resort, check Windows Update history for the specific update that caused the problem and uninstall it temporarily while waiting for a fix from Microsoft
Font problems in specific applications
Office applications
- Microsoft Office installs its own fonts (Calibri, Cambria, Aptos, and others). If Office fonts are missing, repairing the Office installation restores them. Open Settings, Apps, find Microsoft Office or Microsoft 365, click Modify, and select Quick Repair or Online Repair
- If fonts look wrong only in Office but fine in other applications, the Office font cache may be corrupted independently of the Windows font cache. Close all Office applications, search for the Office font cache files in the user AppData directory, delete them, and reopen Office
Web browsers
- Browsers render web fonts downloaded from the internet alongside system fonts. If text on websites appears garbled but desktop applications look fine, the browser font rendering settings may be misconfigured
- In browser settings, look for font configuration options. Ensure the default fonts are set to common system fonts (Arial, Times New Roman, or Segoe UI) and that the option to allow websites to use their own fonts is enabled
- Hardware acceleration in the browser can sometimes cause font rendering artifacts. Try disabling hardware acceleration in browser settings to see if font display improves
Per-user fonts versus system fonts
- Windows 10 version 1809 and later allows fonts to be installed per-user rather than system-wide. Per-user fonts are stored in a different location than system fonts
- If a font works for one user account but not another, it may be installed per-user. To make it available system-wide, right-click the font file and select Install for All Users, which requires administrator permissions
- Some applications, particularly older ones and those running as a different user or as a service, cannot access per-user fonts. If an application cannot find a font that appears installed, try reinstalling the font system-wide
Font file formats
- Windows supports TrueType fonts (TTF), OpenType fonts (OTF), and TrueType Collections (TTC). If you are trying to install a font in a different format (such as web-only WOFF or WOFF2 files), Windows may not be able to use it as a system font
- Corrupted font files can crash the font rendering system or cause specific characters to display incorrectly. If you suspect a font file is corrupted, remove it and reinstall from the original source
- Very large font collections (hundreds of installed fonts) can slow down font loading and increase the chance of cache corruption. Remove fonts you do not use to reduce the load on the font system
Registry font registration
- Windows tracks installed fonts through registry entries. If a font file exists in the Fonts folder but does not appear in the font list for applications, the registry entry may be missing
- Re-registering fonts involves adding the font filename to the registry under the Fonts key. For most users, the simplest approach is to remove the font file from the Fonts folder, then reinstall it by right-clicking the file and selecting Install. This recreates both the file and the registry entry
- Third-party font management tools can sometimes leave orphaned registry entries or remove entries without removing files, causing mismatches between what Windows thinks is installed and what is actually available
Need help with font problems?
If fonts on your computer are missing, corrupted, or displaying incorrectly and the steps above have not resolved the issue, Marion Remote Fix can remotely diagnose font rendering problems, rebuild your font cache, restore missing system fonts, and fix application-specific font issues without you needing to bring your computer anywhere.