FIELD MANUAL / 06 / UI 3.3.1.2
Tuning panel and Laboratory
Choose extra tuning under Game & background, Graphics, System and Laboratory.
Step by step
- On your first visit to Tuning, a guide can be closed after three seconds. Use One-click setup if unsure, or keep the defaults; core features run during game scheduling according to your saved settings.
- Presets and Smart/Competitive scenes are selected separately. Author’s setup uses Normal governance and basic CPU-mitigation disabling; Extreme uses Aggressive governance, the extended mitigation scope and GPU clock/power controls. Both disable VBS, follow the original CPU-idle policy and restore the original foreground quantum.
- Game GPU and disk I/O priority are in the per-game render scheduling dialog. Background governance manages eligible background CPU, I/O, page and GPU priority and efficiency mode, including Delivery Optimization yielding. Keep-awake follows session and foreground conditions.
- Maintenance-trigger limits follow background governance and stay off when it is off. Multimedia scheduling is a separate switch, on by default; it applies only while protection is on and restores when the switch or protection is turned off. Desktop compositor scheduling and its old switch are removed.
- Tuning has Game & background, Graphics, System and Laboratory tabs. Follow each control’s actual support, readback status and PC/game restart notices.
- Manual memory cleanup during a game reclaims only Pudding memory. Configure the separate standby cleaner under Settings → General.
- Choose EPP, CPU idle, GPU clock, GPU power and low-buffer audio separately. File-filter, clock-repair and audio-effects tweaks are removed; recovery of older changes remains available.
- Smart and Competitive share power settings. Managed power uses the legacy policy on laptops and CPU-specific presets on desktops, with a verified copy of the original plan when a high-performance template is unavailable. ROG Ally, GPD WIN and similar handhelds remain under system and vendor control.
Compare individual changes
Optional timer, cache and other controls can reduce performance in some environments. Record the original configuration, compare the same workload and keep suitable choices.
Microsoft background in ordinary governance
The built-in list covers DiagTrack, DPS, WdiServiceHost, WdiSystemHost, diagsvc, WSearch, verified indexing workers, Widgets and their WebView2 processes, even at low load. They follow the Off/Normal/Aggressive levels with no separate switch, scan, dedicated Job or CPU quota; write strength, efficiency mode, background core placement, switch-out release and match-end restoration all follow ordinary background. A shared host is eligible only when all its running services are listed. Manual allowlists, service allowlists and family protection remain effective; services are not started or stopped for this governance. The WeGame main process is governed the same way and is left alone only while it is in the foreground. Aggressive also confines ordinary background apps to a few cores so the game keeps its preferred ones.
In-game power-plan guard
While a session owns a plan, the guard keeps checking the active plan and managed parameters and correcting external changes without switching the preference to No switching. Checks and writes are serial; repeated conflicts slow the response interval to at most 15 seconds, which is an interval rather than a guarantee of successful writes. Initial acquisition, plan creation, write failures, monitor-registration failures and restoration retain bounded retries, preserving later external writes on restoration.
Earlier demo screenshots for 3.3.0.8 use fictional games and synthetic readings. Current controls follow the 3.3.1.2 manual and your hardware support. Follow actual support status on your machine.
Continue reading → Anti-cheat and whitelist