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-17T13:31:34+00:00

    I am one of those affected and cannot seem to right the ship - the update has been uninstalled; I even rolled my restore point back to Dec. 7 with no luck. I;m a weekly newspaper layout artist here that can't see our headlines, and I'm not sure how to implement your code. MS - faster, faster!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-12-17T07:18:43+00:00

    6 days and still nothing?

    People all over the World is affected by this problem, so it really should not take MS 3 days to acknowledge that there is a problem and another 4 days with no fix!

    If we had done this to our customers, they would surely find another place to place the purchases..

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-12-16T05:04:31+00:00

    Yeah, this works as a work-around.

    Here is my code for it if anyone needs it now -- and incase they don't fix this next week:

    http://www.mouseindustries.com/fixKB2753842.html

    Thanks for the information.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-12-16T01:30:12+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.

    Thanks man... Will do that. This version is beta, so my customers will just expect it if something doesn't work correctly. Hopefully by production deadline this API will be fixed and I can pull it.

    Not a bad idea though -- Maybe more a kludge than a hack in this case :)

    Was this answer helpful?

    0 comments