Hotfix rollup 2862069 is available for the .NET Framework 2.0 SP2 on Windows 8 or Windows Server 2012

Applies to: Windows 8Windows Server 2012 StandardWindows Server 2012 Standard


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

This hotfix rollup is available for the following operating systems:
  • Windows 8
  • Windows Server 2012

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

Common language runtime (CLR) issues

When you run Microsoft SQL Server workloads that use large amounts of memory, out-of-memory errors occur even if sufficient memory is available.

Windows Management Instrumentation (WMI) issues

When an application uses the System.Management namespace to connect to a remote computer, a memory leak may occur. This issue occurs if the following conditions are true:
  • The application enters credentials for the remote computer by using the ConnectionOption parameter.
  • The application uses the ConnectionOption parameter as a part of the ManagementScope parameter to connect to the remote computer.
  • The ManagementScope parameter is used to perform operations.

ASP.NET issues

Assume that a validator control is defined inside a naming container. When you use the SetFocusOnError ASP.NET validation property, the focus is not set to a control that is in the container. This issue occurs even when a control fails the validation process.

Note After you install this hotfix rollup and the controls that inside the container fails the validation process, the focus is set to the first control that has failed validation.