The Undo function  is only advisable to use if the New snapshot is actually new, i.e. newly scanned, and reflects the current state of the Registry. Only in that case would the proper return to the previous version of the key take place. If the time since your last scan exceeds 10 minutes, you will see a warning. Of course, 10 minutes is not reliable enough to ensure that the key is truly up-to-date, so you need to be aware of possible registry changes and determine the state of the registry yourself.
|
|
|
| If you have just scanned a new snapshot of the Registry and immediately compared it, you can feel confident that you are dealing with a fully current state of the Registry and should it be necessary, you can correctly return to a previous state.
|
|
|
| You may ask, why Undo is available if a New snapshot is not fully up-to-date? The answer is that it is not always necessary to change only a fresh version; you may well need to change some old ones. For example, if you compare a snapshot of the Registry scanned before the installation of a program to a snapshot scanned after it, The Compare function shows changes that appeared due to the installation of that program. In that case Undo removes only those changes that were caused by the program installation.
|
|
|
Similarly,  Redo (in the example of a program installation) makes the same changes to the Registry that the installation of the program originally made. Unlike Undo, however, Redo is not time sensitive, i.e. there is no warning if the time since a New snapshot scan exceeds 10 minutes.
|
|
|
| In general, it is advisable to use Redo only when settings of a program are damaged and you want to restore them and happen to have Registry snapshots that were scanned prior to and after the installation of the program.
|
|
|
| When comparing a snapshot from a REG file or tweak (First node) with the current state of the registry (Second node) the Undo function changes the current registry according to the values in the REG file or tweak.
|
|
|