Silent install command for Araxis Merge 2026.0

The exact silent switches the Araxis Merge 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, user scope)

msiexec.exe /i Merge2026.0-x64.msi /quiet /norestart ALLUSERS=2 MSIINSTALLPERUSER=1

Run from the directory containing Merge2026.0-x64.msi. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x64	user	MSI	Custom: ALLUSERS=2 MSIINSTALLPERUSER=1	Default for MSI
x64	user	MSI	Custom: ALLUSERS=2 MSIINSTALLPERUSER=1	Default for MSI
x64	machine	MSI		Declared by publisher
x64	machine	MSI		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. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for Araxis Merge?

Araxis Merge uses MSI. After downloading the installer, run: msiexec.exe /i Merge2026.0-x64.msi /quiet /norestart ALLUSERS=2 MSIINSTALLPERUSER=1. The silent install switches are /quiet /norestart.

How do I deploy Araxis Merge via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Araxis.Merge --exact 2026.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 MSI" come from the installer framework's documented defaults.

Prefer the winget route? See the full Araxis Merge install page.