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-13T15:32:45+00:00

    Security update 3023562 (also related to MS15-010) also causes "text quality degradation".

    No, it sure doesn't. I'm sure that you are telling this in good faith, but you confuse something.

    This update does not cause this issue, do not remove it!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-13T15:27:40+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]

    I have uninstalled this update from my Windows Vista PC, but update search keeps prompting me to install it. Do you have any estimate when the font corruption problem will be fixed? Will it be fixed with a new release of KB3013455 or a new update number?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-13T15:11:28+00:00

    Please note: Security update 3023562 (also related to MS15-010) also causes "text quality degradation".

    This was incorrect - see B-Hörnchen und A-Hörnchen reply below!!!

    However, my comments concerning 3013455 below still stand.

    I am on Vista Home Premium SP2 with all other current updates applied.

    I have had to remove both this one and 3013455 as my HTML editor is unreadable with them on.  I spent several hours isolating which of the 10 updates issued on February 10 was causing the problem.

    Since this was a "known issue" with this security update, does this mean I must read the technical bulletins of all future MS updates to determine if there are known issues and decide whether to install or not?  So, auto-install should not be used?  I find it VERY irksome that Microsoft would knowingly issue a fix that breaks something else in the operating system.  If I did this type of change to my customers, I'd be fired.

    Isn't there a way that Microsoft could issue a warning where there are "known issues" with a fix to alert us to review before install?

    Was this answer helpful?

    0 comments