When you use a custom program or a Microsoft Visual Basic script that uses Windows Management Instrumentation (WMI) to generate and monitor events, a memory leak condition may appear on the computer that is running the program or the script. You can use the Windows Task Manager to see the memory leak by monitoring the service host process (Svchost.exe) for Windows Management.
The memory leak condition will eventually cause system services to stop, will slow down server performance, and may result in access violation errors (0xC0000005).
This problem occurs because WMI does not release event objects after they are sent to semi-synchronous clients or to other WMI consumers.
When the event registration is synchronous or semi-synchronous, the events
are cached inside the WMI service. The memory that is used by the event object
is not released until the consumer is unregistered.
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 global version of this fix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name
25-Apr-2003 09:41 5.1.2600.1214 480,256 Wbemcore.dll
To work around this problem, use asynchronous API consumers instead of synchronous or semi-synchronous consumers in your custom script or program.
Although this is not an actual memory leak, this problem can result in the same symptoms
as a memory leak for semi-synchronous WMI consumers that
receive many events and that run for long periods of time.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.