> 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/troubleshoot-support/desktop-doctor.md).

# Desktop Doctor

Desktop Doctor is a diagnostic utility for IT administrators to triage We360 agent issues — network connectivity, AV/EDR interference, agent process status, database health, and log collection.

Desktop Doctor runs directly on the affected machine to inspect network connectivity, SSL/TLS interception, antivirus detection, agent processes, and local database health. It can collect available logs into a ZIP for support. Collection is best-effort: permissions, retention, selected options, and the Doctor version affect which evidence is available.

**Use it whenever an agent issue cannot be resolved from the admin portal alone, or before escalating any support ticket.**

***

## Download

Download the file for your platform and send it to the affected machine. No installation is required — it runs as a standalone executable.

| 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) |

***

## Running the app

{% tabs %}
{% tab title="Windows" %}
Double-click `Desktop-Doctor.exe`.

If a Windows security warning appears, verify the download source and ask your IT administrator to review the exact warning before approving execution. SmartScreen reputation warnings, Smart App Control, application-control policies, and antivirus blocks are different controls. Don't disable protection or assume that every warning offers an approved **Run anyway** option. Retain the warning text and any security-product event for support.

For protected event logs or computer-scope policy reporting, an authorized administrator may need to right-click the verified executable and select **Run as administrator**. A standard-user run can still provide permitted evidence, but denied checks are unavailable—not proof that an app or policy is absent. Don't grant employees local administrator rights just to collect diagnostics. If another administrator account is used, record that account context; its user-specific settings and logs aren't the affected employee's.
{% endtab %}

{% tab title="macOS" %}
macOS blocks apps from unidentified developers by default. Use one of these methods:

**Option 1 — Right-click to open (easiest)**

1. Unzip `Desktop-Doctor.app.zip`
2. Right-click `Desktop-Doctor.app` → **Open**
3. In the dialog, click **Open**

**Option 2 — System Settings bypass**

1. Unzip and attempt to open the app — macOS will block it
2. Open **System Settings → Privacy & Security**
3. Scroll to the Desktop Doctor entry → click **Open Anyway**

