FIX: Sos.dll leaks memory when you use an external debugger tool to debug an application in the .NET Framework 2.0

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. You use an external debugger tool to debug an application in the Microsoft .NET Framework 2.0. For example, you use the WinDbg tool to debug an application in the .NET Framework 2.0. Then, you run debugger extension commands in the external debugger tool. In this scenario, the SOS Debugging Extension (Sos.dll) leaks memory.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft .NET Framework 2.0 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: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.


You must have the Microsoft .NET Framework 2.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes that are installed on the computer.

File information

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.
File nameFile versionFile sizeDateTime
Normidna.nlpNot Applicable59,34225-Jul-200620:28
Normnfc.nlpNot Applicable45,79425-Jul-200620:28
Normnfd.nlpNot Applicable39,28425-Jul-200620:28
Normnfkc.nlpNot Applicable66,38425-Jul-200620:28
Normnfkd.nlpNot Applicable60,29425-Jul-200620:28
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 923299 - Last Review: 12/09/2015 06:37:07 - Revision: 2.0

Microsoft .NET Framework 2.0

  • kbnosurvey kbarchive kbqfe KB923299