> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/deployment/agent-deployment-hub/mass-deployment/command-line-msi.md).

# Command Line / MSI / EXE

Our Windows installers come as both MSI and EXE packages . They can be deployed silently using `MSIEXEC` from an elevated Command Prompt, PowerShell, or any RMM tool with remote command-line access.

{% hint style="warning" %}
The MSI installer is absolutely not recommended unless you have no other choice. We recommend using the EXE installer to ensure that our app starts immediately after install and that the updates and installtions work properly (which has been found to be buggy with MSI setups)
{% endhint %}

## Prerequisites

* The installer file downloaded from the We360.ai portal (Stealth version recommended for silent deployment).
* An elevated (Run as Administrator) command prompt or PowerShell session on the target machine.

{% hint style="danger" %}
**Do not rename the stealth installer file.** The **stealth** installer filename is tied to your organization's license. Renaming it, or allowing extra characters to be appended (e.g. `(1)` or `(2)` from duplicate downloads), will cause the installation to fail.
{% endhint %}

## Silent Install

#### EXE

```powershell
> "C:\path\to\<installer-filename>.exe" /exenoui /qn
```

Replace `C:\path\to\<installer-filename>.exe` with the actual path and filename of your organization's EXE.

#### MSI

```powershell
MSIEXEC /i "C:\path\to\<installer-filename>.msi" /QN
```

Replace `C:\path\to\<installer-filename>.msi` with the actual path and filename of your organization's MSI.

## Silent Uninstall (MSI only)

```powershell
MSIEXEC /x "C:\path\to\<installer-filename>.msi" /QN
```

## Silent Uninstall (All Apps and Config)

* Download the zen-cleanup utility from here [Download Links & Utilities](/deployment-and-it-ops/deployment/agent-deployment-hub/download-links.md#utilities)
* Run the exe file via terminal with Administrator permissions.

## Install with Logging (for Troubleshooting)

If an installation fails, re-run with verbose logging enabled:

```
"C:\path\to\<installer-filename>.exe" /exenoui /qn /l*v %TEMP%\myzen-install.log
```

```powershell
MSIEXEC /i "C:\path\to\<installer-filename>.msi" /QN /l*v %TEMP%\myzen-install.log
```

Attach the generated log file (`%TEMP%\myzen-install.log`) when creating a support ticket.

## Usage with RMM / PSExec

These commands work with any tool that provides remote command-line access:

* **RMM tools** with remote shell (e.g. ConnectWise, Datto, NinjaRMM)
* **PSExec** for remote execution across the network
* **SCCM** task sequences

The command runs silently with no on-screen feedback. RMM tools may provide their own success/failure reporting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/deployment-and-it-ops/deployment/agent-deployment-hub/mass-deployment/command-line-msi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
