Back Up Mem Reduct Settings Before Changes
Exit Mem Reduct and copy its active configuration to a separate backup folder before changing settings or moving installations. Also record the version and executable path. A backup is useful only when you know which running copy and which Windows account it belongs to.
What matters for this task
A filename alone is not enough to identify the active configuration. Portable mode stores memreduct.ini alongside the program; the documented profile location is under %APPDATA%\Henry++\Mem Reduct. Two valid files can exist at the same time, but only one may be used by the copy you are launching.
Steps to follow
- Write down the executable path and the visible version. Capture the cleanup-region selections, both automation controls, and the startup setting so that their meaning is not lost in a bare INI file.
- Exit through the tray menu. Wait until the process is gone before copying the configuration to avoid taking a backup during a write.
- Copy the file into a dated folder outside the installation directory. Include a short note identifying the Windows account, application version, and whether this is portable mode.
- Make one harmless change and confirm that the expected configuration file updates. If it does not, find the active file before relying on the backup for a future restore.
Check the result
Confirm the backup exists, is readable, and has a sensible nonzero size when it came from an existing configuration. Do not overwrite your only known-good backup with an untested replacement.
Limitations and precautions
Configuration files can expose local paths or preferences. Review them before posting them in a public issue report.
Questions and answers
Can I back up while the program is running?
A closed application provides a clearer snapshot and avoids a later settings write overwriting the file you are trying to preserve.
Should I copy settings between different releases?
Only with a backup and a review of changed settings. An older INI file is not a guarantee of identical behavior in another build.
Sources and evidence
Product statements use the tagged release documentation. Diagnostic steps are proposed checks, not claimed laboratory results.