The MASM Forum

General => The Campus => Topic started by: Don57 on January 05, 2013, 07:35:54 PM

Title: System Registry CLSID's
Post by: Don57 on January 05, 2013, 07:35:54 PM
In HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall the installed programs are listed.
About 25% are stored as CLSID values (Class ID's - COM Class Objects).
After searching the registry, I find multiple locations where I can relate the CLSID to a program or dll name. However I can find no reference by Microsoft as to where the name of the CLSID should be referenced.

Title: Re: System Registry CLSID's
Post by: japheth on January 05, 2013, 08:11:12 PM
Quote from: Don57 on January 05, 2013, 07:35:54 PM
In HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall the installed programs are listed.
About 25% are stored as CLSID values (Class ID's - COM Class Objects).

Actually, these are GUIDs ( globally unique identifiers ). Those things are used to make other things "unique" - hence they are used for CLSIDs or IIDs ... or for keys in the registry just to ensure that the key isn't used yet.

Quote
After searching the registry, I find multiple locations where I can relate the CLSID to a program or dll name. However I can find no reference by Microsoft as to where the name of the CLSID should be referenced.

I don't think these GUIDs are used as a reference. Why should they? All information needed for uninstall can be stored quite right there as subkeys/data.

Title: Re: System Registry CLSID's
Post by: Don57 on January 05, 2013, 08:24:25 PM
I need to display the program name in a child window.
Title: Re: System Registry CLSID's
Post by: Don57 on January 05, 2013, 08:29:40 PM
Yea your right, just checked the subkeys, too late at night time to go to bed. Thanks.
Title: Re: System Registry CLSID's
Post by: dedndave on January 05, 2013, 09:36:03 PM
this is a fairly short explanation....

http://www.easydesksoftware.com/rworks.htm (http://www.easydesksoftware.com/rworks.htm)
Title: Re: System Registry CLSID's
Post by: Tedd on January 06, 2013, 05:19:19 AM
Check each one for a subkey named "DisplayName" - that's the name you should display to the user, not the key name itself; "DisplayVersion" may also be useful.

If DisplayName isn't present then it's most likely a Windows Update patch, with the name in the default value (e.g. "KB2429453"); if that's null, then you'll have to use the key name.