OpenClaw on Windows — Installation & Common Issues
Step-by-step Windows installation guide covering Node.js setup, WSL2 configuration, LM Studio integration, and troubleshooting Windows-specific issues.
⚠️ The Problem
Need help don't have a lot of computer knowledge
Need help setting clawd on my windows pc
2. **WSL2 cron jobs skipping scheduled runs:**
Hourly cron job (0 * * * *) skips slots — nextRunAtMs jumps forward without executing
Jobs seem to only run when there's user message activity
Overnight, zero jobs fire despite gateway staying alive
3. **LM Studio connection errors from WSL2:**
Invalid input: expected object, received string
Unrecognized keys in config
4. **openclaw node run on Windows shows nothing:**
openclaw node run on Windows only shows node Host Path and nothing has done
Nothing on the Gateway side either
5. **Exec commands not working after approval:**
"I cannot directly view your hardware... but I can provide precise commands"
Bot responds about needing approval but doesn't execute
🔍 Why This Happens
openclaw node run command may not find required binaries if PATH isn't set up correctly.
5. Exec tool permissions — The exec tool requires explicit approval for commands. If approvals aren't being processed correctly, the bot can't execute anything.✅ The Fix
## Complete Windows Installation (From Scratch)
### Step 1: Install Node.js
1. Go to https://nodejs.org and download the LTS version 2. Run the Windows Installer (.msi) 3. Click "Next" through everything 4. Restart your computer after installing
Open Command Prompt (Windows key + R, type cmd, press Enter) and verify:
node --versionYou should see v24.x.x or higher.
### Step 2: Install Git
Download from https://git-scm.com/download/win and install with defaults.
### Step 3: Install pnpm
npm install -g pnpm### Step 4: Clone and Build OpenClaw
git clone https://github.com/clawdbot/clawdbot.gitcd clawdbotpnpm installpnpm build### Step 5: Run Onboarding
pnpm clawdbot onboardFollow the wizard to set up your model and channels.
## WSL2 Cron Jobs Skipping
If your cron jobs only run when there's activity and skip overnight:
Root cause: Windows host is sleeping, which suspends WSL2.
Fixes:
1. Prevent Windows from sleeping — Change power settings to never sleep when plugged in
2. Move gateway to always-on server — A Linux VPS or dedicated machine won't sleep
3. Add timeouts to long jobs — Prevent one job from blocking the next:
{ "cron": { "jobs": [{ "id": "hourly-pulse", "schedule": "0 * * * *", "isolated": true, "payload": { "timeoutSeconds": 300 } }] }}Debug cron issues:
openclaw --versionopenclaw cron runs --id <jobId> --limit 50openclaw logs --limit 300 | grep "cron:"## Connecting LM Studio (Windows) to OpenClaw (WSL2)
LM Studio runs on Windows, but OpenClaw in WSL2 can't reach localhost:1234. You need the WSL2 host IP.
Find your WSL2 host IP:
# From inside WSL2:cat /etc/resolv.conf | grep nameserver | awk '{print $2}'Configure OpenClaw:
Your config must use the correct format (object, not string):
{ "providers": { "lmstudio": { "baseUrl": "http://172.x.x.x:1234/v1", "models": { "default": { "id": "your-model-name" } } } }, "model": { "provider": "lmstudio", "id": "your-model-name" }}In LM Studio: Enable "Allow connections from network" in settings.
## Fixing openclaw node run on Windows
If the command shows PATH and does nothing:
1. Check the SSH tunnel is working:
ssh -L 18789:localhost:18789 user@gateway-host2. Verify gateway connectivity:
curl http://localhost:18789/health3. Check logs on both sides:
# On the node (Windows)openclaw logs --follow# On the gatewayopenclaw logs --follow## Exec Tool Not Working
If the bot says it can provide commands but won't execute them:
1. Check exec is enabled:
{ "exec": { "enabled": true, "approval": "auto" }}2. For Discord: Make sure exec approvals are configured for the channel 3. Approve in the same channel — The approval button must be clicked where the request appeared
## Fresh Start on Windows
# Stop the daemonopenclaw daemon stopopenclaw daemon uninstall# Delete all data (PowerShell)Remove-Item -Recurse -Force $env:USERPROFILE\.clawdbot# Delete workspaceRemove-Item -Recurse -Force $env:USERPROFILE\clawd# Reinstallgit clone https://github.com/clawdbot/clawdbot.gitcd clawdbotpnpm installpnpm buildpnpm clawdbot onboard🔥 Your AI should run your business, not just answer questions.
We'll show you how.$97/mo (going to $197 soon)
📋 Quick Commands
| Command | Description |
|---|---|
| node --version | Check Node.js version |
| npm install -g pnpm | Install pnpm package manager |
| pnpm install | Install dependencies |
| pnpm clawdbot onboard | Run the setup wizard |
| openclaw cron runs --id <jobId> --limit 50 | Check cron job history |
| cat /etc/resolv.conf | grep nameserver | Find WSL2 host IP (run in WSL2) |
| Remove-Item -Recurse -Force $env:USERPROFILE\.clawdbot | Delete OpenClaw config (PowerShell) |
| openclaw logs --follow | Watch logs in real-time |
Related Issues
📚 You Might Also Like
Set Up OpenClaw for Beginners
Installation Guide
30-Minute Setup Guide
OpenClaw Configuration Guide: Complete Settings Reference (2026)
Master OpenClaw configuration with this complete reference. All config.yaml settings explained: AI models, channels, multi-agent setup, plugins, secrets management, and more.
🐙 Your AI should run your business.
Weekly live builds + template vault. We'll show you how to make AI actually work.$97/mo (going to $197 soon)
Join Vibe Combinator →