That's a tangled web you're dealing with! The 'proper' way to move the dll would be to move or copy it back to the ORIGINAL location (where it was first registered), the UNregister it from the command prompt, then move it back to the intended destination and register it again from there.

Te windows registration information is not a pretty place to be - and it's difficult and careful work to repair problems like this from the registry.

>When I release my app, I had all my files (including a dll) in the app's directory. As the app runs, it looks to see if the dll has been registered on the users machine. If it has not, then it registers and then instantiates what it needs.
>
>However, the system admin decided to move the app to a different folder. Now the registry shows that the dll is registered but the path of the dll in the registry is no longer valid ... the dll was moved with the app. So, when the app tries to instantiate the object, it crashes.
>
>What I'd like to do is compare the working path of the running app to the path listed in the registry. If they differ, I could unregister the dll and re-register it. Actually, maybe I could just replace the path value in the registry?
>
>Is there any easy way to get the registered path of the dll? In this case, the path is found in the Registry as:
>
>HKEY_CLASSES_ROOT\CLSID\{832E8CD7-F63C-47AB-8F73-7F41B0FD232E}\InprocServer32
>
>However, I can't seem to figure out how to get the default value from this registry path.
>
>Thanks so much for whatever help you can offer!
>
>Rodd