Hotfix rollup 3088944 for the .NET Framework 3.0 SP2 on Windows Server 2008 R2 SP1 and Windows 7 SP1

This article describes the hotfix rollup 3088944 that's available for the Microsoft .NET Framework 3.0 Service Pack 2 (SP2). For more information about the issues that the hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.

Resolution
A supported hotfix is now available from Microsoft. However, it's intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To fix this problem, contact Microsoft Customer Support Services to get the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note 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 fix your problem. The usual support costs will apply to additional support questions and issues that don't qualify for the specific update in question.
More information

Prerequisites

To apply this hotfix, you must have the .NET Framework 3.0 SP2 installed.

Restart requirement

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 doesn't replace a previously released hotfix package.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows
FilenameFileversionFilesizeDateTime
presentationframework.dll3.0.6920.86875,283,84021-Aug-201517:21
reachframework.dll3.0.6920.8687532,48021-Aug-201517:21
windowsbase.dll3.0.6920.86871,253,37621-Aug-201517:21
presentationcore.dll3.0.6920.86874,227,07221-Aug-201517:21
presentationfontcache.exe.config16103-Jun-201520:15
wpfgfx_v0300.dll3.0.6920.86871,737,88821-Aug-201517:21
system.printing.dll3.0.6920.8687372,73621-Aug-201517:21
penimc.dll3.0.6920.868768,75221-Aug-201517:21
presentationframework.dll3.0.6920.86875,283,84021-Aug-201517:21
presentationhostdll.dll3.0.6920.8687132,68021-Aug-201517:21
reachframework.dll3.0.6920.8687532,48021-Aug-201517:21
windowsbase.dll3.0.6920.86871,253,37621-Aug-201517:21
For all supported x64-based versions of Windows
FilenameFileversionFilesizeDateTime
presentationcore.dll3.0.6920.86874,009,98421-Aug-201517:21
presentationfontcache.exe.config16103-Jun-201520:16
wpfgfx_v0300.dll3.0.6920.86872,257,46421-Aug-201517:22
system.printing.dll3.0.6920.8687358,40021-Aug-201517:22
penimc.dll3.0.6920.868787,08821-Aug-201517:22
presentationframework.dll3.0.6920.86874,640,76821-Aug-201517:21
presentationhostdll.dll3.0.6920.8687173,64021-Aug-201517:22
reachframework.dll3.0.6920.8687532,48021-Aug-201517:22
windowsbase.dll3.0.6920.86871,114,11221-Aug-201517:22
presentationframework.dll3.0.6920.86875,283,84021-Aug-201517:21
reachframework.dll3.0.6920.8687532,48021-Aug-201517:21
windowsbase.dll3.0.6920.86871,253,37621-Aug-201517:21
presentationcore.dll3.0.6920.86874,227,07221-Aug-201517:21
presentationfontcache.exe.config16103-Jun-201520:15
wpfgfx_v0300.dll3.0.6920.86871,737,88821-Aug-201517:21
system.printing.dll3.0.6920.8687372,73621-Aug-201517:21
penimc.dll3.0.6920.868768,75221-Aug-201517:21
presentationframework.dll3.0.6920.86875,283,84021-Aug-201517:21
presentationhostdll.dll3.0.6920.8687132,68021-Aug-201517:21
reachframework.dll3.0.6920.8687532,48021-Aug-201517:21
windowsbase.dll3.0.6920.86871,253,37621-Aug-201517:21

Issue that this hotfix rollup fixes

This hotfix rollup fixes an issue with touch-enabled Windows Presentation Foundations (WPF) applications that are running in the same process but targeting two different .NET Framework versions. An example of this issue is two VSTO Office Add-ins written in WPF but targeted to different side-by-side .NET Frameworks. Users in this scenario could see strange touch behavior and/or crashes at various points during program execution.

The fix makes sure that proper DLLs are loaded and accessed in these scenarios, stopping any issues with touch behavior or program crashes.

Note If you use the .NET Framework 4.0 or the .NET Framework 4.5.2 on your computer, install the corresponding fix for your version to fix this issue.

Known issues

A fix that was previously released for touch-enabled VSTO add-ins in WPF was found to have a regression in scenarios in which partial-trust applications are used on touch-enabled devices. In these scenarios, customers see an application crash and cannot load a partial trust application. Therefore, the fix for touch-enabled VSTO add-ins has been removed.
Properties

Article ID: 3088944 - Last Review: 10/29/2015 00:47:00 - Revision: 4.0

Microsoft .NET Framework 3.0 Service Pack 2

  • kbqfe kbfix kbexpertiseadvanced kbsurveynew KB3088944
Feedback