01
Choose the owner before installing
- Windows Hub: desktop setup, tray status, chat, diagnostics, node mode, and local MCP mode.
- Native PowerShell: direct Windows CLI and managed Gateway through Scheduled Tasks or a per-user startup fallback.
- WSL2: Linux-compatible runtime, systemd user service, and Linux tooling; Windows Hub can provision its own isolated WSL distribution.
02
Native PowerShell path
- 1
Run the official installer
Review the official PowerShell script and domain first.
iwr -useb https://openclaw.ai/install.ps1 | iex - 2
Verify the installation
Inspect version and health before adding a channel.
openclaw --version openclaw doctor openclaw gateway status --json - 3
Install managed startup if needed
This may create a Scheduled Task.
openclaw gateway install openclaw gateway status --json
Common questions
Before you act
Is WSL2 required?
No. It remains a strong compatibility option, while Windows Hub and the native CLI/Gateway are supported alternatives.
Primary sources
Verify against the owner.
OpenClaw on Windowsofficial docs · verified 2026-08-24
OpenClaw installation overviewofficial docs · verified 2026-08-24
OpenClaw Gateway CLIofficial docs · verified 2026-08-24
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.