Hotfix rollup 3064706 for the .NET Framework 4 on Windows Vista SP2, Windows 7 SP1, Windows Server 2003 SP2, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2

This article describes hotfix rollup 3064706 that is available for the Microsoft .NET Framework 4. For more information about the issues that the hotfix rollup resolves, see the "Issues that this hotfix rollup resolves" section.


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: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 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.

More Information


To apply this hotfix, you must have the .NET Framework 4 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 does not replace a previously released hotfix package.

File information

Issues that this hotfix rollup resolves

Issue 1

When you insert a 4-byte character by using an Input Method Editor (IME) in a Windows Presentation Foundation (WPF) text box, a crash occurs.

When IME sends a 4-byte character (a character that is made up of two UTF-16 characters), it does this by using two WM_IME_CHAR messages. Each message contains half of the character. During a text insertion operations, WPF is positioned between the two surrogate characters. Because text operations are typically not performed in this position, an internal mechanism breaks out of the compound sequence early. This causes WPF to go out of bounds when it tries to position the caret.


Article ID: 3064706 - Last Review: Jun 24, 2015 - Revision: 1

Microsoft .NET Framework 4