# How to Update OpenClaw-Windows-Node to the Latest Version: 3 Methods Explained

> Update OpenClaw-Windows-Node to the latest version with our guide. Discover three easy methods: in-app updates, manual download, or source builds.

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

---

**OpenClaw-Windows-Node supports automatic in-app updates, manual installer downloads, and source builds to ensure you always run the latest release.**

Updating the OpenClaw-Windows-Node client ensures you receive the latest tray features, security patches, and WSL gateway improvements. According to the `openclaw/openclaw-windows-node` source code, the project ships with three complementary update mechanisms designed for different deployment scenarios, all documented in the repository's [`README.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/README.md).

## Method 1: Automatic In-App Updates (Recommended)

The WinUI tray application implements an auto-update mechanism via the `CheckForUpdatesAsync` routine that queries the GitHub Releases API upon launch.

To update automatically:

1. Launch **OpenClaw Tray** by starting `OpenClaw.Tray.WinUI.exe`.
2. Wait for the background check—the app contacts the GitHub Releases API automatically.
3. Click the **Update** button when the toast notification appears.
4. The installer downloads and launches automatically (MSI/MSIX).
5. Relaunch the tray app to use the new version.

This behavior is documented in [`README.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/README.md) under the auto-updates section, which notes that the mechanism parses the latest release asset URLs to locate the appropriate installer.

## Method 2: Manual Download of Official Installers

For controlled deployments or offline installations, fetch the signed binaries directly from the OpenClaw releases page. The [`README.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/README.md) lists these links under the download section.

Download the appropriate installer for your architecture:

```text
https://github.com/openclaw/openclaw/releases/latest/download/OpenClawCompanion-Setup-x64.exe
https://github.com/openclaw/openclaw/releases/latest/download/OpenClawCompanion-Setup-arm64.exe

```

Installation steps:

1. Download via browser or use PowerShell: `Invoke-WebRequest -Uri "URL" -OutFile "setup.exe"`.
2. Run the installer—the wizard restores your previous settings automatically.
3. Complete the on-screen prompts.

## Method 3: Build and Install from Source

When you need a custom build (for example, to target a different .NET runtime or include local changes), use the provided `build.ps1` script located in the repository root.

Clone and build:

```powershell

# Clone the repository

git clone https://github.com/openclaw/openclaw-windows-node.git
cd openclaw-windows-node

# Run the build script for the host architecture

./build.ps1

```

For architecture-specific MSIX packages:

```powershell

# Build ARM64 MSIX package

dotnet build src/OpenClaw.Tray.WinUI/OpenClaw.Tray.WinUI.csproj -r win-arm64 -p:PackageMsix=true

# Build x64 MSIX package  

dotnet build src/OpenClaw.Tray.WinUI/OpenClaw.Tray.WinUI.csproj -r win-x64 -p:PackageMsix=true

```

Install the resulting package:

```powershell
Add-AppxPackage .\bin\Release\net6.0-windows10.0.19041.0\win-arm64\AppPackages\OpenClaw.Tray.WinUI_*.msixbundle

```

The `build.ps1` script orchestrates the restore, compile, and packaging steps according to the source implementation.

## Updating the WSL Gateway Component

If you maintain the optional WSL gateway, it updates automatically when you update the Windows node. The bundled gateway version is tied to the OpenClaw hub release.

To manually validate or update the gateway:

```powershell
./scripts/validate-wsl-gateway.ps1

```

The repository also includes a CI workflow at [`.github/workflows/gateway-lkg-update.yml`](https://github.com/openclaw/openclaw-windows-node/blob/main/.github/workflows/gateway-lkg-update.yml) that creates draft pull requests when newer upstream gateway versions are available, ensuring the bundled component stays current. Detailed administration instructions appear in [`docs/WSL_GATEWAY_ADMIN.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/docs/WSL_GATEWAY_ADMIN.md).

## Verifying Updates via CLI

The `OpenClaw.Cli` utility (located in `src/OpenClaw.Cli/`) provides programmatic access to update checks:

```bash

# Force a check-for-updates request (same logic as the tray)

dotnet run --project src/OpenClaw.Cli -- --check-updates

```

The CLI entry point in [`src/OpenClaw.Cli/Program.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/src/OpenClaw.Cli/Program.cs) implements this logic alongside other administrative functions.

## Summary

- **Automatic updates** offer the simplest path through the WinUI tray's `CheckForUpdatesAsync` routine, which polls the GitHub Releases API.
- **Manual installers** provide control over timing and offline deployment using official signed binaries (`OpenClawCompanion-Setup-x64.exe` or `arm64.exe`).
- **Source builds** allow customization via `build.ps1` and architecture-specific MSIX packaging using `dotnet build` with runtime identifiers.
- The **WSL gateway** updates automatically with the node, or manually via `validate-wsl-gateway.ps1`, with automation handled by [`gateway-lkg-update.yml`](https://github.com/openclaw/openclaw-windows-node/blob/main/gateway-lkg-update.yml).
- The **CLI tool** (`OpenClaw.Cli`) supports programmatic update verification as implemented in [`Program.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/Program.cs).

## Frequently Asked Questions

### How do I check my current OpenClaw-Windows-Node version?

Run the CLI helper with the `--version` flag or check the tray application properties. The `OpenClaw.Cli` project in [`src/OpenClaw.Cli/Program.cs`](https://github.com/openclaw/openclaw-windows-node/blob/main/src/OpenClaw.Cli/Program.cs) implements version reporting alongside the `--check-updates` functionality, allowing you to verify your installed release against the latest GitHub tag.

### Will updating remove my existing configuration?

No. Both the automatic updater and manual installers preserve user settings. According to the [`README.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/README.md), the installation wizard restores your previous settings automatically during the upgrade process, ensuring continuity across versions.

### Can I update the WSL Gateway separately from the Windows Node?

While the gateway typically updates automatically with the Windows node, you can validate and update it manually using the `./scripts/validate-wsl-gateway.ps1` script. The repository also maintains a CI workflow at [`.github/workflows/gateway-lkg-update.yml`](https://github.com/openclaw/openclaw-windows-node/blob/main/.github/workflows/gateway-lkg-update.yml) that creates draft pull requests for gateway updates when new upstream versions are detected.

### Is it safe to use the automatic updater in enterprise environments?

Yes, the auto-update mechanism downloads cryptographically signed MSI/MSIX packages from the official OpenClaw GitHub releases feed. For environments requiring offline updates or pre-installation auditing, use the manual installer method or build from source after reviewing the `build.ps1` script and [`docs/SETUP.md`](https://github.com/openclaw/openclaw-windows-node/blob/main/docs/SETUP.md) documentation.