Type 1 font handling messed up by December 11, 2012 update KB2753842

Anonymous
2012-12-13T00:15:42+00:00

Programs like Quark Xpress and Coreldraw on Windows 7 and XP have their Type 1 font handling broken by this patch. Characters larger than 15 pt. become invisible. Uninstalling the patch removes the problem. We have 330 machines with this problem. Is Microsoft getting ready to release a fix for this?

Windows for home | Previous Windows versions | 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
2013-01-02T09:53:51+00:00

Hello all,

Please be informed, that MS12-078 now has been updated – you can read more about the update here: http://technet.microsoft.com/en-us/security/bulletin/ms12-078

Why was this bulletin rereleased on December 20, 2012? ****Microsoft rereleased this bulletin to address a known issue in the KB2753842 update related to OpenType Fonts (OTF) not properly rendering in applications after the original update was applied. Customers who have successfully installed the original KB2753842 update are protected from the vulnerability described in CVE-2012-2556. However, customers need to install the rereleased KB2753842 update to resolve the issue with improper OpenType font rendering and to keep the affected binaries up to date.

Was this answer helpful?

0 comments

62 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-12-21T20:35:15+00:00

    I have just installed the revised KB2753842. At first glance, it would appear to have solved the problem I had with MS Word after the original fix.

    I thought that too but when I went to one of the 454 files where this font was supposed to be there were letters there but they weren't the same font and I could not edit them!!!  That gives me more than 3300 "corrections" I have to make!!!!!!!!

    Is there something I can do to change this?  Do you think MS will do something in the next "update" to make my problem go away?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-12-20T18:46:54+00:00

    I have just installed the revised KB2753842. At first glance, it would appear to have solved the problem I had with MS Word after the original fix.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-12-20T01:01:43+00:00

    What is the workaround? (besides uninstalling the KB) I am an engineer who's software is affected by this and would like to know my options.

    Yes, there is a workaround.

    When GetGlyphOutline() returns 0, allocate a buffer of a fixed size and call it again on that buffer. It will now return how much BYTE was written in that buffer. Now do it again with a buffer of larger size : if the number of byte written is still the same, you know your buffer is now large enough.

    This is horrible and super hacky but it will work.

    Hope this help.

    Hope more people LIKE YOUR POST so the FIX becomes visible at the 1st page (top) of this thread!

    Thanks for posting and sharing your code (later post in this thread) so we have a temporary patch workaround to give time for MS to get their permanent fix out.

    With MS Word and Powerpoint affected, MS will have their fix out soon, but a week is too long for corporations affected across the world!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-12-18T23:56:41+00:00

    If this is not fixed, it will be Microsoft's admission that page layout and design is better accomplished on a Mac...not because of DP software quality under Windows, but because of problems with the OS itself.

    This was a very easy bug to fix on my 4 system SOHO (although removing a "security" patch is troublesome), but I sure wouldn't want to be responsible for the fix in a larger company like a bank or government office, where hundreds or thousands of systems might be effected.

    Was this answer helpful?

    0 comments