> 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/manual-installation/windows-stealth.md).

# Windows Stealth Installation

Install We360.ai MyZen Stealth agent on Windows — silent employee monitoring setup with background service deployment.

## Prerequisites

| Requirement      | Detail                                                               |
| ---------------- | -------------------------------------------------------------------- |
| **OS**           | Windows 10 or later                                                  |
| **Admin rights** | **Required** for Stealth mode                                        |
| **Antivirus**    | Add an exception for the MyZen stealth process and install directory |

{% hint style="danger" %}
**Never rename the stealth installer file.** The encoded filename contains your organization's license key and configuration. Renaming it or allowing extra characters to be appended (e.g. `(1)` from duplicate downloads) will cause the installation to fail. Use the file exactly as downloaded.
{% endhint %}

## Download the Installer

1. Log in to the We360.ai web portal as an administrator.
2. Click the **Download Apps** button in the top bar.
3. In the **Windows** section, click **Stealth** to download the installer (filename is a Base64-encoded string ending in `.exe`).

## Install

1. Locate the setup file (e.g. `<encoded-name>.exe`) in your Downloads folder and double-click it.
2. A Windows SmartScreen dialog appears. Click **More info**.
3. Click **Run anyway** to continue.
4. A UAC prompt appears. Click **Yes** to confirm and start installation.
5. The installer runs silently. No application window opens because MyZen is in stealth mode.

### Post-Installation Notes

* Stealth mode does not show a visible application or system tray icon to the employee.
* Consider clearing browser download history on the target machine if confidentiality is required.

## Install Locations (Reference)

| Item                  | Path                                 |
| --------------------- | ------------------------------------ |
| Application directory | `C:\Program Files\zs\zs\`            |
| Version file          | `C:\Program Files\zs\zs\version.txt` |
| Process name          | `MyZenV2s.exe`                       |
| Background service    | `zsrvc`                              |
| Watchdog service      | `C:\Windows\svcmonitor.exe`          |
| Service host process  | `C:\Windows\svcrunner.exe`           |

{% hint style="info" %}
Both `svcmonitor` and `svcrunner` run as **Local System**. `svcmonitor` is a watchdog that automatically restarts the agent if terminated. `svcrunner` is the Windows service host.
{% endhint %}


---

# 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/manual-installation/windows-stealth.md?ask=<question>&goal=<user_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.