Mem Reduct Command-Line Cleaning Options

What matters for this task

Command-line behavior can differ from clicking a button with a saved configuration. In 3.5.2 the argument parser selects a default mask unless the full value is supplied. That distinction matters when testing: a command-line run should be recorded with its exact argument, not described as identical to every manual cleanup.

Steps to follow

1. Identify the verified executable and record its version. Use its full path so that a different file with the same name elsewhere is not launched by mistake.
2. Save work and test interactively before building a scheduled action. Keep the test separate from a game, capture session, or sensitive transfer.
3. Use the default-region command for an initial comparison. Record the command and the observed behavior, and avoid a fast repeating loop.
4. Review the source-defined difference before ever using the full option. If a pause or error occurs, stop automation and retain the event details for diagnosis.

"C:\Path\To\Mem Reduct\memreduct.exe" -clean

Replace the example path with your verified executable location. This is an example, not an automatically executed command.

Check the result

Compare the expected operation, observed notification or log, and the application workload. An exit without an obvious window is not automatically a proof of successful cleanup.