Look up unattended install and uninstall flags for MSI, InstallShield, NSIS, Inno Setup, WiX, and more. Search by name or switch — or drop in the installer and let FLAGR identify it.
If the vendor or packaging engine isn't obvious from the filename, these checks usually reveal it in under a minute.
Most engines print their own usage text. Try /?, /help, or --help and read the console output — it often names the engine outright.
Open the .exe in 7-Zip or a hex/strings viewer. Look for telltale text like "Inno Setup", "Nullsoft", "InstallShield", or "Wise Installation" embedded near the top of the file.
Right-click → Properties → Details. The "Comments" or "Product Name" field frequently names the packaging tool used to build the installer.
When nothing else works, cycle through /S, /s, /silent, /verysilent, /quiet, -q, --silent — one of these covers the vast majority of third-party .exe installers.
FLAGR is an independent reference tool and is not affiliated with, endorsed by, or sponsored by Microsoft, Flexera/InstallShield, the WiX Toolset project, the NSIS project, Igor Pavlov/7-Zip, or any other vendor named on this page. Product and project names are used only to identify the installer technology they refer to.
Switches are compiled from public documentation and common packaging practice. Installer behavior varies by version and vendor customization, so treat every entry as a starting point — test in a non-production environment before relying on any switch for mass deployment.
The file-detection feature runs entirely in your browser: files are read locally and never uploaded
or transmitted anywhere. Engine detection, flag discovery, and usage-text extraction are all heuristic
(pattern matching on file bytes), not a guarantee — they can occasionally miss or misidentify obfuscated,
repackaged, or unusually built installers. Always confirm with the installer's own /? or
--help output before scripting a deployment.