Article ID: 2862064 - View products that this article applies to.
Expand all | Collapse all

On This Page

Introduction

This article describes hotfix rollup 2862064 that is available for the Microsoft .NET Framework 4.5. This hotfix rollup fixes several issues in the .NET Framework 4.5. 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 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:
http://support.microsoft.com/contactus/?ws=support
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.

File information

Collapse this imageExpand this image
assets folding start collapsed
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 the .NET Framework 4.5 in Windows 8

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
system.management.dll4.0.30319.19117405,08829-Jul-201322:12
mscorlib.dll4.0.30319.191175,173,32829-Jul-201322:12
clr.dll4.0.30319.191176,882,87229-Jul-201322:12
mscordacwks.dll4.0.30319.191171,299,54429-Jul-201322:12
mscordbi.dll4.0.30319.191171,096,78429-Jul-201322:12
sos.dll4.0.30319.19117747,06429-Jul-201322:12
wminet_utils.dll4.0.30319.1911742,08029-Jul-201322:12

For all supported x64-based versions of the .NET Framework 4.5 in Windows 8 and Windows Server 2012

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
mscorlib.dll4.0.30319.191175,122,12829-Jul-201322:13
clr.dll4.0.30319.191179,813,04829-Jul-201322:13
mscordacwks.dll4.0.30319.191171,742,93629-Jul-201322:13
mscordbi.dll4.0.30319.191171,497,16829-Jul-201322:13
sos.dll4.0.30319.19117785,46429-Jul-201322:13
system.management.dll4.0.30319.19117405,08829-Jul-201322:13
wminet_utils.dll4.0.30319.1911747,71229-Jul-201322:13
system.management.dll4.0.30319.19117405,08829-Jul-201322:12
mscorlib.dll4.0.30319.191175,173,32829-Jul-201322:12
clr.dll4.0.30319.191176,882,87229-Jul-201322:12
mscordacwks.dll4.0.30319.191171,299,54429-Jul-201322:12
mscordbi.dll4.0.30319.191171,096,78429-Jul-201322:12
sos.dll4.0.30319.19117747,06429-Jul-201322:12
wminet_utils.dll4.0.30319.1911742,08029-Jul-201322:12

Issues that this hotfix rollup resolves

Common language runtime (CLR) issues

Issue 1

When you press F5 to debug an application in Microsoft Visual Studio, Visual Studio crashes during the period after the application is compiled, but before it starts. 

Issue 2

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

Issue 3

When an application creates lots of threads for parallel processing, each thread may experience a leak of approximately 100 bytes.

Issue 4

When a computer has high workloads and low memory, Garbage Collector will compact the heap to recover memory. In certain cases, Garbage Collector will perform back-to-back garbage collection for applications. This behavior may cause the applications to be unresponsive.

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.

Properties

Article ID: 2862064 - Last Review: August 15, 2013 - Revision: 2.0
Applies to
  • Microsoft .NET Framework 4.5
Keywords: 
kbqfe kbexpertiseadvanced kbfix kbhotfixserver kbsurveynew KB2862064

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com