Font Managers for WindowsIndependent install & setup guide
Home / Troubleshooting / Conflicts and configuration problems

Conflicts and configuration problems

When the wrong version of a font shows up, text renders strangely, or apps crawl, the cause is usually duplicate fonts, a stale cache, or two tools managing the same files.

Duplicate and conflicting fonts

Two files with the same internal font name, for example an old Roboto-Regular.ttf and a newer one, compete with each other. Windows and apps pick one unpredictably, so you get the wrong version, missing weights, or shifting layouts.

  1. Run the manager's find duplicates tool. NexusFont, MainType, FontExpert and Suitcase Fusion all have one.
  2. Keep the newest version. Compare the version numbers in the font properties.
  3. Don't mix an installed copy and an activated copy of the same font. Either uninstall it from Windows or remove it from the manager.
  4. Watch for families that ship as both static and variable fonts. Use one or the other, not both.

Rebuild the Windows font cache

If fonts appear missing or garbled in every app, or a deleted font still appears, the Windows font cache may be stale. Rebuilding it is safe.

  1. Stop the font cache service

    Press Win + R, type services.msc, find Windows Font Cache Service, and click Stop. Set its startup type to Disabled for now.

  2. Delete the cache files

    In File Explorer, open C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache (click Continue if asked for permission) and delete the .dat files inside. Also delete C:\Windows\System32\FNTCACHE.DAT.

  3. Re-enable and restart

    Set Windows Font Cache Service back to Automatic, then restart Windows. The cache rebuilds automatically, and the first startup may be a little slower.

# Same steps in an elevated (Administrator) PowerShell window Stop-Service FontCache -Force Remove-Item "$env:WINDIR\ServiceProfiles\LocalService\AppData\Local\FontCache\*.dat" -Force Remove-Item "$env:WINDIR\System32\FNTCACHE.DAT" -Force -ErrorAction SilentlyContinue Restart-Computer

Running two font managers at once

Two managers that both activate fonts, or both watch the same folder, can fight: one deactivates what the other activated, or both register the same font twice.

  • Choose one manager to handle activation. You can keep a second tool for browsing only, with auto-activation and "start with Windows" turned off.
  • Don't point two managers at the same library folder with copy into library turned on.
  • When switching tools, deactivate everything in the old manager, export your collections, uninstall it, and restart before you set up the new one.

App-level font caches

Some apps keep their own font lists on top of Windows:

  • Adobe apps: close all Adobe apps, then search your %APPDATA%\Adobe folder for files named AdobeFnt*.lst and delete them. They are rebuilt on the next launch.
  • Microsoft Office: fully close every Office app, including the tray icon, and reopen. Office reads the font list at startup.
  • Browsers: restart the browser after installing fonts you want to test on local web pages.

Too many active fonts

Windows can hold thousands of fonts, but every installed font adds to startup time and to the font menu of every app. Signs include slow app launches, long font menus, and apps like Word freezing when you open the font dropdown.

Rule of thumb

Keep system fonts plus a few hundred everyday fonts installed. Keep the rest in your font manager and activate them per project. See Trim fonts installed in Windows.

Cloud sync and network folder issues

  • OneDrive's Files On-Demand can leave fonts as online-only placeholders that won't activate. Mark the font folder Always keep on this device.
  • Don't sync a manager's database between two PCs that are running at the same time. Export and import collections instead.
  • Check font licenses before syncing commercial fonts to several machines. Many desktop licenses limit the number of computers.

Still stuck? Go back to the troubleshooting overview.