fontdrvhost.exe
Also called fontdrvhost, usermode font driver host, font driver host
Usermode Font Driver Host. It rasterizes fonts outside the kernel so a bad font is less likely to crash Windows.
What you need to know
This isolates font drawing so a corrupt font is less likely to bugcheck the kernel.
fontdrvhost.exe is Usermode Font Driver Host. Microsoft moved font rasterization out of the kernel after font bugs became crash bugs. Two copies, one per session, are common.
- Safe?
- Yes. It isolates fonts
- Why two copies?
- Session 0 and your session
- Should I end it?
- Text can vanish or apps can crash
What is fontdrvhost.exe?
fontdrvhost.exe is the usermode font driver host. It parses and rasterizes fonts in user mode. Older Windows did more of this in the kernel.
What does it do?
Apps ask GDI or DirectWrite for glyphs. The host does the unsafe parse away from ntoskrnl. Desktop Window Manager then composites the pixels.
Why is it running?
Any session that draws text needs it. A session 0 copy and an interactive copy at the same time are expected, not a duplicate infection.
Why are there multiple copies?
One copy for session 0 and one for your desktop is normal. Extra copies from a user folder are not.
Is it safe?
Usually safe
System32 plus Microsoft is the isolator. A fontdrvhost.exe in a font-pack crack is using the name.
A legitimate copy normally runs from:
C:\Windows\System32\fontdrvhost.exe
- Expected publisher: Microsoft Corporation
- Often two copies, different sessions
- Exists to keep font parsing out of the kernel
Can I end it?
No
Ending the host can blank text or crash the app that was drawing. It is not a visual-effects toggle.
Can I remove it?
No
Do not delete fontdrvhost.exe. Windows needs it to draw fonts safely.
Should it start with Windows?
The session starts it. There is no supported Startup Apps off switch.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Can rise while a document with many unusual fonts first opens
- Memory
- Follows cached faces
- Disk
- Font cache reads
- Network
- None
File information
| Executable name | fontdrvhost.exe |
|---|---|
| Common legitimate path | C:\Windows\System32\fontdrvhost.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
High CPU in a PDF or Office file
Embedded fonts can hammer the host once. That is the document, not a miner named Font Driver.
Crash after installing a free font pack
Remove the last installed fonts. Isolation reduces kernel crashes. It does not make every font well-formed.
Troubleshooting
Diagnose before you change anything destructive.
Clear the font cache only after a known bad pack
Rebuilding the cache is a repair for garbage fonts, not a monthly ritual.
Do not replace the exe
Servicing owns this file.
Technical details
Technical details
| Image name | fontdrvhost.exe |
|---|---|
| Role | Usermode Font Driver Host |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft: usermode font driver · Font rendering isolation context
- Microsoft Learn: Windows · Primary Windows documentation
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.