Install OpenClaw on Windows 11 in 15 Minutes

Set up your personal AI assistant on Windows 11 with this complete guide covering prerequisites, installation, and common fixes.
·
4 min read
·
Mark
·
AI Tools

Problem: Getting OpenClaw Running on Windows 11

You want to set up OpenClaw—the AI assistant that actually does things—but you're on Windows 11 and unsure about the best installation path.

You'll learn:

  • The recommended WSL2 installation method (most stable)
  • How to install Node.js and OpenClaw properly
  • How to fix common Windows-specific issues

Time: 15 min | Level: Beginner

OpenClaw runs best on Linux-based systems because it relies on Unix tools and file permissions. While native Windows installation works, WSL2 (Windows Subsystem for Linux) provides better compatibility and performance.

Common symptoms of native Windows issues:

  • Node.js PATH errors during installation
  • Permission denied errors
  • Gateway service failures
  • File system performance problems

WSL2 solves these by running a real Linux kernel inside Windows 11.

Solution

Step 1: Enable WSL2

Open PowerShell as Administrator (right-click Start → Windows Terminal (Admin)):

# Enable WSL and Virtual Machine Platform
wsl --install

# This installs Ubuntu by default

Expected: Windows will download and install WSL2 with Ubuntu. You'll be prompted to restart.

If it fails:

  • Error: "WSL 2 requires an update": Run wsl --update then retry
  • Virtualization disabled: Enable it in BIOS (varies by manufacturer)

After restart, open Ubuntu from the Start menu. Create a username and password when prompted.

Step 2: Install Node.js in WSL2

Inside your Ubuntu terminal:

# Update package lists
sudo apt update && sudo apt upgrade -y

# Install Node.js 22 (OpenClaw requires Node 18+)
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt install -y nodejs

# Verify installation
node --version  # Should show v22.x.x
npm --version   # Should show 10.x.x

Expected: Both commands return version numbers without errors.

If it fails:

  • "curl: command not found": Run sudo apt install curl first
  • Permission errors: Make sure you're using sudo for apt commands

Step 3: Install OpenClaw

Now install OpenClaw globally:

# Install OpenClaw via npm
npm install -g openclaw@latest

# Verify installation
openclaw --version

Expected: Shows OpenClaw version (e.g., 2026.1.30).

If "openclaw command not found":

# Add npm global bin to PATH
echo 'export PATH="$PATH:$(npm config get prefix)/bin"' >> ~/.bashrc
source ~/.bashrc

# Try again
openclaw --version

Step 4: Run Onboarding Wizard

This sets up your AI provider and messaging platforms:

openclaw onboard

The wizard will ask:

  1. AI Provider: Choose Anthropic (Claude), OpenAI, or local models
  2. API Key: Paste your API key from the provider's website
  3. Messaging Platform: Select WhatsApp, Telegram, Discord, etc.
  4. Skills: Optional plugins (you can skip for now)

Expected: Interactive terminal UI guides you through setup. At the end, you'll see your gateway URL (e.g., http://172.20.224.5:18789).

If it fails:

  • "Invalid API key": Double-check your key has no extra spaces
  • Network errors: Make sure WSL2 has internet access (ping google.com)

Step 5: Access the Dashboard

Find your WSL2 IP address:

ip addr show eth0 | grep inet
# Example output: inet 172.20.224.5/20

Open a browser on Windows and go to:

http://YOUR_WSL_IP:18789

Replace YOUR_WSL_IP with the address from the command above.

Expected: OpenClaw web dashboard loads showing your configuration.

If it doesn't load:

  • Connection refused: Check if gateway is running: openclaw status
  • Can't find IP: Use localhost:18789 as fallback (may not work for all setups)

Verification

Test your installation:

# Check health status
openclaw health

# View gateway logs
openclaw gateway logs --tail 20

You should see:

  • CLI version: 2026.1.30 (or newer)
  • Node.js: v22.x.x
  • Gateway service: running
  • Auth: Your AI provider configured

Send a test message via your chosen platform (e.g., message your WhatsApp number). OpenClaw should respond.

What You Learned

  • WSL2 provides the best OpenClaw experience on Windows 11
  • Node.js 22+ is required for the latest features
  • The onboarding wizard handles most configuration automatically

Limitations:

  • Native Windows installation exists but has known issues (as of Feb 2026)
  • Some skills may require additional Linux tools
  • File access between WSL2 and Windows is possible but slower

Common Issues

Issue 1: Node.js Installed but Not Found

Symptom: node --version fails after installation.

Fix:

# Restart terminal
exit
# Open Ubuntu again from Start menu

# If still failing, check installation
which node

Issue 2: WSL2 Network Access from Windows

Symptom: Can't access dashboard from Windows browser.

Fix: WSL2 uses a virtualized network. Always use the WSL IP address, not localhost:

# Get your WSL IP
hostname -I | awk '{print $1}'

Issue 3: "Permission Denied" When Installing

Symptom: npm install fails with EACCES errors.

Fix: Never use sudo with npm global installs. Fix npm permissions:

# Change npm's default directory
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'

# Add to PATH
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

# Reinstall OpenClaw
npm install -g openclaw@latest

Issue 4: Slow File Performance

Symptom: OpenClaw feels sluggish.

Fix: Keep OpenClaw files inside WSL2, not Windows directories:

# Store config in WSL home
~/.openclaw/  # Good (fast)

# Avoid Windows paths
/mnt/c/Users/...  # Bad (10-20x slower)

If you absolutely can't use WSL2:

  1. Install Node.js from nodejs.org (Windows installer)
  2. Open PowerShell:
npm install -g openclaw@latest
openclaw onboard

Known issues as of Feb 2026:

  • winget errors during Node.js installation
  • PATH configuration problems
  • Gateway service may not start automatically
  • Some skills won't work