narmi2
asked on
finding a registered dll?
hello
in windows 2000 if i use the following command
regsvr32.exe "some.dll"
how do i see where it is in the registryy?
thanks
in windows 2000 if i use the following command
regsvr32.exe "some.dll"
how do i see where it is in the registryy?
thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually both -u and /u work.
The thing is some of the entries that are added to the registry when you run regsvr32 are by CLSID and not by name, so you would need to know the CLSID and search for that too. To make things worse, some dlls have more than one CLSID.
Here's an example of what happened when I ran regsvr32 adsiedit.dll:
SetValue HKCR\CLSID\{1C5DACFA-16BA- 11D2-81D0- 0000F87A7A A3}\Inproc Server32\( Default) SUCCESS "C:\adsiedit.dll"
SetValue HKCR\CLSID\{E6F27C2A-16BA- 11D2-81D0- 0000F87A7A A3}\Inproc Server32\( Default) SUCCESS "C:\adsiedit.dll"
SetValue HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N ameString SUCCESS "ADSI Edit"
SetValue HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\A bout SUCCESS "{E6F27C2A-16BA-11D2-81D0- 0000F87A7A A3}"
SetValue HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeType SUCCESS "{D4F3374F-052F-11D2-97B0- 00A0C9A06D 2D}"
SetValue HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\P rovider SUCCESS "Microsoft Corporation"
SetValue HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\V ersion SUCCESS "5.00.2139.1"
SetValue HKLM\Software\Microsoft\MM C\NodeType s\{D4F3374 F-052F-11D 2-97B0-00A 0C9A06D2D} \(Default) SUCCESS "Root ADSI Edit Subtree"
SetValue HKLM\Software\Microsoft\MM C\NodeType s\{5C22520 3-CFF7-11D 2-8801-00C 04F72ED31} \(Default) SUCCESS "ADSI Edit Connection Node"
SetValue HKLM\Software\Microsoft\MM C\NodeType s\{8690ABB B-CFF7-11D 2-8801-00C 04F72ED31} \(Default) SUCCESS "ADSI Edit Container Node"
SetValue HKLM\Software\Microsoft\MM C\NodeType s\{70B9C15 1-CFF7-11D 2-8801-00C 04F72ED31} \(Default) SUCCESS "ADSI Edit Leaf Node"
SetValue HKLM\Software\Microsoft\MM C\NodeType s\{072B64B 7-CFF7-11D 2-8801-00C 04F72ED31} \(Default) SUCCESS "ADSI Edit Query Node"
And here's what happened when I ran regsvr32 -u adsiedit.dll:
DeleteKey HKCR\CLSID\{1C5DACFA-16BA- 11D2-81D0- 0000F87A7A A3}\Inproc Server32 SUCCESS Key: 0xE20F4130
DeleteKey HKCR\CLSID\{1C5DACFA-16BA- 11D2-81D0- 0000F87A7A A3} SUCCESS Key: 0xE3127530
DeleteKey HKCR\CLSID\{E6F27C2A-16BA- 11D2-81D0- 0000F87A7A A3}\Inproc Server32 SUCCESS Key: 0xE20F4130
DeleteKey HKCR\CLSID\{E6F27C2A-16BA- 11D2-81D0- 0000F87A7A A3} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes\{ 072B64B7-C FF7-11D2-8 801-00C04F 72ED31} SUCCESS Key: 0xE23621A8
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes\{ 5C225203-C FF7-11D2-8 801-00C04F 72ED31} SUCCESS Key: 0xE23621A8
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes\{ 70B9C151-C FF7-11D2-8 801-00C04F 72ED31} SUCCESS Key: 0xE23621A8
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes\{ 8690ABBB-C FF7-11D2-8 801-00C04F 72ED31} SUCCESS Key: 0xE23621A8
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes\{ D4F3374F-0 52F-11D2-9 7B0-00A0C9 A06D2D} SUCCESS Key: 0xE23621A8
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\N odeTypes SUCCESS Key: 0xE20F4130
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3}\S tandalone SUCCESS Key: 0xE20F4130
DeleteKey HKLM\Software\Microsoft\MM C\SnapIns\ {1C5DACFA- 16BA-11D2- 81D0-0000F 87A7AA3} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\NodeType s\{D4F3374 F-052F-11D 2-97B0-00A 0C9A06D2D} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\NodeType s\{5C22520 3-CFF7-11D 2-8801-00C 04F72ED31} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\NodeType s\{8690ABB B-CFF7-11D 2-8801-00C 04F72ED31} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\NodeType s\{70B9C15 1-CFF7-11D 2-8801-00C 04F72ED31} SUCCESS Key: 0xE377A588
DeleteKey HKLM\Software\Microsoft\MM C\NodeType s\{072B64B 7-CFF7-11D 2-8801-00C 04F72ED31} SUCCESS Key: 0xE377A588
If you look close, everything that was created during registration was deleted during "unregistration"
The point is if regsvr32 /u succeeds, you have nothing else to worry about.
The thing is some of the entries that are added to the registry when you run regsvr32 are by CLSID and not by name, so you would need to know the CLSID and search for that too. To make things worse, some dlls have more than one CLSID.
Here's an example of what happened when I ran regsvr32 adsiedit.dll:
SetValue HKCR\CLSID\{1C5DACFA-16BA-
SetValue HKCR\CLSID\{E6F27C2A-16BA-
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
SetValue HKLM\Software\Microsoft\MM
And here's what happened when I ran regsvr32 -u adsiedit.dll:
DeleteKey HKCR\CLSID\{1C5DACFA-16BA-
DeleteKey HKCR\CLSID\{1C5DACFA-16BA-
DeleteKey HKCR\CLSID\{E6F27C2A-16BA-
DeleteKey HKCR\CLSID\{E6F27C2A-16BA-
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
DeleteKey HKLM\Software\Microsoft\MM
If you look close, everything that was created during registration was deleted during "unregistration"
The point is if regsvr32 /u succeeds, you have nothing else to worry about.
ASKER
thanks