Finding silent switches without guessing

Why “/S” is not always right

/S is a convention some installers know and many do not. Attach it blindly and you get either a silent run or a dialog hanging in the background. A package that “passes” because someone clicked is not a silent package.

MSI: properties instead of guesswork

An MSI is a database. Properties are in the vendor documentation or can be read from the MSI. Typical candidates are install directory, language, licence key and update behaviour. For a silent run one parameter set is often enough; the point is to take it from the source that matches this version, not from a random blog post.

EXE: help, logs, vendor docs

Three reliable routes: the installer's help (/?, /help, --help), vendor documentation, and the log of a test run. The log shows which arguments were accepted and what the installer actually did. That is worth more than any guess.

When nothing is documented

Then it is work. A test machine or VM, a snapshot, a run with logging. Then uninstall, restore the snapshot, next attempt. Document every attempt, or you will repeat it later.

In practice: if an installer accepts no silent arguments at all, that is a case for the vendor or for repackaging. It is not a reason to build a package that only works with clicks.

Check before packaging

1. Does the command run on a clean device without a dialog? 2. Does it return a code? 3. Is there an uninstall command with the same parameters? 4. Does uninstall leave anything behind?

Four “yes” answers give you a foundation. Everything else is detective work better done before rollout than after.

---