ChaoticSi1ence/SlimBrave-Neo v1.7.0

v1.7.0 - Unmanaged DNS default & multi-profile Shields repair

on GitHub

DNS handling is no longer opinionated by default, and the Shields prefs-leak repair now covers multi-profile setups.

New

• unmanaged DNS mode - the new default on all platforms. Apply writes no DNS policy at all until you explicitly pick a managed mode (automatic, off, secure, custom), so Brave's own DNS settings stay user-controlled. Previously every Apply force-wrote a DNS policy - on Windows the default was off, which actively force-disabled DoH and locked the DNS section in brave://settings as "managed by your organization". Selecting unmanaged and applying also removes any DNS policy a previous version wrote.
• Exports omit DnsMode when DNS is unmanaged; configs with an explicit DnsMode (including all bundled presets) import and apply exactly as before.

Fixed

• Shields prefs-leak repair now scrubs every browser profile (Default, Profile 1, Profile 2, ...) on all platforms. Previously only Default was repaired, so multi-profile users could be left with Shields stuck off in secondary profiles after unchecking the Shields toggles. User-set per-site exceptions are preserved; System Profile and Guest Profile are left alone.
• Windows: the self-elevation relaunch now passes -NoProfile -ExecutionPolicy Bypass, so starting the script from a shell that used -ExecutionPolicy Bypass no longer fails silently under a restrictive machine policy.
• The Brave Dev channel is now recognized on Linux by both Python scripts for prefs repair and running-process detection (previously only slimbrave-linux.py knew about it).

Changed

• Maximum Privacy preset no longer forces incognito-only browsing (IncognitoModeAvailability: 2 removed). Forced incognito silently disabled history, persistent logins, and most extensions - more surprise than protection. The preset's forget-first-party-storage-on-close enforcement remains and covers the intent; the Force Incognito toggle is still available manually. See the preset notes in the README.

Upgrade note: if a previous version applied a DNS policy you never wanted, re-run the tool, leave DNS on unmanaged, and Apply - the policy is removed and DNS control returns to Brave's settings UI.

After applying, verify at brave://policy - every row should report OK.