What Installer Types and Automation Tools Does Silent Install Builder Support?

Updated

Silent Install Builder 6 supports the most common Windows installer families — InstallShield, Inno Setup, Nullsoft (NSIS), and Windows Installer (MSI) — and can automate them through CMD, VB, PS1, JS, and other scripting tools. It also recognizes the installer type and its command-line switches automatically, which is the part of unattended installation the vendor describes as the most difficult. The practical benefit: you can build a silent package even for software that has no native silent switches, because the tool records an installation automation script instead of relying only on command-line options.

Supported installer types

The site lists these installer families as recognized automatically, along with their command-line switches:

Installer family What the tool does with it
InstallShield Detects the installer type and applies the appropriate command-line switches
Inno Setup Same automatic detection and switch handling
Nullsoft Installer (NSIS) Same automatic detection and switch handling
Windows Installer (MSI) Handles MSI-based unattended installation

The list is described as containing "some supported installers," so treat it as the documented core set rather than an exhaustive catalog. For anything outside these families, the recording feature is the fallback path.

Automation tools and scripting

Silent Install Builder supports CMD, VB, PS1, JS, and other automation tools. Two capabilities matter most when you plan a package:

  • Installation Automation script recording. You record the steps of an installation once, and the tool replays them silently. This is what makes it possible to install applications that do not support command-line options.
  • Custom installation conditions using JS and the .NET Framework API. You define when and how parts of your installer run, based on system checks, file presence, registry values, or other conditions. Built-in functions handle working with files and the Windows registry.

That combination covers two different jobs: replaying a GUI installer that has no silent mode, and gating parts of a package so they only run on machines that meet your conditions.

Multi-application packages

A single package can contain multiple application installers. Running the package installs the included programs automatically in background mode, silently. This is the mechanism behind one-click deployment of a software set across multiple devices.

How to check support for your specific installer

  1. Identify the installer technology behind your target application (for example, by checking whether it is an MSI or which setup framework it uses).
  2. If it matches one of the documented families, let the tool detect the type and switches; verify by running the built package on a test machine.
  3. If it does not match, plan on recording an Installation Automation script instead of relying on command-line switches.
  4. If parts of the install should be conditional, add JS or .NET Framework API conditions using file, registry, or system checks, then re-test on a machine that both meets and fails the condition.

The expected result at each step is a package that installs without user interaction; if a test run still prompts, the installer likely needs the recording path rather than switch-based automation.

Limits to keep in mind

The documented material covers installer recognition, script recording, conditions, and multi-app packaging. It does not publish a complete compatibility list, so unusual or custom installers should be validated with a trial build before wider deployment. A trial download is offered on the site; pricing and licensing terms are not detailed in the material reviewed here, so check the order page for current terms.