The CLSID key contains information used by the default COM handler to return information about a class when it is in the running state. To obtain a CLSID for your application, you can use the Uuidgen.exe, or use the CoCreateGuid function. The CLSID is a 128-bit number, in hex, within a pair of curly braces.
A programmatic identifier (ProgID) is a registry entry that can be associated with a CLSID. Like the CLSID, the ProgID identifies a class but with less precision because it is not guaranteed to be globally unique.
CLSID is an abbreviation for class identifier, in the same way that GUID is an abbreviation for globally unique identifier. Both abbreviations refer to a 128-bit integer with a low statistical likelihood of being duplicated so that it can be used as a unique identifier across computers and networks.
Local RPC (LRPC) is an Inter-Process Communication (IPC) mechanism that enables data exchange and invocation of functionality residing in a different process that resides on the same computer.
5. Open the Component Services Tool Using the Control Panel Press Win + X and select Search from the options. Type Control Panel and then select the Best match result. Expand the View by drop-down menu and select Large icons. Select Administrative Tools from the menu items. Double-click on the Component Services option.
A CLSID is a globally unique identifier that identifies a COM class object. If your server or container allows linking to its embedded objects, you need to register a CLSID for each supported class of objects.
Search for the program, folder or library name in regedit. You will probably find several occurrences but one of them should tell you the CLSID.
If you have a CLSID {} you can take a look at the registry key HKEY_CLASSES_ROOT\CLSID\{}\ . The default value for the registry key will give you a description of the CLSID. Other values under the key will give you more information like the DLL that implements the interface and a short name (program ID).