Printer Prints in Wrong Font After Driver Update: Fixed

It's Almost Always the Font Cache

You just updated your printer driver, and now your documents look like someone swapped fonts mid-print. Every 'Arial' is showing up as 'Times New Roman', or worse, some garbage serif font you've never seen. I've seen this on HP LaserJets, Canon imageCLASS, Brother HL series, and Epson WorkForce printers. The cause: Windows cached the old font mapping when the old driver was in use, and the new driver expects a different set of font files or mappings.

The Real Fix: Clear the Font Cache

Don't bother reinstalling the driver again — that wastes time. The fix is wiping the font cache so Windows rebuilds it fresh. Here's the step-by-step:

1. Close all open applications — especially Word, Excel, or any program that might have fonts loaded.
2. Open File Explorer and type %windir%\ServiceProfiles\LocalService\AppData\Local in the address bar, then hit Enter.
3. Find the folder named FontCache. You'll see a few files in there — FontCache.dat and possibly others like FontCache-System.dat.
4. Delete everything inside the FontCache folder. Don't delete the folder itself, just the files.
5. Open Task Manager (Ctrl+Shift+Esc), go to the Services tab, find FontCache service, right-click it, and select Stop.
6. With the service stopped, go back to File Explorer and verify the FontCache folder is empty. If any files remain, manually delete them.
7. Now restart the FontCache service. In Task Manager, right-click FontCache and select Start.
8. Reboot your PC. Yes, you need to reboot — the cache rebuilds during boot.
9. After reboot, test print from Notepad first. If that works, test from your actual application.

That's it. 90% of the time, you're done.

Why This Happens

Windows caches font data so apps load faster. When you install a new printer driver, it often registers new font metrics or substitutes — especially with PostScript or PCL printers. The old cache still points to fonts that the new driver doesn't handle the same way. So Windows does font substitution at print time, picking whatever it thinks is close. Clearing the cache forces Windows to re-read all font data from scratch. The new driver's font info gets properly indexed, and your prints come out correct.

Pro tip: This also happens when you upgrade from Windows 10 to 11, or after a major Windows update that includes driver changes. Same fix applies.

Less Common Variations & Their Fixes

1. Font Corruption in the Driver Itself

Sometimes the driver update didn't install cleanly — partial font files get left behind. If clearing the cache didn't work:

• Go to Settings > Apps > Installed apps, find the printer driver, and choose Uninstall.
• Run printui /s /t2 (open Run, type that) to open the Print Server Properties. Go to the Drivers tab, remove any leftover driver entries for your printer.
• Reboot, then re-download the driver fresh from the manufacturer's site — not Windows Update. Windows Update often pushes generic drivers that don't include proper font tables.

2. Font Substitution Table in the Printer Driver

Some drivers — especially for HP and Canon — have a font substitution table buried in the printer preferences. Open Devices and Printers, right-click your printer, select Printing Preferences. Look for a tab labeled Fonts or Advanced. Check if any fonts are manually mapped to substitutes. Reset to defaults.

3. PostScript vs PCL Mode Mismatch

This one's sneaky. Some printers can run in PostScript or PCL mode. If your driver update switched modes, fonts will look different. Check the printer's display panel for the current language. For HP printers, enter the menu and look for I/O or Printer Language. Set it to match what the driver expects. Usually, PCL is safer for most offices — PostScript is only needed for Adobe-heavy workflows.

4. Third-Party Font Management Software

If you use FontBase, NexusFont, or Suitcase Fusion, those can interfere. Disable them temporarily, clear the font cache again, and test. Re-enable them one at a time to find the conflict.

How to Prevent This Next Time

• Never install printer drivers from Windows Update. Always download the full driver package from the manufacturer's website. The Windows Update versions are stripped down — they often lack included fonts and PPD files.
• Before updating a driver, create a system restore point. That way you can roll back not just the driver but the entire font state if things go sideways.
• If your workflow relies on specific fonts (like for legal documents or branding), keep a test document handy. Print it after any driver change before doing production work.
• On multi-user systems, consider using the Print Management Console (printmanagement.msc) to deploy drivers — it deploys fonts along with them more reliably than standard installers.

That's the playbook. Clear the cache, reboot, and you're usually golden. If not, check the driver source and printer language mode. I've never seen this problem survive that combo.