Something broke after I optimized: find the culprit and undo it fast

Almost everything BRUTAL changes is reversible, so a problem that appears right after an optimization pass is usually quick to fix. The trick is to match the symptom to the module that most likely caused it, then undo just that change instead of guessing.

Act fast, in order. Don't pile on more tweaks to "fix" a broken state, and don't reinstall Windows yet. Start with the smallest, most targeted undo and only climb the ladder if it doesn't help. Reaching for the right step first is faster and far less disruptive.

Find the likely culprit

Each row pairs a symptom with the module (or two) most likely responsible. If you only ran Smart Optimize or a Boost pass, you may not have touched all of these, so undo the ones you actually applied first.

SymptomMost-likely module(s)
No soundModule 15 (system debloat + latency, audio latency tweaks) or Module 22 (app optimizer)
No internetModule 5 (network stack) or Module 17 (network adapter deep)
Black screen / display glitchModule 6 (GPU tweaks) or Module 14 (GPU deep tuning)
A game won't launchModule 3 (IFEO priority), Module 9 (Emulator Performance Tuning) or Module 11 (VBS/Spectre)

To see exactly what you ran, check the log on the Optimize page or %LOCALAPPDATA%\BRUTAL\guardian_log.txt. Not sure which module does what? See what each module does.

The fast recovery ladder

Work down this list. Stop as soon as the problem clears.

  1. Per-module Undo — on the Optimize page, find the module you suspect and click its Undo button. This reverts only that module's changes and is the cleanest fix.
  2. Restore All Defaults — Settings → Restore All Defaults reverts every reversible module at once. Use this when you're not sure which module is at fault.
  3. System Restore — roll back to the restore point named BRUTAL Optimizer — Before Optimization that the app takes before major changes. See system restore points.
  4. Safe Mode — if the screen is unusable (for example, a black screen you can't click past), boot Windows into Safe Mode and then run Undo, Restore All Defaults, or System Restore from there.
Two changes can't be undone. Module 1 (process + service killer) and Module 2 (cache + storage cleaner) are transient by design — they don't change persistent settings, so there's nothing to revert and no Undo button for them. They are not the cause of a setting that "stays broken."

For the full picture of how reverting works — including how the Undo backups are stored and what survives a reboot — read undo and restore defaults.

If none of that works

Email [email protected] with your app version (Settings → System Information / About), your Windows version, the exact steps that triggered the problem, and the Optimize/Guardian log from %LOCALAPPDATA%\BRUTAL\. Screenshots help too. See contact support.

FAQ

Which module broke my sound?

Usually Module 15 (system debloat, audio latency tweaks) or Module 22 (app optimizer). Open the Optimize page and click Undo on whichever of those you applied. If you're unsure which you ran, use Settings → Restore All Defaults.

My screen is black and I can't click anything — what now?

Boot Windows into Safe Mode, then run the suspect module's Undo, or Settings → Restore All Defaults, or roll back to the 'BRUTAL Optimizer — Before Optimization' System Restore point. A black screen most often traces to Module 6 (GPU tweaks) or Module 14 (GPU deep tuning).

Can I undo Module 1 or 2?

No — those are transient (process/service kill and cache clean). They don't change persistent settings, so there's nothing to revert and no Undo button. They aren't the cause of a setting that stays broken.

More in Troubleshooting

← Back to the Help Center