Every optimization BRUTAL applies is built to be reversible. There are two levels of rollback: per-module Undo to reverse one specific change, and Restore All Defaults to put everything back at once. This page explains exactly what each one does and what to expect.
When a reversible module runs, BRUTAL transparently records every registry value it is about to change — capturing the original value before it overwrites it. Command-based changes (powercfg, bcdedit, netsh) are stored as forward/reverse command pairs, binary registry values are saved too, and Module 22 even backs up the settings files it edits. Each module's backup is written as a signed JSON file under %ProgramData%\BRUTAL Optimizer\Backups\<your SID>\module_N.json, written atomically so it can't be corrupted mid-save.
Because backups live on disk, Undo buttons persist across app restarts and reboots. A module you ran last week is still reversible today — the Optimize page checks for backup files every time it loads.
You can also open the Audit view first to see the exact changes a module made before deciding to undo it.
Modules 1 (Process + Service Killer) and 2 (Cache + Storage Cleaner) are transient and have no Undo button — they end processes and delete cache/temp files, which can't be un-done. Services that Module 1 or Module 15 stopped are restarted by Restore All Defaults.
When you want to wipe the slate clean, use ↩ Restore All Defaults in Settings (it's also offered from the Home dashboard). It replays every per-module backup, reverting all captured registry, command and file changes to their original state — not a hardcoded subset. Then it:
Restore All Defaults is a big, system-wide change. You'll be asked to confirm, and you should restart your PC afterwards for the reverts to fully take effect.
Before any batch of optimizations — whether you press Run Selected, Run All, Smart Optimize or a one-click Boost/Aggressive run — BRUTAL creates a Windows System Restore point (throttled to once per session). This is a second safety net beneath the per-module backups: even a tweak the per-module undo can't reach stays recoverable by rolling back to that restore point through Windows.
Where are the backups stored?
As signed JSON files under %ProgramData%\BRUTAL Optimizer\Backups\<your SID>\ — one module_N.json per reversible module. They're written atomically and persist across restarts, which is why Undo buttons survive a reboot.
Does Restore All Defaults undo everything?
It replays every per-module backup, restarts the services the killer modules stopped, and reverts privacy and Defender hardening applied by one-click runs. The only deliberate exception is security/Integrity-Audit fixes, which are kept so a restore can't un-fix a threat. Transient file deletions (Modules 1 and 2) can't be reversed.
Do I need to restart after undoing?
For a single module, usually not — but some registry and especially boot/timer changes only fully revert after a reboot. After Restore All Defaults you should always restart.
What if Undo isn't enough — can I roll back the whole machine?
Yes. BRUTAL creates a Windows System Restore point before each optimization batch (named "BRUTAL Optimizer — Before Optimization"). If anything still feels wrong after Restore All Defaults, use Windows System Restore to return to that point.