Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
.NET Framework January 2018 Rollup Known Issue KB4074906 - "TypeInitializationException" or "FileFormatException" error in WPF applications #53
.NET Framework January 2018 Monthly Rollup Known Issue KB4074906 - "TypeInitializationException" or "FileFormatException" error in WPF applications
Updated: January 24, 2018
An issue has been found in the .NET Framework January 2018 Security and Quality Rollup (KB 4055002), applicable to .NET Framework 4.7.1 installed on either Windows 7 and Windows Server 2008 R2.
The .NET team has fixed the issue and re-released the January 2018 Monthly Rollup for affected Windows versions as KB 4074880. Affected machines can be fixed by using one of the solutions described later in the document.
This document describes the symptoms and solutions to resolve the issue.
The .NET Framework January 2018 Monthly Rollup Announcement blog post has been updated with this information.
Please share your thoughts on this change and see what others are saying at:
This issue applies to Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 machines. Users that install the following products/updates in the following order will experience this issue.
Windows Presentation Foundation (WPF) applications that request a fallback font or a character that is not included in the currently selected font return the following error messages:
To work around this problem, use one of the following methods. We recommend the first option. The other options are provided in the unlikely case that the first option doesn't work for you.
Solution 1 - Run Fixit tool for KB4074906
The tool replaces the corrupted font file with the correct version.
The easiest approach is to get the tool via Windows Update or WSUS. If you download and run the tool directly, please follow these instructions.
You can use the following commands to run the tool and determine the return code.
The follow table lists the error codes that the tool outputs:
Solution 2 - Uninstall and re-install the January 2018 Monthly Rollup
The January 2018 Monthly Rollup has been re-released with a fix for this known issue. You will have a working system if you uninstall the initial Monthly Rollup (KB 4055002) and instead install updated January 2018 Monthly Rollup (KB 4074880).
Follow these steps:
Solution 3 - Replace GlobalUserInterface.CompositeFont Manually
Manually replace corrupted font file with correct version.
The root cause of this problem is a MSI setup interaction between the .NET Framework January 2018 Rollup (KB4055002) and an already installed version of .NET Framework 4.7.1 product. The Rollup installer unexpectedly overwrites the 4.7.1 version of the GlobalUserInterface.CompositeFont file. This causes WPF operations that need this font file to fail.
All updates are extensively tested before they are provided to you. We are investigating the gap in our testing and will resolve that for our next release.