> 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/deploy/agent-deployment-hub/download-links.md). # Download Links Download We360.ai MyZen agent installers and utilities for Windows, macOS, Linux, Android, iOS, and Chrome. Get direct download links for employee monitoring software deployment. All We360.ai agent downloads are available from `https://portal.we360.ai`. Use this page to download MyZen installers and deployment utilities for Windows, macOS, Linux, Android, iOS, and Chrome. It includes direct download links for EXE, MSI, PKG, DMG, shell, and cleanup tools used in employee monitoring software deployment. Administrators can open the Download page from the **Download Apps** button in the top bar. After downloading, confirm the file is genuine and complete with [Verify Downloaded Installers](/deployment-and-it-ops/deploy/agent-deployment-hub/verify-downloads.md). For step-by-step setup, use [Manual Installation](/deployment-and-it-ops/deploy/agent-deployment-hub/manual-installation.md), [Command Line / MSI / EXE](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/command-line-msi.md), or [Direct Link](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/direct-link.md). The following tables list all available We360.ai download links and utilities. ## Desktop Agent Downloads
PlatformTypeFormatDirect Download
:windows: WindowsStandardEXEMyZenV2-setup.exe
:windows: WindowsStandardMSIMyZenV2.msi
:windows: WindowsStealth*EXEzs-setup.exe
:windows: WindowsStealth*MSIzs.msi
:apple: macOS (Intel)StandardPKGMyZenV2-amd64.pkg
:apple: macOS (Intel)StandardDMGMyZenV2-amd64.dmg
:apple: macOS (Apple Silicon)StandardPKGMyZenV2-arm64.pkg
:apple:macOS (Apple Silicon)StandardDMGMyZenV2-arm64.dmg
:apple:macOS (Intel)Stealth*PKGzs-amd64.pkg
:apple:macOS (Apple Silicon)Stealth*PKGzs-arm64.pkg
:ubuntu: Ubuntu (64-bit Intel)Stealth*SHzs-amd64.sh
{% hint style="info" %} * Organization-specific Stealth downloads require **Tenant Owner** permissions. Standard EXE downloads are available to authenticated users. The generic Stealth links below don't include your organization's configuration. {% endhint %} {% hint style="danger" %} **Prepare generic Stealth downloads before deployment.** They don't contain your organization's license configuration. Follow [Stealth installer preparation](#important-notes-for-stealth-installer-downloads); an organization-specific installer downloaded from the portal must keep its original filename. {% endhint %} ## Mobile App Downloads | Platform | Link | | -------- | ------------------------------------------------------------------------------------------ | | Android | [Google Play Store](https://play.google.com/store/apps/details?id=com.zenstack.we360.ai) | | iOS | [Apple App Store](https://apps.apple.com/in/app/we360-ai-workforce-analytics/id6455370600) | ## Browser Extension Download | Browser | Link | | ------- | ----------------------------------------------------------------------------------------------------------------------- | | Chrome | [Chrome Web Store](https://chromewebstore.google.com/detail/we360ai-workforce-product/eainhghihghonimoemjhiimpkfejkgbd) | ## Deployment and Cleanup Utilities Use these utilities for scripted installation, deep cleanup, macOS uninstall, and Windows installation and GPO package troubleshooting. | Utility | Platform | Architecture | Direct Download | | ------------------------------------------- | --------------------- | ------------ | ------------------------------------------------------------------------------------- | | **macOS Uninstall (pkg)** | macOS | Universal | [zen-uninstall.pkg](https://portal.we360.ai/static/installers/zen-uninstall.pkg) | | **Zen Cleanup Utility** | Windows | amd64 | [zen\_cleanup.exe](https://portal.we360.ai/static/utils/windows/zen_cleanup.exe) | | **Zen Cleanup Utility** | macOS (Intel) | amd64 | [zen\_cleanup](https://portal.we360.ai/static/utils/mac_amd64/zen_cleanup) | | **Zen Cleanup Utility** | macOS (Apple Silicon) | arm64 | [zen\_cleanup](https://portal.we360.ai/static/utils/mac_arm64/zen_cleanup) | | **Zen Cleanup Utility** | Linux | amd64 | [zen\_cleanup](https://portal.we360.ai/static/utils/linux_amd64/zen_cleanup) | | **Zen Cleanup Utility** | Linux | arm64 | [zen\_cleanup](https://portal.we360.ai/static/utils/linux_arm64/zen_cleanup) | | **Zen Online Installer (zs\_manager)** | Windows | amd64/arm64 | [zs\_manager.exe](https://portal.we360.ai/static/utils/windows/zs_manager.exe) | | **Powershell Stealth Install Script (PS1)** | Windows | amd64/arm64 | [MyZenInstall.ps1](https://portal.we360.ai/static/scripts/MyZenInstall.ps1) | | **Installation Debugger** | Windows | amd64/arm64 | [test-msi.ps1](https://portal.we360.ai/static/scripts/test-msi.ps1) | | **GPO MSI Package Diagnostic (PS1)** | Windows | amd64/arm64 | [msi-gpo-diagnose.ps1](https://portal.we360.ai/static/scripts/msi-gpo-diagnose.ps1) | | **macOS Stealth Install Script (Shell)** | macOS (All) | amd64/arm64 | [zs-macos.sh](https://portal.we360.ai/static/scripts/zs-macos.sh) | | **macOS Uninstall Script (Shell)** | macOS (All) | amd64/arm64 | [zs-uninstall-macos.sh](https://portal.we360.ai/static/scripts/zs-uninstall-macos.sh) | ### PowerShell Stealth install helper Download [MyZenInstall.ps1](https://portal.we360.ai/static/scripts/MyZenInstall.ps1), save a local copy, and have your deployment administrator review it before use. Use this portal-hosted helper rather than an older pinned gist. It's for the Stealth EXE, not a general-purpose Standard installer. Configure these values in your reviewed copy: | Setting | Value | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `$DownloadUrl` | `https://portal.we360.ai/static/installers/zs-setup.exe` for the generic Windows Stealth EXE | | `$InstallerName` | Your exact organization-specific EXE filename, including `.exe`, obtained through [Stealth installer preparation](#important-notes-for-stealth-installer-downloads) | The source URL and saved filename serve different purposes. The helper downloads the generic binary and saves it under `$InstallerName`. Leaving the generic filename `zs-setup.exe` isn't sufficient to configure a fresh computer for your organization. Protect the organization-specific filename as license information. The current Stealth EXE uses `--silent`. If your downloaded helper still passes `/exenoui /quiet`, replace its installer-launch statement with the following in your reviewed local copy: ```powershell $process = Start-Process -FilePath $tempFile -ArgumentList '--silent' -Wait -PassThru -NoNewWindow ``` Keep the surrounding download, organization configuration, and result handling. For a custom installer log path, use the [EXE logging command](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/command-line-msi.md#install-with-logging-for-troubleshooting). Changing these arguments doesn't make the helper safe for recurring installation. Use **Windows PowerShell 5.1** with administrative privileges or SYSTEM. Check download access in that context and follow your organization's script-signing and execution policies. For distribution and task configuration, see [Active Directory GPO](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/active-directory-gpo.md#alternative-deployment-through-a-group-policy-preferences-task). {% hint style="warning" %} **Don't run this helper unchanged on a recurring schedule or every startup.** It defaults to forced installation, checks installed products using `Win32_Product`, and reports every nonzero EXE exit code as a failure. Setting `$ForceInstall` to `$false` alone doesn't make it safe to repeat: the product check is broad and still runs. The supplied helper also attempts to set a process-scoped execution-policy bypass. Review that behavior against your organization's policy before approving the script. Before recurring deployment, your administrator must review detection of the intended installation, repeat-run behavior, and the installer's result codes. `Win32_Product` queries can trigger MSI consistency checks and repairs; see [Microsoft's guidance](https://learn.microsoft.com/en-us/troubleshoot/windows-server/admin-development/windows-installer-reconfigured-all-applications). Pilot a one-time deployment and verify installation separately from script completion. {% endhint %} ### macOS Stealth install helper Download [zs-macos.sh](https://portal.we360.ai/static/scripts/zs-macos.sh) and review it before use. It downloads the generic Stealth PKG for the detected Mac architecture, saves it under `INSTALLER_NAME`, then runs the macOS installer with `sudo`. For a new Mac, the installer needs your tenant configuration. In the downloaded script, set `INSTALLER_NAME` to the exact organization-specific filename from the portal, including `.pkg`. The tenant-specific filename contains the configuration the installer needs. Treat this filename as a credential. Keep it private and remove duplicate-download suffixes such as `(1)`. The helper writes to `/tmp/$INSTALLER_NAME` and expects the filename alone. If the portal filename contains a path separator, don't use this helper. Use a managed installation method that supplies tenant configuration through a separate step, such as the [MDM configuration procedure](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/macos-mdm/filename-independent-config.md). Run the reviewed script from Terminal as a signed-in administrator who can use `sudo`: ```bash /bin/bash ./zs-macos.sh ``` The supplied script defaults `FORCE_INSTALL=true`, so it attempts installation even when it detects an existing Stealth app. Review this behavior before using it on a managed or already-installed Mac. The helper installs immediately after downloading and doesn't verify the package's signature or checksum first. If your process requires verification before installation, download the package to an approved location and follow [Verify Downloaded Installers](/deployment-and-it-ops/deploy/agent-deployment-hub/verify-downloads.md). Then use an approved installation method. For MDM, follow the MDM-specific procedure instead of using this interactive helper unchanged. After installation, verify the tenant and agent status using [macOS Installation Validation](/deployment-and-it-ops/deploy/agent-deployment-hub/manual-installation/macos-validation.md). A successful installer exit alone doesn't prove that the device enrolled to the intended organization. The helper installs Stealth only. It doesn't install the Standard app. **Zen Online Installer (zs\_manager) -** A web-installer utility: resolves the correct agent installer for the machine's tenant, downloads it, and installs it silently (`/updater-standard` or `/updater-stealth`, with a `--dry-run` mode). Work in progress — intended for support and IT tooling, not end users. See [Agent Runtime & Update Reference](/deployment-and-it-ops/deploy/agent-runtime-update.md#zs_manager-online-installer-utility-windows). ### GPO MSI Package Diagnostic Download and review [msi-gpo-diagnose.ps1](https://portal.we360.ai/static/scripts/msi-gpo-diagnose.ps1). Run it from an elevated Windows PowerShell session using the account that runs Group Policy Management. Example: `.\msi-gpo-diagnose.ps1 -MsiPath '\\server\share\installer.msi'`. It compares opening the MSI over the supplied path and from a temporary local copy; the checks are diagnostic clues, not proof that a file is valid, corrupt, or blocked. See [Active Directory GPO troubleshooting](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/active-directory-gpo.md#cant-add-the-package-in-group-policy-management) for result interpretation and safe evidence sharing. **Zen Cleanup -** Completely removes all MyZen traces from a system, including registry entries, launch agents/daemons, processes, and application files. Use only when you want a full removal of everything related to MyZen. {% hint style="warning" %} The **Zen Cleanup Utility** performs a deep clean and removes all MyZen-related files, processes, and configuration. Only use it if you intend to completely remove MyZen from the system. It cannot be undone. {% endhint %} ## Desktop Doctor Downloads Desktop Doctor is a diagnostic utility for troubleshooting agent issues. Run it on any affected machine to check network connectivity, AV interference, agent status, and collect logs for support. See [Desktop Doctor](/deployment-and-it-ops/troubleshoot-support/desktop-doctor.md) for usage instructions. | Platform | Download | | --------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Windows | [Desktop-Doctor.exe](https://portal.we360.ai/static/desktop-doctor/windows-gui/Desktop-Doctor.exe) | | macOS (Apple Silicon) | [Desktop-Doctor.app.zip](https://portal.we360.ai/static/desktop-doctor/darwin-gui/darwin-arm64/Desktop-Doctor.app.zip) | | macOS (Intel) | [Desktop-Doctor.app.zip](https://portal.we360.ai/static/desktop-doctor/darwin-gui/darwin-amd64/Desktop-Doctor.app.zip) | | Linux (x86\_64) | [Desktop-Doctor-x86\_64.AppImage](https://portal.we360.ai/static/desktop-doctor/linux-gui/Desktop-Doctor-x86_64.AppImage) | *** ## Important Notes for Stealth Installer Downloads ### Organization-specific portal download The recommended source is your organization's Stealth installer from **Download Apps** in the portal, using a **Tenant Owner** account. Preserve the full filename exactly as downloaded. Don't replace it with a friendly name or allow duplicate-download suffixes such as `(1)` or `(2)`. ### Generic public download The generic Stealth EXE, PKG, and shell downloads don't contain your organization's license configuration. An authorized administrator must prepare them before installation: 1. Obtain the organization-specific installer filename or Stealth key from your organization's portal download. If you can't obtain it, contact support; don't guess a key or reuse another organization's installer. 2. Save the generic file using the organization's exact license-bearing filename and the matching extension. For the Windows helper, set `$InstallerName` to that EXE filename instead of renaming the downloaded script. 3. Verify the file and pilot installation and reporting on a fresh computer. After preparation, preserve the configured filename throughout distribution. {% hint style="danger" %} **Preserve the organization-specific Stealth installer filename.** Its name is tied to your organization's license. Don't give a portal download or prepared installer a different name, and don't allow duplicate-download suffixes such as `(1)` or `(2)`. A generic public download must first receive your organization's filename or configuration through [Stealth installer preparation](https://github.com/zenstack-we360/documentation/tree/main/docs-we360-ai/it-ops/deployment/agent-deployment-hub/download-links.md#important-notes-for-stealth-installer-downloads). {% endhint %} * Stealth installers should not be shared directly with employees, as they may extract the embedded license key or misuse the installer. * For stealth deployments, prefer administrator-controlled methods: GPO, Intune, MDM, or command-line installation. [^1]: Generic Stealth downloads require organization-specific preparation before use on a fresh computer. [^2]: (Save the file if not downloaded automatically) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/download-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.