This article describes hotfix rollup kb3078646 that is available for the Microsoft .NET Framework 4.5.2, the .NET Framework 4.5.1, and the .NET Framework 4.5. For more information about the issues that the hotfix rollup resolves, see the "Issues that this hotfix rollup resolves" section.
The offline package can be used in situations where the web installer cannot be used because of lack of Internet connectivity. Wherever possible, we recommend that you use the Web Installer instead of the offline package for optimal efficiency and bandwidth requirements.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Note To verify the hotfix update version, check the value of the Release keyword to determine the installed version. To be forward-compatible, you can check for a value greater than or equal to the value listed in the table:
Hotfix Rollup Version
Value of the Release DWORD
Hotfix rollup KB3078646 for the .NET Framework 4.5 and later versions of .NET Framework
For more information about how to detect for the .NET Framework versions, see How to: Determine Which .NET Framework Versions Are Installed.
To apply this hotfix, you must have the .NET Framework 4.5.2, the .NET Framework 4.5.1, or the .NET Framework 4.5 installed.
You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.
Hotfix replacement information
This hotfix package does not replace a previously released hotfix package.
Issues that this hotfix rollup resolves
Assume that you have a Windows Presentation Foundation (WPF) application that creates an XPS file, and this XPS file has an embedded font that is missing some special characters. Assume then that you have another WPF application that prints this XPS file. In this situation, the missing characters may result in the document being printed in an incorrect font.
After you apply this update, WPF now includes the missing characters when you create a new XPS file if the font supports them.
Note This issue still occurs when you use the WPF application to print an old XPS file.
Assume that you run a touch-enabled WPF application on a computer that is running Windows 8 or a later version of Windows. You remove a tablet device from the computer while the device is being used, the WPF application crashes or you lose the touch promotion to mouse operations. This means clicking buttons may not work correctly and some touch specific actions could be broken.
WPF no longer immediately removes a tablet device when it is removed from the system. Instead, it delays this process until it can guarantee that there is no further pending input to be processed for the device. At that point, the device will be removed safely and normal touch operation will continue.