Why did I recently begin having a display problem with fonts.
I recently started seeing a lower quality font display in my web based email program and can't pinpoint it to anything that changed on my pc, unless it was an update to Firefox. Also noticed that the headers of Google search results have tiny dots on top of all the letters.
The two images show my web mail in Firefox and also in IE which is how the fonts used to display in Firefox. I also noticed that this is happening on seemingly random emails as some actually display the font correctly. I am running ver. 36.0 and it is up to date.
Well, I've been trying to upload the images for a while now, but I can't see if there is any progress being made. I can email the .png files if anyone is interested. Thanks.
Chosen solution
hi, this is probably caused by microsoft update kb3013455 which can cause font rendering issues on vista:
After you install security update 3013455, you may notice some text quality degradation in certain scenarios. The problem only occurs on systems that are running Windows Vista SP2 or Windows Server 2003 SP2. Microsoft is researching this problem and will post more information in this article when the information becomes available.
reference: https://support.microsoft.com/kb/3013455
in order to address that you'll have to manually install this follow-up patch provided by microsoft, which should fix the problem: http://support2.microsoft.com/kb/3037639
Read this answer in context 👍 1All Replies (1)
Chosen Solution
hi, this is probably caused by microsoft update kb3013455 which can cause font rendering issues on vista:
After you install security update 3013455, you may notice some text quality degradation in certain scenarios. The problem only occurs on systems that are running Windows Vista SP2 or Windows Server 2003 SP2. Microsoft is researching this problem and will post more information in this article when the information becomes available.
reference: https://support.microsoft.com/kb/3013455
in order to address that you'll have to manually install this follow-up patch provided by microsoft, which should fix the problem: http://support2.microsoft.com/kb/3037639