Article ID: 968760 - View products that this article applies to.
A managed application has a high number of thread handles and of event handles. This problem occurs if the application creates and releases many managed threads, but the application does not create sufficient memory pressure to trigger the garbage collector of the Microsoft .NET Framework 2.0 very frequently.
For example, this problem may occur in Microsoft System Center Operations Manager 2007 on a computer that is acting as a management server or as an agent. The affected processes may be the Monitoringhost.exe process or the HealthService.exe process.
This problem occurs because the event handle that is associated with managed threads is only released when the finalizer runs.
Note This hotfix changes the common language runtime (CLR) so that the CLR runs the finalizer when a managed thread completes.
Hotfix Replacement InformationThe hotfix that corresponds to KB968760 has been superseded with the hotfix KB981574, which contains all fixes that were previously included in KB968760. You should use the hotfix KB981574 to fix the issues described in KB968760. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/981574/ )The splash screen stays open longer than usual when you try to start Excel on a computer that has the .NET Framework 3.5 SP1 installed
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Handle v3.42, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/sysinternals/bb896655.aspxFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 968760 - Last Review: August 4, 2010 - Revision: 4.0