FIELD MANUAL / 18
Recovery, uninstall & troubleshooting
Determine whether a change is session-based, persistent or a file operation before choosing a recovery action. Preserve recovery records rather than deleting the application first.
- Where to find it
- Module restore action → Settings → Pudding-Rescue.cmd when necessary
- When it applies / restoration
- A failed restore is not success. Check state and logs; interrupt-affinity restoration also requires a restart.
Step by step
- For a single regression, disable the relevant option, exit the game and check recovery logs.
- Restore persistent options in their own modules. Turning protection off is not a system-wide reset.
- Restart Pudding after a crash so pending restoration can retry. Review a diagnostic summary before sharing it.
- Use the rescue script for situations where the app cannot open or emergency recovery is needed. Prefer the Settings uninstall action for normal removal.
Three categories of change
Session scheduling restores from records on exit. Environment, application GPU preferences and per-EXE compatibility settings need separate restoration. Deleted caches/layers and one-time input-language changes do not roll back like ordinary session settings.
What the rescue script does
Pudding-Rescue.cmd requests elevation, exports logs, crash and power/boot information to a Pudding-Rescue desktop folder, then restores from receipts. It also removes the library, whitelist and settings, resets power plans to factory defaults, and requires a restart.
How to report a useful issue
Include the Pudding/Windows versions, CPU/GPU, game, mode, recently changed options and reliable reproduction steps. State whether restoration succeeded. Share only diagnostic details you choose; this website does not automatically upload local logs.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.