← Back to axesWord
Silent install command for axesWord 26.0.0.0
The exact silent switches the axesWord 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)
msiexec.exe /i axesWord.Setup.26_0_0.exe /quiet /norestart ACCEPT_AXES4_EULA=1
Run from the directory containing axesWord.Setup.26_0_0.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 Burn bundle | Custom: ACCEPT_AXES4_EULA=1 | Default for Burn (WiX bundle) |
- 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 axesWord?
axesWord uses EXE (Burn bundle). After downloading the installer, run: msiexec.exe /i axesWord.Setup.26_0_0.exe /quiet /norestart ACCEPT_AXES4_EULA=1. The silent install switches are /quiet /norestart.
How do I deploy axesWord via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id axes4.axesWord --exact 26.0.0.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 axesWord install page.