OpenClaw runs on Windows three ways: Docker Desktop (isolated container, most reliable), WSL2 + npm (full Linux environment, best for daily development), or native PowerShell (quickest start, known bugs). Each takes 15–30 minutes. For zero setup, Blink Claw runs OpenClaw on managed infrastructure in 2 minutes, from $22/mo.

OpenClaw has 358,000 GitHub stars and is one of the most widely deployed AI agent platforms of 2026. The agent itself works well. Getting it running reliably on Windows is a different story.

spawn npm ENOENT on plugin installs. Lost filesystem tools after updates. A cross-filesystem I/O penalty that makes file reads 10x slower. A command injection CVE that requires a manual update to patch.

Most people don't want to manage that. They want an AI agent doing work — not an afternoon debugging WSL2.

This guide covers every self-hosted path and every Windows-specific error. It also covers the 2-minute alternative that skips all of it.

VS Code and Windows Terminal running side by side on Windows 11 — the development environment where OpenClaw runsBlink

Pick Your Installation Method in 30 Seconds

Don't read the whole guide if you don't need to. Answer one question and skip to the right section.

Already use Docker? → Docker Desktop method (15 min)

Developer who wants a real Linux environment? → WSL2 + npm method (20 min)

Just testing, no commitment? → Native PowerShell method (15 min, known bugs)

Zero infrastructure, just want it running? → Blink Claw managed hosting (2 min)

System Requirements for OpenClaw on Windows

Run winver in PowerShell to check your Windows build number. Below 19041 means WSL2 won't work.

CVE-2026-22176 — update before running. A command injection vulnerability in the Windows Scheduled Task auto-start mechanism was disclosed March 19, 2026. Always install the latest release. See the OpenClaw security guide for full details.

Installation Methods

Install OpenClaw on Windows Using Docker Desktop

Docker Desktop runs OpenClaw inside an isolated Linux container. You get easy upgrades via docker pull.

1. Install Docker Desktop
   Download from docker.com. During installation, ensure "Use WSL 2 instead of Hyper-V" is selected.

2. Pull the OpenClaw image

   docker pull ghcr.io/openclaw/openclaw:latest
   

3. Create a persistent config directory

   mkdir C:\openclaw
   

4. Run the container

   docker run -d --restart unless-stopped --name openclaw `
     -v C:\openclaw:/home/node/.openclaw `
     -p 18789:18789 `
     ghcr.io/openclaw/openclaw:latest `
     node openclaw.mjs gateway --allow-unconfigured
   

5. Verify

   docker ps
   

6. Open the web UI
   Navigate to http://localhost:18789.

Install OpenClaw on Windows with WSL2

WSL2 runs a real Linux kernel inside Windows, giving OpenClaw native systemd, correct file permissions, and an environment identical to a Linux server.

1. Enable WSL2
   PowerShell as Administrator:

   wsl --install
   

2. Install Node.js v22+

   curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
   sudo apt-get install -y nodejs
   

3. Install OpenClaw

   curl -fsSL https://openclaw.ai/install.sh | bash
   

4. Run onboarding

   openclaw onboard --install-daemon
   

Install OpenClaw Natively on Windows Without WSL

1. Install Node.js v22+

   winget install OpenJS.NodeJS
   

2. Run the installer (Administrator PowerShell)

   Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
   iwr -useb https://openclaw.ai/install.ps1 | iex
   

3. Complete onboarding

   openclaw onboard --install-daemon
   

Common Errors and Fixes

Use openclaw doctor to Diagnose Windows Issues

Before chasing any specific error, run this first:

openclaw doctor

What it checks:

• Node.js version
• Network connectivity
• API key validation
• Daemon/gateway status
• Plugin health
• Config integrity

Plugin Installation Errors on Windows

You tried to install a plugin. You got this:

Failed to start CLI: Error: spawn npm ENOENT

Fixes:

1. Update OpenClaw to latest

npm install -g openclaw@latest

2. **Verify npm is on PATH**  

where.exe npm

3. **Switch to WSL2**  
The plugin system works flawlessly on Linux.

## Security for Your OpenClaw Gateway on Windows

### Bind to localhost only

Add this to your OpenClaw config:
```json
{
  "gateway": {
 "host": "127.0.0.1"
  }
}

Enable Gateway Authentication

openclaw config set gateway.auth.enabled true
openclaw config set gateway.auth.token "$(openssl rand -hex 32)"

Manage Secrets in .env Files

export OPENAI_API_KEY="sk..."

Optimize WSL2 Performance for OpenClaw

1. Create or edit .wslconfig

   [wsl2]
   memory=8GB
   processors=4
   swap=4GB
   localhostForwarding=true
   

2. Keep files inside WSL ext4:

   cd ~/openclaw
   

Update OpenClaw on Windows

1. Docker

   docker pull ghcr.io/openclaw/openclaw:latest
   docker stop openclaw && docker rm openclaw
   

2. WSL2 or native npm

   npm install -g openclaw@latest
   openclaw daemon restart
   

For most developers, WSL2 + npm is the sweet spot. Full Linux compatibility, native systemd, and faster file I/O than Docker overhead, and zero licensing concerns.

Self-host when: you need data to stay on-device for compliance, or you want to run large local models on your own GPU.

Use Blink Claw when: you want an AI agent doing work, not an afternoon managing infrastructure.