Silent Install Switches Explained MSI Quiet NSIS and Inno Setup
Every automatic installation stands or falls on one small detail - the silent switch. Get it right and forty PCs install themselves; get it wrong and forty setup windows open at once.
✍️ Technical Anshu🪟 Windows⏱️ 7 minute read
🎥 Watch all three methods side by side in the full video
A silent switch is a command-line instruction that tells an installer to run with no windows and no questions. The catch everyone discovers the hard way: there is no single universal switch. The right one depends on which installer technology built the file - MSI, NSIS, Inno Setup or InstallShield each speak a different dialect. This guide shows how to identify the type, the standard switch for each, and how professionals test before deploying.
The Usual Switches by Installer Type (typical, not guaranteed)
InstallShield (setup.exe)/s (often with a recorded answer file)
These are the standard documented switches for each technology - the app publisher can still customise or ignore them.
Same goal, four dialects - identify the installer type first, then pick the switch
1
MSI Files - The Well Behaved Standard
MSI installs run through msiexec, never by double-clicking in a deployment
Standard silent install: msiexec /i "app.msi" /quiet /norestart - /quiet shows no interface at all, and /norestart stops a surprise reboot
Silent uninstall is the mirror: msiexec /x "app.msi" /quiet /norestart
Useful middle setting: /passive shows only a progress bar - handy while testing, wrong for mass deployment
2
EXE Files - Identify the Maker, Then the Switch
Right-click the EXE → Properties → Details. A mention of Nullsoft means NSIS - its silent switch is a capital /S, and it is case-sensitive
Inno Setup installers (very common for free utilities) use /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
InstallShield wrappers typically use /s, sometimes needing a recorded response file created once with setup.exe /r
Many installers answer /? or /help with their own supported switches - try it on a test PC before believing any list, including this one
3
Test Like a Professional Before Any Rollout ⭐
On one spare PC, run your exact command from an admin command prompt - not by double-clicking
Success looks like this: nothing appears on screen, the app is present afterwards, and the command's exit code is 0
Add /log for MSI tests (msiexec /i "app.msi" /quiet /norestart /log C:\install.log) so failures explain themselves
Only after a clean silent test does the command go into a winget script, a batch file or an Endpoint Central package
⚠️ The honest truth: some publishers deliberately block silent installation in free editions, and some custom installers ignore every standard switch. When that happens the answer is not a cleverer switch - it is the publisher's enterprise installer, a different tool, or accepting a manual install for that one app.
🎥 Watch the Full Comparison
In the video, one package fails loudly with the wrong switch and then installs invisibly with the right one - the difference is exactly this page.
Check Properties → Details for Nullsoft (NSIS) or Inno hints, try running it with /? to see if it documents switches, and watch its setup window style during a manual install - Inno and InstallShield have recognisable looks. When in doubt, test the common switches on a spare PC.
What does exit code 1603 mean during a silent MSI install?
A generic fatal error from Windows Installer. The /log file gives the real reason - common ones are a broken previous version still present, a missing prerequisite like a specific .NET runtime, or insufficient rights.
Does winget need me to know these switches?
Mostly no - winget manifests already carry the silent switches for catalogue apps, which is one of its conveniences. You need this knowledge for your own installers, scripts and deployment packages.
This guide is based on the Technical Anshu video on automatic software installation • Stuck on a step? Ask in the video comments and you will get a reply 🙏