Undoing changes and Restore All Defaults

Every optimization module except 1 and 2 is built to be reversible. There are two levels of rollback: per-module Undo to reverse one module, and Restore All Defaults (now Roll back all changes on the History page) to roll all of them back at once. This page explains exactly what each one does and what to expect.

How the backup system works

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.

Undoing a single module

1. Open the Optimize page.
2. Find the module you ran — it shows an ↩ Undo button (its tooltip shows when the backup was taken).
3. Click Undo and confirm.
4. BRUTAL puts that module's registry values and settings files back as they were and runs its recorded reverse commands (for power and network commands, Windows' defaults), logs the result, and hides the Undo button.

You can also open the Audit view first to see the exact changes a module made before deciding to undo it.

Roll back all changes (formerly Restore All Defaults)

When you want to wipe the slate clean, use Roll back all changes on the History page (Home's Restore… link opens it). It replays every per-module backup, not a hardcoded subset: registry values and settings files go back to what they were, the power plan you had comes back, and other power and network commands go back to Windows' defaults. Then it:

• Restarts the services Boost stopped, using the exact list Module 1 recorded, and sets SysMain, Windows Search and DiagTrack to start automatically.
• Puts privacy settings back to Windows defaults, and Defender settings BRUTAL strengthened back to the values it captured first.
• Leaves what can't come back: closed apps, cleared caches and deleted junk. DNS, startup items and game profiles are rolled back on their own pages.
• Clears the backup files once they've been replayed, including the records of any module it couldn't fully restore.

The restore point safety net

Before any batch of optimizations — whether you press Run Selected, Run All, Smart Optimize or a one-click Boost/Aggressive run — BRUTAL attempts a Windows System Restore point (throttled to once per session; Windows refuses one when System Protection is off). This is a second safety net beneath the per-module backups: a change the per-module undo can't reach can be rolled back through Windows when that restore point exists.

How to fully roll back your PC

1. First try Roll back all changes on the History page — confirm and let it finish.
2. Restart your PC.
3. If something still feels off, use Windows' own System Restore and pick the "BRUTAL Optimizer — Before Optimization" point created before your run.

Common issues / troubleshooting

• No Undo button on a module — either it's a transient module (1 or 2), or it hasn't been run on this PC yet, so there's no backup to restore.
• "Restore point skipped" in the log — System Restore is disabled or was rate-limited by Windows. Per-module backups still protect you; consider enabling System Restore for the extra net.
• A module reports it couldn't fully undo — after a single-module Undo its backup file is kept so you can retry; Roll back all changes clears the records it couldn't restore. The log names what failed.
• Changes seem to come back — some settings only revert after a restart. Reboot after a big Undo or a roll back.
• Integrity-Audit fixes survive Restore — security remediations are intentionally excluded from Restore All Defaults so restoring optimizer settings never silently re-opens a fixed threat.