← Back to Plume
Silent install command for Plume 0.1.0
The exact silent switches the Plume 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)
Plume_0.1.0_x64-setup.exe /S
Run from the directory containing Plume_0.1.0_x64-setup.exe. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x86 | user | EXE | Declared by publisher |
- 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 Plume?
Plume uses EXE. After downloading the installer, run: Plume_0.1.0_x64-setup.exe /S. The silent install switches are /S.
How do I deploy Plume via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id b7s.Plume --exact 0.1.0 --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.
Where do these silent switches come from?
The switches marked "Declared by publisher" come from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs. Switches marked "Default for EXE" come from the installer framework's documented defaults.
Prefer the winget route? See the full Plume install page.