Short answer: BRUTAL Optimizer is designed from the ground up to be anti-cheat-safe. It does not read or write game memory, it does not inject DLLs into games, and it does not hook DirectX. Every feature that could look like cheating to an anti-cheat system was deliberately built a safer way — usually by leaning on built-in Windows tools instead of touching the game at all. This article explains how, so you can run it alongside titles protected by Vanguard, BattlEye, Easy Anti-Cheat, and similar.
Anti-cheat software flags programs that interfere with a protected game: reading its memory, injecting code, or hooking its rendering. BRUTAL Optimizer does none of those things. It optimizes the system around the game — the Windows registry, services, power plan, drivers, network stack — not the game itself.
This is the feature people worry about most, because most FPS overlays work by injecting into the game and hooking DirectX — exactly the behavior anti-cheats hunt for. BRUTAL Optimizer's overlay does not do that. It reads the display's frame rate from a documented Windows graphics statistic (the D3DKMT display present count) at the desktop level. There is no DirectX hook and no injection, so there's nothing for an anti-cheat to flag.
When the Guardian service detects a game and elevates its priority, locks a timer resolution, or disables power throttling, it does so entirely through standard Windows APIs (the same ones Task Manager and the OS use). It sets the game to High priority through the official process API — it never opens the game's memory to modify it. Drive and disk maintenance run through the in-box Windows tools (fsutil, defrag.exe) with no custom kernel driver and no firmware tampering.
Drive Health is a thin wrapper over Windows' own storage engine. No kernel driver is installed, no custom disk-rewriting engine runs, and nothing touches drive firmware or the storage controller. It only analyzes, runs TRIM on flash, or defragments a confirmed hard drive — all using the built-in Windows commands.
The Disk Cleaner's GPU shader caches category is special. Clearing it forces a one-time shader recompile, which would cause stutter if you wiped it mid-session. So that category is automatically skipped while a game or emulator is running. This isn't an anti-cheat concern — it's about not ruining your session — but it's a good example of how the app checks for a running game before acting.
If an anti-cheat ever warns about any background tool, the standard advice applies: it's almost always a generic caution about third-party software, not a detection of cheating. BRUTAL Optimizer performs no injection, no memory access, and no DirectX hooks, so there is nothing for it to legitimately flag. If you want maximum peace of mind during a ranked session, you can hide the overlay with its hotkey (Ctrl+Shift+F) and keep optimizing the system around the game as usual.
Smart Route relays your game’s server traffic through a WireGuard tunnel. Nothing of ours touches the game — but whether a publisher permits relayed traffic is their rule, not our mechanism, and they can detect it. That is why only titles we have verified use server-side anti-cheat are ever routed automatically, and why kernel-anti-cheat titles and anything unverified stay manual-only. See “Will Smart Route get me banned?”.
Will the FPS overlay get me banned?
It is built specifically to avoid that risk. Unlike typical overlays, it does not inject into your game or hook DirectX — it reads a documented Windows display statistic at the desktop level. There's no game-process interference for an anti-cheat to detect.
Does BRUTAL Optimizer read or modify game memory?
No. It never reads or writes any game's memory and never injects code into a game. It optimizes Windows itself — registry, services, power, drivers, network — using standard system APIs.
Is it safe with Vanguard, BattlEye, or Easy Anti-Cheat?
Yes. Because it performs no injection, no memory access, and no DirectX hooks, there is nothing for those anti-cheat systems to legitimately flag. The risky techniques they look for simply aren't present.
Why does the shader-cache cleaner skip while I'm gaming?
Clearing GPU shader caches forces a one-time recompile, which causes stutter on the first run after. To avoid wrecking an active session, that category is automatically skipped whenever a game or emulator is running.