Reversibility
How DRX Optimizer revert works
The safest revert behavior is not always 'go back to Windows default'. Many users already changed Windows before installing an optimizer. A correct revert should restore the previous value saved before DRX modified it.
Correct revert principle
DRX should revert to how the system was before DRX changed it. That is safer than assuming every PC should return to the same default value.
Previous state vs Windows default
If a user changed a registry value before installing DRX, then DRX applies a tweak, revert should restore the pre-DRX value. Forcing a generic Windows default could erase the user's own configuration.
What needs to be saved
A reliable revert system needs to save enough identity for each change: tweak id, registry path, registry value name, previous value, service state, task state, power setting, or other target-specific metadata.
Single tweak revert
Reverting one tweak should not undo unrelated tweaks. This is why revert data needs to be keyed precisely instead of relying on broad category-level assumptions.
Batch revert
Batch revert should apply the same rule at scale: restore saved previous states where available and clearly report items that cannot be reverted because no prior state exists.
Old logs and compatibility
When an app evolves, older backup logs may use different shapes. Revert logic should remain compatible with older logs where possible and report unsupported records clearly.