← Back to Azure Batch Explorer
Silent install command for Azure Batch Explorer 2.23.0
The exact silent switches the Azure Batch Explorer 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)
BatchExplorer.Setup.2.23.0-stable.1210.exe /S
Run from the directory containing BatchExplorer.Setup.2.23.0-stable.1210.exe. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | - | EXE NSIS | Default for NSIS (Nullsoft) |
- 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 Azure Batch Explorer?
Azure Batch Explorer uses EXE (NSIS). After downloading the installer, run: BatchExplorer.Setup.2.23.0-stable.1210.exe /S. The silent install switches are /S.
How do I deploy Azure Batch Explorer via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id Microsoft.Azure.BatchExplorer --exact 2.23.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.
Prefer the winget route? See the full Azure Batch Explorer install page.