BUG: Registry Event Provider Notification Fails with More Than 64 Concurrent Notification Requests (240099)


The information in this article applies to:

  • Microsoft Windows Management Instrumentation 1.0
  • Microsoft Windows Management Instrumentation 1.1
  • Microsoft Windows Management Instrumentation 1.5
This article was previously published under Q240099

SYMPTOMS

If an event consumer causes the registration of more than 64 concurrent notifications, all previous notifications are invalidated and will not receive their desired events.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Windows Management Instrumentation (WMI) clients can receive notification of changes in the registry by using the Registry Event Provider. Clients can register to receive an event notification when:
  • A value for a specific key changes.
  • A specific key itself changes.
  • One of the keys of the hierarchy of a certain key changes.
In order for a client to receive these event notifications, it must register itself as a consumer to the desired event. This is accomplished by executing a notification query which designates the desired key to be monitored. The query has the following form: 
Select * from RegistryTreeChangeEvent where Hive="HKEY_LOCAL_MACHINE" and RootPath="SOFTWARE"

REFERENCES

For additional information, see "Registry Provider" and "Event Notification" in the WMI SDK documentation or MSDN Library.
Modification Type:MinorLast Reviewed:3/20/2004
Keywords:kbDSWManage2003Swept kbBug kbWBEM100 KB240099
©2004 Microsoft Corporation. All rights reserved.