Go to C:\Windows\ServiceProfiles\LocalService\AppData\Local\ ,delete all Font*.dat and reboot it.
PresentationFontCache.exe uses 50%+ of my CPU
PresentationFontCache.exe uses 50%+ of my CPU and therefore my 64 bit Windows 7 system runs even slower than it did with Vista. Is there a fix other than killing it every time I boot up?
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi,
the service PresentationFontCache.exe is only usefull if you use WPF (Windows Presentation Foundation) applications. If not, start services.msc and disable the service.
André
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
59 additional answers
Sort by: Oldest
-
Anonymous
2011-04-19T15:59:43+00:00 Help, I don't have the same folder string. After Local Service I don't have a folder named AppData. I'm running W7. Any Sugestions? My CPU usages is killing me........
-
Anonymous
2011-04-29T06:59:54+00:00 Hi
the AppData is a hidden file located in >>> local disk C >> users >>> "admin or your pc log name"
* you may use view hidden files and then you will see it.
** for your prob. I suggest to open your windows task manager and terminate the
"presentationfontcache.exe", you will never have this annoying problem any more (CPU usage 100%)
cheers
-
Anonymous
2011-04-29T12:16:56+00:00 As you know now that presentationfontcache.exe is a part of .net framework 3 and it is very much required for some applications to work properly. You should not disable it as it is highly recommended to run it.
If presentationfontcache.exe is a using very high CPU then you can try killing the process temporarily, but please note that it will start automatically after some time, you can refer our guide to block an executable to run here. Still if you want to stop presentationfontcache.exe, then you can refer some discussion here and here