Windows

Install OpenClaw on Windows (WSL2 Recommended)

Step-by-step guide to get OpenClaw running reliably on Windows.

Is this setup right for you?

Good fit

  • You run OpenClaw manually
  • You're comfortable following guides

Not recommended

  • You need 24/7 uptime
  • You don't want to touch system settings

Before You Start

  • Windows 10/11
  • WSL2 enabled
  • Supported Node.js version
  • Internet access

Installation Steps

To ensure correctness and avoid outdated commands, we guide you through the official installation path and highlight what actually matters for this setup.

Step 1 - Follow the Official Installation Guide

OpenClaw's installation commands may change between versions. To avoid copy-paste errors or outdated instructions, we link directly to the official guide for this setup.

This ensures you always use the latest and supported installation commands.

Step 2 - Platform-Specific Notes (Read Before Running Commands)

Before running the official commands, review these notes to avoid common setup issues on this platform.

  • On Windows, WSL2 is strongly recommended for stability
  • Make sure required ports are not already in use
  • Use a supported Node.js version as specified in the official docs

Step 3 - Verify Your Installation

After completing the official steps, confirm that OpenClaw is running correctly.

What you should see: a startup or 'listening' message without immediate errors.

What should work: a local dashboard, health endpoint, or CLI response indicating the service is active.

If something doesn't look right, see: Troubleshooting Guide

This guide intentionally links to official installation instructions to ensure accuracy. Platform-specific notes and verification steps are curated and validated to improve success rates.

Verify Your Installation

Service status

OpenClaw should show a running or listening state.

Local access

You can reach the local UI or health endpoint without errors.

First task

A simple workflow runs end-to-end without permissions errors.

Common Issues on Windows

Port conflicts

OpenClaw fails to bind or starts then exits.

Stop the conflicting service or change the configured port.

See troubleshooting

Permission errors

Commands fail with permission denied.

Recheck WSL2 permissions and file ownership.

See troubleshooting

Node version mismatch

Install scripts fail or runtime crashes.

Install the supported Node.js version listed in the official docs.

See troubleshooting
Install OpenClaw on Windows – Local Deployment Guide | openclawskill