KB3013455 (MS15-010) causes font corruption

Anonymous
2015-02-10T21:06:56+00:00

February 2015 update KB3013455 causes 'Courier New' font corruption on some Windows systems, I can confirm it for Windows Server 2003 and 2008. You can verify it in Notepad. Removing the update fixes the issue.

Windows 7 and 8.1 are not affected by the update.

[removed information that 64bit may not be affected]

Windows for home | Other | 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.

0 comments
Answer accepted by question author
Anonymous
2015-02-12T05:17:15+00:00

Yes Remove/Add Program >> View Installed Windows Updates >> I added the column to display installation date, reverse sorted and found "3013455" ((this update), then Uninstalled it.

This was common in the late 90's/early 2000's, had to remember which updates not to install that would break things. It's been solid for at least a decade, now this.

I don't really care what the fix is for. If I can't read my screen from my chair, I need to resolve it to do my job (own a web design firm).

I share the same opinion as this article "...the bottom line here is that if you want to be able to actually read the screen, you'll want to hold off installing this update until the problem is fixed."

http://windowsitpro.com/msrc/patch-tuesday-font-corruption-kb3013455

Was this answer helpful?

3 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2015-02-18T18:42:43+00:00

The link for all downloads is:

http://www.microsoft.com/en-us/search/Results.aspx?q=kb3013455&form=DLC

Choose your OS from the half dozen big options at the top and it brings you right to the download page.

Hit the big red download button and it should offer you two updates:

kb3013455   (the original that breaks fonts)

and

KB3037639  (the secondary update to fix fonts)

I installed the original, said do not reboot, and installed the second.

After reboot I appear patched and my fonts are good.

Was this answer helpful?

2 people found this answer helpful.
0 comments

300 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-02-12T15:47:39+00:00

    I've already reverted the one system where I tested this. It *is* a serious readability issue. A font like Courier New becomes almost unreadable which makes editing a pain. Sans-serif fonts are less affected if not displayed too big or bold. But it seems all TT fonts are affected more or less. The bigger the font gets displayed or the bolder the more obvious. For instance, the text in this editor doesn't show much difference, but the bolded titles of threads in the thread list look like some mice nibbled on them. Switching off ClearType or FontSmoothing doesn't fix it.

    So, it's a serious readability issue and should be corrected within a senseful timeframe, but it's not making the system unusable (at least not in the short run). Especially, keeping in mind that you can easily uninstall the update until, hopefully, a fix for the bad rendering is incorporated.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-12T15:32:55+00:00

    Nothing was "censored". You kept attacking me personally without any reason. That's why I reported them for abuse.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-12T15:27:53+00:00

    To confirm, you are using 2003/Vista or Server 2008?  As that's the only platforms it should have this issue.

    Microsoft has released the patch to these platforms and won't be pulling it back.  They are still investigating the issue., but they have clearly documented they know about it and deem the problem not bad enough to not release it.

    If you are on another platform, holler.

    No, you're right, I am on Vista SP2.

    You are one up on me, though. In my post censored yesterday, I made reference to the fact that anyone I was put through to in technical support maintained they knew nothing about this patch's problem. Furthermore, telephone calls to Microsoft UK this afternoon have elicited the same response - there is no known problem with KB3013455.

    I have put through a complaint to Microsoft about its supplying a patch with a known fault, and about the attitude and censorship on answers.microsoft.com.

    Nonetheless, many thanks for your news which is, unless I have misunderstood it, Microsoft intends doing nothing to correct the error.

    Was this answer helpful?

    0 comments