Difference between revisions of "RegyChange"

From SpybotWiki
Jump to: navigation, search
m (Examples: added example description)
m (Description: added HKLM details.)
 
(4 intermediate revisions by one other user not shown)
Line 2: Line 2:
 
|SYNTAX = RegyChange
 
|SYNTAX = RegyChange
 
|PENAME = SpybotSD.exe
 
|PENAME = SpybotSD.exe
|PEVERSION = 1.4 or later
+
|PEVERSION = 1.4 or later<br />1.5.3 for adv. file
 
|GROUP = Registry
 
|GROUP = Registry
 
|MINUPDATE = n/a
 
|MINUPDATE = n/a
|ADVFILEPARAMS = no
+
|ADVFILEPARAMS = yes (sixth)
|ADVREGPARAMS = yes (fifth)
+
|ADVREGPARAMS = no
 
|ADVBUILDPARAMS = yes (fifth)
 
|ADVBUILDPARAMS = yes (fifth)
 
|ADVSPECIALPARAMS = ''value=data''
 
|ADVSPECIALPARAMS = ''value=data''
Line 12: Line 12:
  
 
==Usage==
 
==Usage==
  RegyChange:<description>,<rootkey>,<keypath>,<value=data>[,advanced registry parameters]
+
  RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced build parameters[,advanced file parameters]]
  
 
===Examples===
 
===Examples===
Line 23: Line 23:
  
 
# First, a description. Using a [[Description templates|description template]] instead of plain text is recommended so that the user will receive a localized version.
 
# First, a description. Using a [[Description templates|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 root key, where HKEY_CURRENT_USER stands for all users actually, and HKEY_LOCAL_MACHINE covers both 32 and 64 bit where applicable, so no Wow6432Node subkey is required.
 
# The path to the value, starting with a backslash. {{AlgoPrefix}} {{PathTemplates}}
 
# The path to the value, starting with a backslash. {{AlgoPrefix}} {{PathTemplates}}
# An entry that is used to assign new data to a value. You can use a simple ''value=newdata''; or for numeric values, ''value=dword:0815''. Binary is possible as well. [[AlgoPrefix|Algo-Prefixes]] are allowed for both value name and text data here. {{AlgoPrefix}}
+
# An entry that is used to assign new data to a value. You can use a simple ''value=newdata''; or for numeric values, ''value=dword:0815'' (or ''value=W=0815'' in short). Binary is possible as well (''value=B=0011''). [[AlgoPrefix|Algo-Prefixes]] are allowed for both value name and text data here. {{AlgoPrefix}}
# This field supports [[Advanced registry parameters|advanced registry parameters]], to be able to use another value as an additional criterion.
+
# This field supports [[Advanced build parameters|advanced build parameters]]. Verifiers are not supported, since the change code conflicts with the verification code currently.
 +
# Starting with 1.5.3, [[Advanced file parameters|advanced file parameters]] for [[:Category:Advanced_file_parameters_for_Flow_Control|Flow Control]] can be specified. {{PathTemplates}}
  
 
You should keep in mind that even system registry values may differ between Windows versions.
 
You should keep in mind that even system registry values may differ between Windows versions.
Line 34: Line 35:
  
 
==See also==
 
==See also==
 +
* [[Advanced file parameters]]
 
* [[Advanced build parameters]]
 
* [[Advanced build parameters]]
 
* [[Advanced registry parameters]]
 
* [[Advanced registry parameters]]

Latest revision as of 19:49, 25 June 2008

RegyChange
Group Registry
Main Application Version 1.4 or later
1.5.3 for adv. file
Required Update n/a
File Parameters yes (sixth)
Registry Parameters no
Build Parameters yes (fifth)
Special Parameters value=data

Looks wether the given registry value has another value then the given one.

Usage

RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced build parameters[,advanced file parameters]]

Examples

RegyChange:"Folder history",HKEY_CURRENT_USER,"\Software\Microsoft\Internet Explorer\Main\","Save Directory="

Empties the registry value Save Directory.

Description

This command checks whether a specified value has known data, to be able to correct that data back to the known one should it have been changed.

  1. First, a description. Using a description template instead of plain text is recommended so that the user will receive a localized version.
  2. The root key, where HKEY_CURRENT_USER stands for all users actually, and HKEY_LOCAL_MACHINE covers both 32 and 64 bit where applicable, so no Wow6432Node subkey is required.
  3. The path to the value, starting with a backslash. AP PT
  4. An entry that is used to assign new data to a value. You can use a simple value=newdata; or for numeric values, value=dword:0815 (or value=W=0815 in short). Binary is possible as well (value=B=0011). Algo-Prefixes are allowed for both value name and text data here. AP
  5. This field supports advanced build parameters. Verifiers are not supported, since the change code conflicts with the verification code currently.
  6. Starting with 1.5.3, advanced file parameters for Flow Control can be specified. PT

You should keep in mind that even system registry values may differ between Windows versions.

Scan Results

  • A special result that allows to change the value back to the known data upon fixing.

See also

Similar commands