A handle leak occurs after you install hotfix 925104 or Windows Server 2003 SP2 on a computer that is running Windows Server 2003

A handle leak occurs when an application runs on a computer that is running Microsoft Windows Server 2003. The handle count of the application continues to increase. Over time, this handle leak may exhaust system resources and cause performance issues.

This problem occurs if the following conditions are true:

• The application accesses the following registry subkey by calling the RegQueryValue function:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance
• Hotfix 925104 or Windows Server 2003 Service Pack 2 is installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  925104� The System log reports many "PerfOS event ID: 2001" errors when you use a Microsoft Windows Server 2003-based computer that has more than 32 processors

This problem occurs because the PerfOS.dll module does not correctly manage open registry handles.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces hotfix 925104.

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.

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

You can use Task Manager to check the handle count of a running application. To do this, follow these steps:

1. Right-click the task bar, and then click Task Manager.
2. Click the Processes tab.
3. On the View menu, click Select Columns.
4. Click to select the Handle Count check box, and then click OK.
5. On the Processes tab, check the values in the Handles column.

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: