← Back to Virtuworks Autopilot
Silent install command for Virtuworks Autopilot 2.0.123
The exact silent switches the Virtuworks Autopilot installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.
One-line silent install (x64)
msiexec.exe /i Virtuworks-Autopilot-2.0.0-x64.msi /qn
Run from the directory containing Virtuworks-Autopilot-2.0.0-x64.msi. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | - | MSI | Declared by publisher | |
| x86 | - | MSI | Declared by publisher | |
| neutral | - | 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 Virtuworks Autopilot?
Virtuworks Autopilot uses MSI. After downloading the installer, run: msiexec.exe /i Virtuworks-Autopilot-2.0.0-x64.msi /qn. The silent install switches are /qn.
How do I deploy Virtuworks Autopilot via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id Virtuworks.MSPControlAutopilot --exact 2.0.123 --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 MSI" come from the installer framework's documented defaults.
Prefer the winget route? See the full Virtuworks Autopilot install page.