WMI does not clear event registrations when the corresponding sink becomes invalid in Windows Server 2003

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • An event consumer uses Windows Management Instrumentation (WMI). WMI provides asynchronous delivery of events.
  • The event consumer registers an IWbemObjectSink interface with WMI. The event consumer does this to receive DCOM callbacks that contain these events.
  • The event consumer uses the same IWbemObjectSink interface for many such event registrations.
In this scenario, the consumer's DCOM connection may be lost because of network issues or because the event consumer stops responding (hangs). If the consumer's DCOM connection is lost, each event registration remains active inside WMI. Therefore, WMI consumes resources for each registration that is associated to the IWbemObjectSink interface. WMI consumes these resources until a failed delivery attempt occurs for each registration.
This problem occurs if an event consumer loses connectivity with WMI. This problem also occurs if a WMI client loses DCOM communication with WMI because of network problems.

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.


The computer must be running Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) to install this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 sizeDateTimePlatformSP requirementService branch
Updspapi.dll6.3.4.1379,18401-Mar-200706:10x86NoneNot Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about the standard terminology that is used to describe Microsoft software updates, 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: 931320 - Last Review: 12/09/2015 09:20:46 - Revision: 3.0

  • kbnosurvey kbarchive kbautohotfix kbqfe kbHotfixServer kbfix kbbug kbwinserv2003presp2fix kbexpertiseadvanced KB931320