← Back to WinSCP Beta
Silent install command for WinSCP Beta 6.6.1.beta
The exact silent switches the WinSCP Beta installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.
One-line silent install (x86, user scope)
installer.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /CURRENTUSER
Run from the directory containing installer.exe. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x86 | user | EXE Inno Setup | Custom: /CURRENTUSER | Default for Inno Setup |
| x86 | machine | EXE Inno Setup | Custom: /ALLUSERS | Default for Inno Setup |
| x86 | machine | MSI WiX | Default for WiX (MSI) |
- Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
- Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g.
/Sfor NSIS,/quiet /norestartfor MSI).
Frequently asked questions
What is the silent install command for WinSCP Beta?
WinSCP Beta uses EXE (Inno Setup). After downloading the installer, run: installer.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /CURRENTUSER. The silent install switches are /VERYSILENT /SUPPRESSMSGBOXES /NORESTART.
How do I deploy WinSCP Beta via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id WinSCP.WinSCP.Beta --exact 6.6.1.beta --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.
Prefer the winget route? See the full WinSCP Beta install page.