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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2015-02-12T18:31:18+00:00

    And yet they "forgot" to mention it impacts Server 2008, XP, WEPOS, POSREADY2009, etc.

    I'm sure it wasnt due to utterly indequate/lack of testing or a recent history of the same with other patches, especially other patches involving the kernel (Win32k.sys specifically)

    No, they simply "forgot" to mention it in the "known issues" and..have "forgotten" to update the article since then, even after being made aware of the "additional impact".

    Rationalizing and minimizing utter incompetence doesn't serve anyone.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-12T18:33:57+00:00

    Well, XP SP3 is already no longer supported, and part of the reason I think it is to reduce testing costs.

    XP/FLP is still supported in the paid support program as well as via its additional distribution flavors of WEPOS/POSReady2009 (they are repacked versions of XP).

    Might want to update your own "knowledge base".

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-12T18:38:31+00:00

    Just be aware that given that it's documented in the bulletin as having this issue, Microsoft found this in their testing.  It was released with this issue.

    "Strangely" they forgot to mention ALL of the Windows versions it impacts, such as Server 2008, XP, FLP, WEPOS, POsReady2009, etc.

    I'm sure it wasn't for lack of testing.

    And I'm sure the lack of updating the bulletin/article to reflect the total OS impact as known to them isn't as well.

    Was this answer helpful?

    0 comments