Windows 7 Get all CLI parameters/switches from NSIS installer

1. Documentation: Check the documentation or any accompanying README file that might have information on supported switches and their usage.
2. Silent Install Switch: As you mentioned, the /S switch is a common silent install switch used with NSIS installers. Sometimes, additional switches might be supported, such as /VERYSILENT or /SUPPRESSMSGBOXES. You can try running the installer with these switches to see if they are recognized and properly handled. For example:
   Code:

   Program.exe /S Program.exe /VERYSILENT Program.exe /SUPPRESSMSGBOXES

3. Contact the Developer: If the above methods do not yield any results, it might be best to reach out to the software developer or their support team directly. They should be able to provide you with the correct switches to use for automating the installation process. Keep in mind that not all NSIS installers support customization via command-line switches, and their availability depends on how the installer was specifically designed.

Exploring NSIS Installer CLI Switches​

1. Common NSIS Switches:
   You already know about /S for silent install, and there are a handful of other frequently supported switches to experiment with:
   • /D=: Specifies the directory for installation.
     
     • /NCRC: Skips the CRC check.
     • /LANG=: Specifies a particular language if the installer supports multiple languages.
     • /SUPPRESSMSGBOXES: Suppresses message boxes during installation.
   
   Example usage:
   
   Code:

    Program.exe /S /D=C:\MyFolder /SUPPRESSMSGBOXES

   • Command-Line Output:
     Some NSIS installers provide insights on switches when you run the .exe file with /?, /HELP, or similar flags:
     
     Code:

      Program.exe /? Program.exe /HELP

   • Check for Hidden Switches in the Installer:
     If you have access to the installer file and want to dig deeper:
     • Use a tool like 7-Zip or Resource Hacker to open the installer and inspect the embedded resources. Sometimes, useful hints or documentation are included within the embedded files.
   • Using Process Monitor for Silent Clues:
     Tools like Process Monitor (ProcMon) from Sysinternals can help you monitor the execution of the installer and its sub-processes. By analyzing the installer as it runs, you might discover additional parameters it processes.
   • Inspect Installer Behaviors:
     If the .nsi script source code is not available, here’s an alternative:
     • Use Strings or similar tools to scan the installer binary for clues. For example, running strings on the installer might reveal hidden switches.
   • Decompile NSIS Installer:
     If it's your own installer (or you have permission):
     • Use NSIS’ Uncompile utility to extract the script from the installer if it's not obfuscated. Doing so will give you direct access to all defined switches:
       
       Code:

        nsis.exe /UNC

   • Look for Community Reports:
     Many NSIS-based setups share common implementation patterns. Searching forums or Stack Overflow for your installer’s name might reveal more undocumented features or switches that others have discovered.

Final Notes​

• Always Back Up: Before experimenting with any undocumented switches, ensure you have appropriate backups of your system or environment to prevent unintended issues.
• Trial-and-Error Tip: Use a virtual machine to test your experiments beforehand to reduce the risk of affecting your main system.