**Option 3 — Terminal (if the above don't work)**

```bash
unzip ~/Downloads/Desktop-Doctor.app.zip -d ~/Downloads
xattr -cr ~/Downloads/Desktop-Doctor.app
open ~/Downloads/Desktop-Doctor.app
```

{% endtab %}

{% tab title="Linux" %}
The Linux build is a single-file **AppImage** — no extraction or installation. Make it executable, then run it:

```bash
chmod +x Desktop-Doctor-x86_64.AppImage
./Desktop-Doctor-x86_64.AppImage
```

Needs a 64-bit Linux desktop with a graphical session (Ubuntu 22.04, Debian 12, Fedora 36, or newer). If it doesn't open when double-clicked from a file manager, launch it from a terminal with the commands above.

{% hint style="info" %}
On a headless server (no desktop), use the command-line build instead — ask We360 support for the `doctor-cli` download link. It runs every check from the terminal and has no graphical requirements.
{% endhint %}
{% endtab %}
{% endtabs %}

***

## Tabs reference

Click **Run** on any tab to start its checks. Each tab is independent — you can run them in any order.

| Tab                      | What it checks                                                                  | When to use                                                                                         |
| ------------------------ | ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Net Check**            | DNS resolution, TCP connectivity, and HTTP reachability for all We360 endpoints | First stop — rules out firewall and proxy issues                                                    |
| **SSL/TLS**              | Certificate validity, proxy/MITM interception, TLS version support              | Run if Net Check passes but data still isn't syncing                                                |
| **AV/Firewall Check**    | Detected antivirus, EDR agents, VPN clients, proxies, and MDM profiles          | Confirms which security software is present before adding exclusions                                |
| **Processes**            | Whether the agent processes are currently running and their file paths          | Quickly confirm the agent is alive vs. stopped or missing                                           |
| **Database**             | Local event count, synced vs. unsynced state, and tenant identity               | Determine whether events are being captured but not uploaded (network issue) or not captured at all |
| **Misc**                 | System clock accuracy, package health, display server                           | Use when you suspect a clock skew, OS-level, or Linux display issue                                 |
| **Logs/Files Collector** | Collects available selected logs into a ZIP for support                         | Review collection errors and missing evidence before escalation                                     |

{% hint style="info" %}
**Interpreting Database results:** If the Database tab shows a large number of unsynced events, the agent is capturing data but cannot upload it — the problem is network or authentication, not the tracker itself. If event count is zero or very low despite the machine being in active use, the tracker subsystem may have stopped.
{% endhint %}

***

## When a Windows policy deployment hasn't completed

Start with the [GPO troubleshooting guide](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/active-directory-gpo.md#troubleshooting). Collect the [computer-policy report and deployment events](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/active-directory-gpo.md#collect-evidence-for-support) before changing the policy or manually installing software. If `gpresult` returns Access Denied, follow the guide's [administrator reporting steps](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/active-directory-gpo.md#gpresult-returns-access-denied).

Missing application logs don't prove that the MSI never ran: it may have failed before application startup or rolled back. An applied policy, installer execution, installed files, a running service, and reporting for the intended user are separate checks. Use [Windows Installation Validation](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/manual-installation/windows-validation.md) after installation; use Windows policy and installer events to investigate the installation attempt itself.

Don't assume a Doctor ZIP includes the GroupPolicy Operational channel, a computer-scope policy report, or every installer log. Check what was collected and add the manual exports requested by support. The [installer-log reference](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-runtime-update.md#log-and-data-locations-windows) distinguishes installer logs from application and service logs.

***

## Collecting and sharing logs

The **Logs/Files Collector** creates a ZIP of the selected evidence it can read. Creating a ZIP doesn't establish that collection was complete. Retain collection warnings and tell support which inputs were missing, denied, or unreadable.

{% stepper %}
{% step %}

### Open Logs/Files Collector tab

Select the evidence requested by support. Include app and system logs when relevant; don't collect unrelated data by default.
{% endstep %}

{% step %}

### Click Create ZIP

The ZIP is saved automatically to the user's **Downloads** folder. The filename includes a timestamp and session ID.
{% endstep %}

{% step %}

### Share with support

Review the archive before sharing. Logs, configuration snapshots, databases, and installer filenames can contain organization configuration, license information, or personal data. Don't assume complete redaction. Remove sensitive or unrelated material and tell support what you omitted. Share through your approved private support channel, using only a support-provided upload address or ticket.
{% endstep %}
{% endstepper %}

Archive contents depend on the platform, Doctor version, selected options, and checks actually run. **Run All** performs additional diagnostics; creating a Collector ZIP doesn't mean those checks ran or their results were included. Inspect the archive and collection output rather than assuming every item below is present:

{% tabs %}
{% tab title="Windows" %}

* Agent logs (Stealth and Standard paths)
* Antivirus, firewall, and scheduled task snapshots
* Root certificate store listing
* Listening ports and DNS/proxy configuration
* Available Windows Event Log files or excerpts; use the GPO guide for explicit deployment-event exports
  {% endtab %}

{% tab title="macOS" %}

* Agent logs (Stealth and Standard paths)
* Launch Agents and Daemons directory listing
* System extensions list
* launchctl service state
  {% endtab %}

{% tab title="Linux" %}

* Agent logs
* systemd unit and journal excerpts
* Network interface and DNS state
  {% endtab %}
  {% endtabs %}

***

## See also

* [Tracker Failure Diagnostic Guide](https://docs.we360.ai/deployment-and-it-ops/troubleshoot-support/tracker-failure-guide.md) — step-by-step resolution for the most common failure patterns
* [AV and EDR Exclusions](https://docs.we360.ai/deployment-and-it-ops/security-hardening/network-security-hardening/av-and-edr-exclusions.md) — what to allowlist after the AV/Firewall Check tab identifies interference
* [Download Links & Utilities](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/download-links.md) — all agent installers and cleanup utilities


---

# 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/troubleshoot-support/desktop-doctor.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.
