Difference between revisions of "CLSID"
(→Usage: added var types) |
(→Examples: added live help example) |
||
| Line 15: | Line 15: | ||
===Examples=== | ===Examples=== | ||
| + | CLSID:"Spyware Class","<$SYSDIR>\spyware.dll" | ||
CLSID:"Dummy Class" | CLSID:"Dummy Class" | ||
| − | + | The second example would detect the following class: | |
[HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}] | [HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}] | ||
@="Dummy Class" | @="Dummy Class" | ||
Latest revision as of 15:56, 22 February 2008
| CLSID | |
| Group | Registry |
| Main Application | Version 1.3 or later |
| Required Update | n/a |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | no |
| Special Parameters | no |
Searches the registry for a class with the given name.
Usage
CLSID:<class(string)>[,filename(string)]
Examples
CLSID:"Spyware Class","<$SYSDIR>\spyware.dll" CLSID:"Dummy Class"
The second example would detect the following class:
[HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}]
@="Dummy Class"
Description
Please do use RegyKey wherever the CLSID GUID itself is static; this command is reserved to identifying class IDs that are random and cn be identified only by their class name, or where you need to specify attributes of the associated file.
- The first mandatory parameter simply specified the exact name of the class.
- The second parameter can be a substring of the InprocServer32 filename. After 1.5.2, this also supports Algo-Prefixes. AP
Scan Results
- The CLSID entry identified by the specified name.
