Silent Install on Windows Explained

What Is a Silent Install?

A silent install (also called an unattended install or quiet install) is an installation that runs to completion without displaying any graphical wizard, dialog boxes, or progress screens. The installer runs in the background, makes all its decisions based on default settings or command-line arguments, and exits when it is done.

Silent installs are used by IT administrators provisioning corporate workstations, DevOps engineers building machine images, CI/CD pipelines setting up build agents, and tools like DevTools Installer that automate multi-tool developer environment setup. Without silent install support, you would need to click through every installer wizard manually — which is exactly the problem DevTools Installer was built to solve.

The key insight is that the same installer executable that shows you a GUI wizard also supports a headless mode. You just have to know the right command-line switch — and that switch depends on which installer framework the publisher used.

MSI Installers — Windows Installer Technology

MSI (Microsoft Software Installer) is the native Windows installer technology, built into Windows Installer (msiexec.exe). MSI files end in .msi and are common for enterprise software like Java JDK, Maven, Yarn, AWS CLI, and Azure CLI. They are not run directly — they are passed to msiexec.exe.

Silent install switches

msiexec /i package.msi /quiet
msiexec /i package.msi /quiet /norestart
msiexec /i package.msi /passive          ; shows progress bar, no dialogs

The /quiet flag is the most commonly used. It suppresses all user interface — no wizard, no dialogs, no progress bar. The installer runs entirely silently. /norestart prevents the installer from rebooting the machine automatically if one is required (useful in CI/CD pipelines). /passive is a middle ground that shows a minimal progress bar but no interactive dialogs.

Passing custom properties

MSI installers often expose public properties that control installation behavior. For example, Python's MSI installer accepts PrependPath=1 to add Python to PATH:

msiexec /i python-3.14.3-amd64.msi /quiet InstallAllUsers=1 PrependPath=1

DevTools Installer uses properties like this internally in the Python integration to ensure PATH is configured correctly without requiring the user to check any boxes.

Tools installed by DevTools Installer using MSI

Java JDK, Yarn, AWS CLI, Azure CLI, Chocolatey, Git, and Maven all use MSI-based installers, making them straightforward to automate with msiexec.

NSIS Installers — Nullsoft Scriptable Install System

NSIS is a widely used open-source installer framework originally developed by Winamp's creator, Nullsoft. Many popular tools distribute their Windows installers as NSIS-based EXE files, including Miniconda/Anaconda, some versions of Node.js, and parts of Git for Windows.

NSIS installers are wrapped EXE files. Unlike MSI packages, they are not passed to msiexec — you run them directly. The silent install flag is:

installer.exe /S

Note the uppercase /S — NSIS is case-sensitive on this flag. A lowercase /s will not work.

Custom install directory

installer.exe /S /D=C:\CustomInstallPath

The /D= switch overrides the default install directory. It must come last on the command line, and the path must not be quoted even if it contains spaces.

Miniconda — NSIS with custom properties

Miniconda uses an NSIS-based installer with additional custom properties:

Miniconda3-latest-Windows-x86_64.exe /InstallationType=AllUsers /AddToPath=0 /RegisterPython=0 /S /D=C:\ProgramData\miniconda3

DevTools Installer uses this exact command internally, with AddToPath=0 because it configures the PATH entries itself through the Windows API rather than relying on the installer to do so — ensuring the correct three conda directories are added in the right order.

Inno Setup Installers

Inno Setup is another widely used installer framework, common for smaller and open-source Windows applications including Notepad++, Gradle, and many others. Inno Setup installers are also EXE files run directly, but with different flags than NSIS:

installer.exe /SILENT          ; shows progress window, no questions
installer.exe /VERYSILENT     ; completely headless, no windows at all
installer.exe /SUPPRESSMSGBOXES  ; suppresses any error message boxes

Unlike NSIS, these flags are case-insensitive. The distinction between/SILENT and /VERYSILENT matters in CI/CD: the former shows a progress window (which may cause issues in headless environments), while the latter runs completely invisible.

Custom directory

installer.exe /VERYSILENT /DIR="C:\CustomInstallPath"

Notepad++ example

npp.8.9.3.Installer.x64.exe /S

Notepad++ uses Inno Setup but accepts the NSIS-style /S for compatibility. When there is ambiguity, check the installer's documentation or run installer.exe /? to see the supported flags.

Squirrel-Based Installers

GitHub Desktop, Postman, VS Code, and Slack use a framework called Squirrel, which is common for Electron-based applications. Squirrel installs to the user's own profile directory (%LOCALAPPDATA%), which is why these apps do not require administrator privileges.

Squirrel-based installers use the --silent flag (with double dashes):

GitHubDesktopSetup-x64.exe --silent PostmanSetup-x64.exe --silent

One complexity: Squirrel installers often auto-launch the application after installation. DevTools Installer handles this by detecting and closing any auto-launched application windows after the installer finishes.

How DevTools Installer Uses Silent Installs

DevTools Installer knows the installer type (MSI, NSIS, Inno Setup, Squirrel, or zip archive) for each of the 20+ supported tools, along with the exact silent flags needed for that specific tool version. When you click "Install Selected," the following happens:

1. The installer binary is downloaded from the official publisher's server and saved to a temporary directory.
2. The installer is launched with the appropriate silent flag for its type — msiexec /i ... /quiet for MSI, setup.exe /S for NSIS, etc.
3. DevTools Installer monitors the process and waits for it to exit. The exit code is checked — a non-zero exit code indicates failure and is reported to the user.
4. After the installer exits, DevTools Installer configures environment variables through the Windows API (for tools that don't configure their own PATH), then runs the tool's verification command to confirm the installation succeeded.

For zip-archive tools (Maven, Gradle, Helm, kubectl, Istio), there is no installer at all — DevTools Installer extracts the archive to the target directory and sets up all environment variables manually.

Quick Reference — Silent Install Switches