FIELD MANUAL / 11
System environment & input
These changes can persist, and some require a restart. Read each option and distinguish environment settings from temporary session policies.
- Where to find it
- Advanced → System environment
- When it applies / restoration
- Persistent settings do not revert when a game exits or protection is disabled. Restore them individually.
Step by step
- Inspect the system audit first and identify the setting relevant to the problem.
- Read the current state, restart requirements and tradeoffs, then change one option.
- Network, power and input changes can affect the entire computer; record the original behavior before testing.
- Use the option’s restore action for regressions. If the app cannot open, consult Recovery instead of stacking more optimization tools.
Kernel and security-related settings
HAGS, windowed-game optimization, VBS, speculation mitigations and timers affect different paths. Disabling VBS or mitigations changes system protection; these are not required settings for using Pudding.
Network and input-device paths
Network energy-saving changes can briefly disconnect the link, and interrupt-moderation experiments also affect non-gaming interrupt rates. Input-device suspension settings target input paths. Queue length and foreground scheduling checks belong in System audit.
Switches can represent Pudding ownership
Since 2.2.2.2, the windowed-optimization switch represents Pudding’s own change. It may appear off even if Windows already had the setting enabled. Follow the option’s explanation rather than repeatedly toggling it.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.