This hotfix rollup is available for the following operating systems:
- Windows XP Service Pack 3 (SP3)
- Windows Vista Service Pack 2 (SP2)
- Windows Server 2003 SP2
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 SP2
- Windows Server 2008 R2 SP1
Hotfix InformationA 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.
PrerequisitesTo apply this hotfix, you must have the .NET Framework 4 installed.
Restart requirementYou 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 informationThis hotfix package does not replace a previously released hotfix package.
Issues that this hotfix rollup resolves
Issue 1DirectorySearcher.FindOne() may throw overflow exceptions when it runs as a 32-bit process that is linked with the LARGEADDRESSAWARE compiler flag and runs on a 64-bit operating system that is configured to use 3 gigabytes (GB) of memory. Applications hosted inside IIS may see this exception when w3wp.exe is compiled as a LARGEADDRESSAWARE application.
This fix makes sure that memory addresses greater than 2 GB are handled correctly.
Issue 2Copying formatted text from a long XPS document can take several minutes, depending on the position of the text within the document, and can cause the application to freeze.
This issue occurs because some formatting declarations require scanning the document from the beginning up to the desired selection. These declarations are rare (they come from custom elements that have a TextElementEditingBehaviorAttribute that is not marked IsTypographicOnly).
The logic has been changed in this hotfix to avoid the expensive scan when no such declarations appear in the desired selection.
Issue 3When a third-party application queries .NET performance counters either concurrently or multiple times within a few milliseconds, a divide-by-zero error may occur based on the last time performance counters were queried.
Article ID: 2908370 - Last Review: 28 Jul 2014 - Revision: 1