Difference between revisions of "RegyKey"
m (→Description: added adv build info) |
m (added info on ADVFILEPARAMS) |
||
Line 5: | Line 5: | ||
|GROUP = Registry | |GROUP = Registry | ||
|MINUPDATE = n/a | |MINUPDATE = n/a | ||
− | |ADVFILEPARAMS = | + | |ADVFILEPARAMS = yes (sixth) |
|ADVREGPARAMS = yes (fifth) | |ADVREGPARAMS = yes (fifth) | ||
|ADVBUILDPARAMS = yes (fifth) | |ADVBUILDPARAMS = yes (fifth) |
Revision as of 15:07, 29 April 2008
RegyKey | |
Group | Registry |
Main Application | Version 0.95 or later 1.5.3 for adv. file |
Required Update | n/a |
File Parameters | yes (sixth) |
Registry Parameters | yes (fifth) |
Build Parameters | yes (fifth) |
Special Parameters | no |
Searches for the defined registry key and adds it to the results list, if found.
Usage
RegyKey:<description(string)>,<rootkey(enum)>,<keypath(string)>,<key(string)>[[,advanced registry parameters][,advanced file parameters]]
Examples
RegyKey:"User settings",HKEY_CURRENT_USER,\SOFTWARE\,"Spyware"
Description
Detects a registry key and flags it for removal.
- First, a description. Using a description template instead of plain text is recommended so that the user will receive a localized version.
- The root key, where HKEY_CURRENT_USER stands for all users actually.
- The path to the value, starting with a backslash. This may not include the actual subkey you want to remove. PT
- The name of the key to detect. You may use a Algo-Prefix here. AP PT
- To refine detection, you can use advanced registry parameters to check the actual data of the value, as well as advanced build parameters. You may use Algo-Prefixes here. AP PT
- Starting with 1.5.3, advanced file parameters for Flow Control can be specified. PT
Scan Results
- The identified registry key(s).
See also
- Advanced file parameters
- Advanced build parameters
- Advanced registry parameters
- AlgoPrefix
- Description templates