Hotfix rollup 2908376 is available for the .NET Framework 2.0 SP2 on Windows Server 2008 SP2 or Windows Vista SP2

Applies to: Microsoft .NET Framework 2.0 Service Pack 2Windows Server 2008 Service Pack 2Windows Vista Service Pack 2

To apply this hotfix rollup, go to the following knowledge base article and download the correct hotfix rollup:

2926992 Hotfix rollup 2926992 is available for the .NET Framework 2.0 SP2 on Windows Server 2008 SP2 or Windows Vista SP2

Introduction


This article describes hotfix rollup 2908376 that is available for the Microsoft .NET Framework 2.0 Service Pack 2 (SP2). For more information about the issues that the hotfix resolves, see the "More information" section.

This hotfix rollup is available for the following operating systems:
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Vista Service Pack 2 (SP2)

More Information


Hotfix Information

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.

Restart requirement

You must 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


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 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 it runs on an 64-bit operating system that is configured to use the 3 GB memory. Applications hosted inside IIS may see this exception as w3wp.exe is compiled as a LARGEADDRESSAWARE application.

This fix makes sure that memory addresses greater than 2 GB are handled correctly.

Issue 4:

When an update is being installed, Fusion can access a state where NGEN is called repeatedly. This causes entries in the following registry key keep to grow until the computer freezes:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\NativeImagesIndex