This article describes hotfix rollup 2862063 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.
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 4.5 installed on a computer that is running one of the operating systems:
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 R2 SP1
- Windows Server 2008 Service Pack 2 (SP2)
- Windows Vista SP2
Restart requirementYou 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 informationThis hotfix package does not replace a previously released hotfix package.
Issues that this hotfix rollup resolves
Common language runtime (CLR) issuesIssue 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.
When you run Microsoft SQL Server workloads that use large amounts of memory, out-of-memory errors occur even if sufficient memory is available.
When an application creates lots of threads for parallel processing, each thread may experience a leak of approximately 100 bytes.
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) 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.
Article ID: 2862063 - Last Review: Aug 15, 2013 - Revision: 1