← Back to xLights
Silent install command for xLights 2026.11
The exact silent switches the xLights 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, machine scope)
xLights64_2026_11.exe /sp- /verysilent /norestart
Run from the directory containing xLights64_2026_11.exe. Download the installer from the Direct link below first. Run an elevated terminal (Run as Administrator) for machine-scope installs.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | machine | EXE Inno Setup | 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 xLights?
xLights uses EXE (Inno Setup). After downloading the installer, run: xLights64_2026_11.exe /sp- /verysilent /norestart. The silent install switches are /sp- /verysilent /norestart.
How do I deploy xLights via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id xLightsSequencer.xLights --exact 2026.11 --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 (Inno Setup)" come from the installer framework's documented defaults.
Prefer the winget route? See the full xLights install page.