Introduction

This article describes hotfix rollup 2862068 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 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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of Windows Server 2008 SP2 and Windows Vista SP2

File name

File version

File size

Date

Time

system.management.dll

2.0.50727.7038

385,024

24-Jul-2013

23:00

mscorlib.dll

2.0.50727.7038

4,554,752

24-Jul-2013

23:00

aspnet_wp.exe

2.0.50727.7038

31,384

24-Jul-2013

22:59

mscordacwks.dll

2.0.50727.7038

990,360

24-Jul-2013

22:59

mscorwks.dll

2.0.50727.7038

5,941,400

24-Jul-2013

23:00

sos.dll

2.0.50727.7038

389,768

24-Jul-2013

23:00

webengine.dll

2.0.50727.7038

437,400

24-Jul-2013

23:00

wminet_utils.dll

2.0.50727.7038

32,928

24-Jul-2013

23:00

system.web.dll

2.0.50727.7038

5,283,840

24-Jul-2013

23:00

For all supported x64-based versions of Windows Server 2008 SP2 and Windows Vista SP2

File name

File version

File size

Date

Time

mscorlib.dll

2.0.50727.7038

4,571,136

24-Jul-2013

22:58

aspnet_wp.exe

2.0.50727.7038

43,160

24-Jul-2013

22:57

mscordacwks.dll

2.0.50727.7038

1,757,336

24-Jul-2013

22:58

mscorwks.dll

2.0.50727.7038

10,004,632

24-Jul-2013

22:58

sos.dll

2.0.50727.7038

486,024

24-Jul-2013

22:58

system.management.dll

2.0.50727.7038

385,024

24-Jul-2013

22:58

webengine.dll

2.0.50727.7038

746,648

24-Jul-2013

22:58

wminet_utils.dll

2.0.50727.7038

43,168

24-Jul-2013

22:58

system.web.dll

2.0.50727.7038

5,292,032

24-Jul-2013

22:58

system.management.dll

2.0.50727.7038

385,024

24-Jul-2013

23:00

mscorlib.dll

2.0.50727.7038

4,554,752

24-Jul-2013

23:00

aspnet_wp.exe

2.0.50727.7038

31,384

24-Jul-2013

22:59

mscordacwks.dll

2.0.50727.7038

990,360

24-Jul-2013

22:59

mscorwks.dll

2.0.50727.7038

5,941,400

24-Jul-2013

23:00

sos.dll

2.0.50727.7038

389,768

24-Jul-2013

23:00

webengine.dll

2.0.50727.7038

437,400

24-Jul-2013

23:00

wminet_utils.dll

2.0.50727.7038

32,928

24-Jul-2013

23:00

system.web.dll

2.0.50727.7038

5,283,840

24-Jul-2013

23:00

For all supported IA64-based versions of Windows Server 2008 SP2 and Windows Vista SP2

File name

File version

File size

Date

Time

mscorlib.dll

2.0.50727.7038

4,014,080

24-Jul-2013

22:50

aspnet_wp.exe

2.0.50727.7038

83,096

24-Jul-2013

22:50

mscordacwks.dll

2.0.50727.7038

3,083,416

24-Jul-2013

22:50

mscorwks.dll

2.0.50727.7038

20,391,576

24-Jul-2013

22:50

sos.dll

2.0.50727.7038

873,608

24-Jul-2013

22:50

system.management.dll

2.0.50727.7038

385,024

24-Jul-2013

22:50

webengine.dll

2.0.50727.7038

1,233,048

24-Jul-2013

22:50

wminet_utils.dll

2.0.50727.7038

80,544

24-Jul-2013

22:50

system.web.dll

2.0.50727.7038

4,812,800

24-Jul-2013

22:50

system.management.dll

2.0.50727.7038

385,024

24-Jul-2013

23:00

mscorlib.dll

2.0.50727.7038

4,554,752

24-Jul-2013

23:00

aspnet_wp.exe

2.0.50727.7038

31,384

24-Jul-2013

22:59

mscordacwks.dll

2.0.50727.7038

990,360

24-Jul-2013

22:59

mscorwks.dll

2.0.50727.7038

5,941,400

24-Jul-2013

23:00

sos.dll

2.0.50727.7038

389,768

24-Jul-2013

23:00

webengine.dll

2.0.50727.7038

437,400

24-Jul-2013

23:00

wminet_utils.dll

2.0.50727.7038

32,928

24-Jul-2013

23:00

system.web.dll

2.0.50727.7038

5,283,840

24-Jul-2013

23:00

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) issuesWhen 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 issuesAssume 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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×