[German]During the last days, Microsoft has released several updates to fix issues in the. NET Framework (Fixit tool for TypeInitializationException or FileFormatException errors in WPF applications) and in Windows 8.1 (Blue Screens). Here is an overview of what you might want to know. Addendum: I've added the description of the (still undocumented) update KB4056446 (Windows Server 2008). And there is an update KB4056254 for Windows 10.
Advertising
Update KB4077561 for Windows 8.1/Server 2012 R2
Microsoft has released Update KB4077561 for Windows 8.1Windows Server 2012 R2 Standard on January 25, 2018. The title is: Stop errors caused by spurious interrupt on systems PIC and APIC interrupt controllers. The kb article says:
Microsoft has received reports of some customers on systems running with programmable and advanced programmable interrupt controllers getting stop errors …
Searching the Internet, you will find this Symantec article about the stop code (Blue Screen) MEMORY_MANAGEMENT (0x1a) resulting from installing some January updates. Also Microsoft has extended the description of several kb articles (e.g. KB4056898) with the following issue description.
After installing this update, some systems running both PIC and APIC interrupt controllers may experience system crashes.
This issue is resolved in KB4077561.
The issue is caused from the following updates from 2018.
- January 3, 2018 – KB4056898 (Security-Only Update)
- January 8, 2018 – KB4056895 (Monthly Update)
- January 10, 2018 – KB4073576
- January 17, 2018 – KB4057401 (Preview of Monthly Rollup)
Update KB4077561 is available via Microsoft Update Catalog only. Woody Leonhard mentioned that update here, and also a German blog reader pointed me to that topic.
Update KB4074906 .NET Framework 4.7.1
German blog reader Teletom informed me also via e-mail, that Microsoft has released update KB4074906 .NET Framework 4.7.1 on January 24, 2018. The release of update KB4074906 was necessary due to the. NET Framework January 2018 rollup (.NET Framework January 2018 Security and Quality Rollup (KB 4055002)). This update is causing TypeInitializationException– or FileFormatException errors in WPF applications.
Advertising
See also my blog post Update KB4055002: Font issues with (WPF) applications for Windows 7 SP1 and Windows Server 2008 R2.
The problem occurs under Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 if the following products are installed:
According to this Github post, the .NET team has fixed the issue and re-released the monthly Rollup from January 2018 for affected Windows versions as KB4074880 (.NET Framework 4.6, 4.6.1, 4.6.2, 4.7 und 4.7.1 for Windows 7 SP1 und Windows Server 2008 R2 SP1).
Fixit-Tool KB4074906
On machines affected by the error, the Fixit Tool for KB4074906 should be run. The "Update for Microsoft. NET Framework 4.7.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4074906)" is available as an optional update via Windows Update, WSUS and Microsoft Update-Katalog Catalog. In the support article here you can also find information on how to obtain the tool under WSUS.
However, the update is only available for systems with the symptoms described in this article.
The Fixit tool replaces the broken font file with the correct version. To run the FixIt tool manually, you must close all. NET applications and initiate the update from an administrative command prompt. Details can be found here.
Update KB4056446 for Windows Server 2008
I've beein informed (see the German comment that Microsoft has released another update KB4056446 for Windows Server 2008 (and probably also valid for Windows Vista).
Update KB4056446 for Windows Server 2008 has been released at January 17, 2018. It seems to be offered via Windows Update, in WSUS and may be available for download via Microsoft Update Catalog. The description in Microsoft Update Catalog is Microsoft like:
Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
More information: http://support.microsoft.com/kb/4056446
The kb articles referenced above still doesn't exists, so some speculations about this update spread the internet (see here (broken) for instance). I've downloaded and inspected the update package. This package updates the Windows SmartCardSubsystemClient (the file WinSCard.dll in system32) to version 6.0.6002.24262. This is also confirmed here and here. But I can't say, what they fix exactly. Hope this help.
Update KB4056254 for Windows 10
Addendum: On January 23./24. 2018 Microsoft releaded Update KB4056254 for Windows 10 Version 1507 (RTM) and later build. The description is a bit cryptically:
This update includes a background service for update facilitation in Windows 10 Version 1507 and later versions (build 10240 and later builds).
This update is deployed only to certain builds of Windows 10. Devices that are running those builds will automatically get this update downloaded and installed.
Update KB4078130 f0r Windows
Microsoft has released on January 27, 2018 Update KB4078130 (Update to Disable Mitigation against Spectre, Variant 2) for . Microsoft wrote:
'Intel has reported issues with recently released microcode meant to address Spectre variant 2 (CVE 2017-5715 Branch Target Injection) – specifically Intel noted that this microcode can cause "higher than expected reboots and other unpredictable system behavior" and then noted that situations like this may result in "data loss or corruption." Our own experience is that system instability can in some circumstances cause data loss or corruption.
While Intel tests, updates and deploys new microcode, we are making available an out of band update today, KB4078130, that specifically disables only the mitigation against CVE-2017-5715 – "Branch target injection vulnerability." In our testing this update has been found to prevent the behavior described.
The patch is available from the Update Catalog for all Windows versions. It does set the registry values documented here to disable CVE 2017-5715 mitigation in Windows.
Similar articles
Update KB4055002: Font issues with (WPF) applications
(Preview-)Updates for Windows, Defender, NET (January 2018)
