I have a 3rd party DLL. When I call regsvr32 /u on it it says it was successful but if I check the registry the information is still there. Any thoughts as to why this is happening? Regards, Shane
Hi Shane, > I have a 3rd party DLL. When I call regsvr32 /u on it it says it was > successful but if I check the registry the information is still there. > > Any thoughts as to why this is happening? As long as the DLL doesn't return an error from DllUnregisterServer, unregistration is considered successful. This really doesn't say anything about what the function did, unfortunately. If you're really curious as to what it's doing, you can always run regmon [1] while unregistering, to see if it attempts to remove anything whatsoever. [1] http://www.sysinternals.com/Utilities/Regmon.html -- Best Regards, Kim Grsman
regsvr32 -u does no more and no less then calls DLLUnregisterServer from the DLL that you passed as an argument. The developers of the DLL could have intentionally leave something in registry, or just forgot to remove something, or some operation inside this function could fail but the function never the less can return success completion code. "Shane" wrote in message news:MPG.1e4d47ab866ba3e79896a0@news.microsoft.com... >I have a 3rd party DLL. When I call regsvr32 /u on it it says it was > successful but if I check the registry the information is still there. > > Any thoughts as to why this is happening? > > Regards, > > Shane
