One solution would be to not show the updated tree until it has been fully populated. Another (faster) approach is to only show those nodes that are actually visible. In other words, don't show a node's contents until it has been expanded. "Love people and use things, not love things and use people." - Unknown "The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

Thanks, I suppose that I could use GetProcAddress for DllRegisterServer and DllUnregisterServer

benjymous wrote: You could use the windows search for files option to find *.exe and *.dll files that contain the name of the dll in question This is no better than using the depends tool. It does not take account of the possibility of programs loading dll's at runtime. The name of the dll may be built at runtime from user input or registry/ini settings for example. The opinions expressed in this communication do not necessarily represent those of the author (especially if you find them impolite, discourteous or inflammatory).