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:40:11+00:00

    I'm checking, no eta at this time.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-12T18:43:38+00:00

    The reason for distributing this patch should be obvious after reading my last post or the bulletin. You did read the bulletin, yes?

    I agree that it's a big nuisance if those fonts are affected.

     Have they modified the support article/bulletin to reflect all of the Windows version affected?

    Are they warning end users about the known negative impact installing this patch will have on their systems either before installation or during installation?

    Right.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-12T18:45:08+00:00

    The security update does not fix ClearType vulnerabilities. It fixes two vulnerabilities concerning TrueType fonts. That's why it affects only TrueType fonts and all ways to display them.

    It fixes three other vulnerabilities not connected to fonts.

    But all five are connected to the kernel-mode driver (= one file). That's why they were released in one update package.

    So. As I understand its a quite important update. when are you gonna do the update for fixing this mess? I want to write code with my code editor,and design usin some fonts, and specially, read. but still I cant cause I cant read.

    Thanx in advance

    Was this answer helpful?

    0 comments