Posted 28 October 2017 - 11:36 PM
Good to hear, thanks for letting us know of your success.
If you run an application in the future which becomes slow or unstable, it may possibly use the Windows Presentation Foundation, and be struggling without the font cache. In that case, if you find restarting the font cache service makes that program run normally, a procedure that has been stated to clear the CPU hogging is to rebuild the cache:
Find a file called FontCache220.127.116.11.dat, expected to reside in C:\Windows\ServiceProfiles\LocalService\AppData\Local, rename the file (e.g. with a .bak extension) and restart the font cache service. If a new .dat file appears and the CPU hogging stops, the .bak file can be deleted.
Top 5 things that never get done: