Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows7SP1 Fonts problem after installing Update for Microsoft .NET Framework 4.7.1 (KB4055002) #9528

Closed
pavrosa opened this issue Jan 10, 2018 · 4 comments

Comments

@pavrosa
Copy link

pavrosa commented Jan 10, 2018

After installing the update we are experiencing problems accessing System.Windows.Media.Fonts type:

class Program
{
    static void Main(string[] args)
    {
        try
        {
            var cnt = Fonts.SystemFontFamilies.Count;

            Console.WriteLine("ok");                
        }
        catch (Exception e)
        {
            Console.WriteLine(e); 
        }
        Console.ReadLine();
    }
}

Uninstall of the update solves the problem.

@0xd4d
Copy link

0xd4d commented Jan 10, 2018

This is a bug in the update. The update removed Windows 7 SP1 support and it only supports Windows 8.1 and later.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\Fonts\GlobalUserInterface.COMPOSITEFONT has been modified. Old one is 182KB, new one is 115KB. What changed? They removed WindowsXPSP2 support and replaced it with Windows8Point1 support (i.e., there's no Windows7SP1 support anymore).

It's pretty clear that this Windows 7 SP1 update has NOT been tested on Windows 7 SP1.

@billwert
Copy link
Member

Hi,
Thanks for the report. We're currently investigating and will have an update soon.

@daykun
Copy link

daykun commented Jan 12, 2018

From what I have seen, this issue can be remediated by using the old C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\Fonts\GlobalUserInterface.COMPOSITEFONT and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\Fonts\GlobalUserInterface.COMPOSITEFONT from before the update.

Alternatively, a complete uninstall of KB4055002 will also work as the file has been changed by this update. Install KB4054183 instead.

Even Visual Studio 2010 will crash because of this bug if you start a WPF-Application (newer versions don't seem directly affected)

@RussKeldorph
Copy link
Contributor

Please refer to dotnet/announcements#53 and/or microsoft/dotnet#599 for more information.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants