This hotfix rollup is available for the following operating systems:
- Windows XP Service Pack 3 (SP3)
- Windows Server 2003 Service Pack 2 (SP2)
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 2.0 SP2 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 1:ASP.NET applications that access additional functionality by using the application configuration settings can experience a deadlock at startup.
Issue 2:The .NET Framework 2.0 and 3.5 applications will throw a NullReferenceException exception when they use GetEnvironmentVariable if the registry key does not exist.
Issue 3:DirectorySearcher.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 larger than 2 GB are handled correctly.
Issue 4:When an update is being installed, Fusion can access a state in which NGEN is called repeatedly. This causes entries in the following registry keys keep growing until the computer freezes:
Article ID: 2908372 - Last Review: 28 Jul 2014 - Revision: 1