.NET Framework 2.0: A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application

SUPPORT SOLUTION:
You have a Microsoft .NET Framework 2.0-based Multi-AppDomain application. When you run the application, an infinite loop occurs in the common language runtime (CLR) worker threads. Then, the application stops responding. Additionally, the memory usage of the operating system increases significantly.Note This symptom occurs for various reasons. The hotfix in this article only resolves this problem for the cause described in the “Cause” section..This problem occurs because an application domain cannot unload successfully. The CLR does not report this failure to the thread pool where the worker threads are running. Therefore, the thread pool waits indefinitely for the result of the unload operation instead of handling work that is queued by the application domain. Note Typically, an application domain cannot unload successfully because of a time out..Hotfix information
2, ‘resolution’);
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.To resolve this problem immediately, 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 Web site:http://support.microsoft.com/contactus/?ws=support
(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.Prerequisites
3, ‘resolution’);
You must have the .NET Framework 2.0 Service Pack 2 (SP2) or the .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix. Restart requirement
3, ‘resolution’);

You do not have to restart the computer after you apply the hotfix if the files that the hotfix affects are not being used.Hotfix replacement information
3, ‘resolution’);

This hotfix does not replace any other hotfixes.File information
3, ‘resolution’);

The English 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 2000, of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.4431989,01625-Jan-201004:32×86Mscorlib.dll2.0.50727.44314,550,65625-Jan-201004:32×86Mscorwks.dll2.0.50727.44315,819,21625-Jan-201004:32×86Sos.dll2.0.50727.4431388,93625-Jan-201004:32×86For all supported x64-based versions of Windows Server 2000, of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.44311,758,55224-Jan-201022:55×64Mscorlib.dll2.0.50727.44314,567,04024-Jan-201022:50×64Mscorwks.dll2.0.50727.443110,061,64824-Jan-201022:54×64Sos.dll2.0.50727.4431485,19224-Jan-201022:52×64For all supported IA-64-based versions of Windows Server 2000, of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.44313,085,14424-Jan-201023:47IA-64Mscorlib.dll2.0.50727.44314,009,98424-Jan-201023:45IA-64Mscorwks.dll2.0.50727.443120,174,67224-Jan-201023:41IA-64Sos.dll2.0.50727.4431872,77624-Jan-201023:44IA-64For all supported x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.4434989,01610-Feb-201015:22Mscorwks.dll2.0.50727.44345,819,21610-Feb-201015:22For all supported x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.44341,758,55210-Feb-201015:23Mscorwks.dll2.0.50727.443410,061,64810-Feb-201015:23For all supported IA-64-based versions of Windows Server 2008 SP2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.44343,085,14410-Feb-201015:22Mscorwks.dll2.0.50727.443420,174,67210-Feb-201015:22For all supported x86-based versions of Windows 7
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.5005995,67210-Feb-201023:25Mscorwks.dll2.0.50727.50055,822,28810-Feb-201023:25For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.50051,757,52810-Feb-201023:24Mscorwks.dll2.0.50727.500510,052,43210-Feb-201023:24For all supported IA-64-based versions of Windows Server 2008 R2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimeMscordacwks.dll2.0.50727.50053,086,16810-Feb-201023:23Mscorwks.dll2.0.50727.500520,186,44810-Feb-201023:23

If this hotfix is not posted for public download (meaning a public URL for this hotfix is not provided in this article), distribution requires technical lead, escalation team member, or manager approval and the following information applies:To receive the hotfix, customers must be experiencing the bug that is mentioned in the “Symptoms” section. You must track the customers you send this to and supply them with the next service pack when it becomes available (if a service pack is released).

This hotfix is scheduled to be included with Windows Vista Service Pack 3 (SP3), and with Windows 7 Service Pack 1 (SP1)..Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section..

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

.

For File Repair and Data Recovery, visit File Repair / Data Recovery