# How to Install openclaw-windows-node on Windows: Complete Setup Guide

> Install openclaw-windows-node on Windows with our complete guide. Download the x64 installer, run setup, and connect to a gateway for a swift, efficient installation.

- Repository: [openclaw/openclaw-windows-node](https://github.com/openclaw/openclaw-windows-node)
- Tags: how-to-guide
- Published: 2026-06-06

---

**Download the x64 installer from GitHub Releases, run it without administrative privileges, and follow the WinUI 3 onboarding wizard to provision a local WSL gateway or connect to a remote OpenClaw gateway.**

The openclaw-windows-node repository (also known as **OpenClaw Companion** or formerly "Molty") provides a WinUI 3 tray application that connects Windows PCs to OpenClaw gateways. To install openclaw-windows-node on Windows, you need Windows 10 (20H2) or Windows 11 plus the WebView2 Runtime, then execute the Inno Setup-based installer which automatically handles WSL provisioning and gateway registration.

## Prerequisites

Before installing, verify your system meets the base requirements:

- **Windows Version**: Windows 10 (20H2 or later) or Windows 11
- **WebView2 Runtime**: Pre-installed on Windows 11; if missing on Windows 10, download the [Evergreen Installer](https://developer.microsoft.com/microsoft-edge/webview2/) according to the [`docs/SETUP.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/docs/SETUP.md) specifications

The application architecture consists of three layers defined in [`docs/CONNECTION_ARCHITECTURE.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/docs/CONNECTION_ARCHITECTURE.md): **OpenClaw.Shared** (WebSocket transport), **OpenClaw.Connection** (gateway lifecycle and SSH tunneling), and **OpenClaw.Tray.WinUI** (the system-tray UI).

## Download the Installer

The latest stable release publishes architecture-specific installers as GitHub release assets. Most users require the **x64** version.

Use PowerShell to download the installer and checksum file:

```powershell
$url = "https://github.com/openclaw/openclaw/releases/latest/download/OpenClawCompanion-Setup-x64.exe"
$shaUrl = "https://github.com/openclaw/openclaw/releases/latest/download/OpenClawCompanion-SHA256SUMS.txt"
Invoke-WebRequest -Uri $url -OutFile "$env:USERPROFILE\Downloads\OpenClawCompanion-Setup-x64.exe"
Invoke-WebRequest -Uri $shaUrl -OutFile "$env:USERPROFILE\Downloads\OpenClawCompanion-SHA256SUMS.txt"

```

Verify the installer integrity before execution:

```powershell
Get-FileHash -Path "$env:USERPROFILE\Downloads\OpenClawCompanion-Setup-x64.exe" -Algorithm SHA256 |
  ForEach-Object { $_.Hash } |
  Find-String -Pattern (Get-Content "$env:USERPROFILE\Downloads\OpenClawCompanion-SHA256SUMS.txt")

```

## Run the Installer and Onboarding Wizard

Double-click the downloaded `.exe` or execute it from PowerShell. The installer defined in `installer.iss` runs **without admin rights** and offers optional desktop shortcuts and auto-start registration. If Windows SmartScreen appears, select **More info → Run anyway**.

Upon first launch, the onboarding wizard implemented in [`src/OpenClaw.SetupEngine/WizardSelection.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/src/OpenClaw.SetupEngine/WizardSelection.cs) initiates automatically when no saved gateway exists. The wizard flow includes:

1. **Welcome**: Choose *Install new WSL Gateway* (default) to provision locally, or *Advanced setup* for an existing remote gateway
2. **Capabilities**: Review Windows features (camera, screen capture, voice) to be enabled
3. **Local Setup**: The **Setup Engine** (`OpenClaw.SetupEngine`) creates a dedicated WSL distro named `OpenClawGateway` using the provisioning logic from `scripts/build-inno-local.ps1`
4. **Gateway Configuration**: Configure AI providers and personas if the gateway supports wizard-based setup
5. **Permissions**: Grant notification, camera, microphone, and location access when prompted
6. **Completion**: Enable *Launch at login* before finishing

The [`TrayExecutableResolver.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/TrayExecutableResolver.cs) file determines which executable (tray app, node, or MCP) to launch based on your settings.

## Verify the Connection

After the wizard completes, the tray icon (a lobster 🦞) appears in your system tray. The [`src/OpenClaw.Tray.WinUI/App.xaml.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/src/OpenClaw.Tray.WinUI/App.xaml.cs) file constructs the `GatewayRegistry` and `GatewayConnectionManager` to establish the link.

- **Green icon**: Connected successfully
- **Menu check**: Right-click the tray icon → **Settings** to confirm the gateway URL (typically `ws://localhost:18789` for local WSL gateways)

The [`ConnectionStateMachine.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/ConnectionStateMachine.cs) in `src/OpenClaw.Connection/Connection/` drives the connection state transitions displayed in the UI.

## Silent Installation and Automation

For enterprise deployment or automated setups, use the silent install flags defined in `installer.iss`:

```powershell
Start-Process -FilePath "$env:USERPROFILE\Downloads\OpenClawCompanion-Setup-x64.exe" `
    -ArgumentList "/VERYSILENT", "/NORESTART", "/MERGETASKS=CreateDesktopIcon,StartWithWindows" `
    -Wait

```

Open the companion via deep link:

```powershell
Start-Process "openclaw://chat"

```

Inspect the managed WSL gateway:

```powershell
wsl -l -v | Where-Object { $_ -match "OpenClawGateway" }
wsl -d OpenClawGateway -u openclaw

```

## Updating and Uninstallation

Updates are checked automatically, or you can manually download the latest installer from the releases page. To uninstall, navigate to **Settings → Apps → Installed apps**, locate *OpenClaw Companion*, and click **Uninstall**.

**Note**: Uninstallation does **not** remove configuration files. Delete `%APPDATA%\OpenClawTray\settings.json` and the identity files under `%APPDATA%\OpenClawTray\gateways\<id>\` manually if you require a complete reset.

## Summary

- **Install openclaw-windows-node on Windows** by downloading the x64 GitHub Release asset and running the Inno Setup installer without elevation.
- The **Setup Engine** automatically provisions a locked-down WSL distro (`OpenClawGateway`) or connects to existing remote gateways.
- Configuration persists in `%APPDATA%\OpenClawTray\` with per-gateway identities stored in subdirectories.
- Silent deployment uses `/VERYSILENT /NORESTART` flags defined in `installer.iss`.
- The **WinUI 3** tray application relies on [`WizardSelection.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/WizardSelection.cs) for onboarding and [`ConnectionStateMachine.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/ConnectionStateMachine.cs) for managing gateway connectivity.

## Frequently Asked Questions

### Does openclaw-windows-node require administrator privileges to install?

No. The installer runs without admin rights. However, if you choose to install the local WSL gateway, Windows may prompt for elevation during the WSL distro creation phase handled by `build-inno-local.ps1`.

### Where does the installer store gateway credentials and identity files?

The application stores per-gateway identity files under `%APPDATA%\OpenClawTray\gateways\<id>\` and global settings in `%APPDATA%\OpenClawTray\settings.json`. These persist after uninstallation and are managed by the `GatewayRegistry` class referenced in [`App.xaml.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/App.xaml.cs).

### Can I connect to a remote gateway instead of using the local WSL option?

Yes. During the onboarding wizard implemented in [`WizardSelection.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/WizardSelection.cs), select *Advanced setup* instead of *Install new WSL Gateway*. This bypasses the `scripts/build-inno-local.ps1` provisioning and allows you to specify an existing gateway WebSocket URL.

### What Windows versions are supported?

The application requires Windows 10 (20H2 or later) or Windows 11, plus the WebView2 Runtime. The WinUI 3 framework utilized by `OpenClaw.Tray.WinUI` depends on these base requirements as documented in [`docs/SETUP.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/docs/SETUP.md).