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 No comments
{count} votes
Answer accepted by question author
  1. 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

    3 people found this answer helpful.
    0 comments No comments
Answer accepted by question author
  1. 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.

    2 people found this answer helpful.
    0 comments No comments

300 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-02-10T22:14:38+00:00

    Since about Octoberish they have moved all the known issues to deep in the sub KB articles.  It used to be on the top of the bulletins, I wish they'd move it back, but unfortunately every time I've asked/pleaded to have them do it the way they used to they just come back and say "the info is still there"

    Well yeah but about 45 mouse clicks from where it used to be....

    So no apparently it's not possible to put that info in a spot that would be really nice and where it USED to be.

    {I do not work for Microsoft and wish they would put that info back in a more viewable place}

    0 comments No comments
  2. Anonymous
    2015-02-10T22:29:44+00:00

    Can you post up a screen shot please?

    It is [Courier New, Regular, 9] font, before and after the update

    0 comments No comments
  3. Anonymous
    2015-02-11T02:32:52+00:00

    AKA "Yet Another Broken Win32k.Sys Iteration"

    This also impacts Windows XP, FLP, WEPOS, and POS Ready 2009 (the last 2 are still supported by MS until 2019)

    Causes font display/smoothing/substitution corruption in IE/Chrome/Firefox/other apps.

    Do not install this update if you value smoothly rendered readable fonts.  Uninstall this update for the same.

    FYI, this is the 5th or 6th released iteration of Win32K.sys on XPSP3 based Windows as of the last 6-12 months that is plagued with obvious significant QA issues.

    Perhaps they need to move these Kernel patches to the "Optional" section (with a popup dialog box warning at install time) of Windows/Microsoft Update considering how problematic they have been.

    0 comments No comments