Native install vs. Windows Hub vs. WSL2 — judged against OpenClaw's own maturity scores and its live issue tracker.
Straight from docs/maturity-scores.yaml in the installed package. Score run completed 2026-05-30. It keeps three separate Windows entries.
LTS-supported in 5 of 6 categories — the best any Windows path manages.
WSL Setup 76 · CLI 76 · Diagnostics & Repair 74 · Browser & Control UI 72 · Gateway Access & Exposure 70 · Gateway Service Lifecycle 64 (the one Alpha soft spot)
netsh portproxydbus-launch idle-termination workaroundInstall with iwr -useb https://openclaw.ai/install.ps1 | iex. LTS-supported in only 1 of 4 categories.
Updates 74 · CLI 72 · Gateway Management 68 · Networking 58 — the weakest Windows category anywhere
Native WinUI app for Windows 10 20H2+ and Windows 11. Signed x64 and ARM64 installers, no admin rights needed.
This is the single most illuminating finding — GitHub issue #126874, still open, measured at commit e78b9d3ce4a:
process.platform === "win32" branches are the untaken path.runWindows requires isCanonicalRepository — so a fork's CI never runs Windows at all.ci-gate counts a skipped job as passing. If the path filter declines to schedule checks-windows, the gate goes green with zero Windows coverage behind it.That is the mechanism behind the Alpha rating. Windows regressions are structurally unlikely to be caught before release — which is exactly what you would predict from the defect list below.
| # | Area | Issue | Severity |
|---|---|---|---|
| 126874 | CI | Windows CI runs 66 of 10,979 test files; a skipped check counts as passing | structural |
| 119882 | Gateway | Gateway process exits silently (code 0) with no auto-recovery | high |
| 105528 | Core tools | exec/read tools silently return empty output (v2026.6.x regression) | high |
| 122834 | Gateway | Restart path unreliable after active-turn crash | high |
| 102755 | Startup | The project won't start on Windows and WSL | high |
| 124407 | Performance | CLI gateway commands take 10–30s due to eager bootstrap before RPC | medium |
| 124125 | Cron | Durable fence fails — getFileLockProcessStartTime has no win32 path | medium |
| 111620 | Paths | Windows file tools misresolve POSIX drive paths | medium |
| 105667 | Paths | Incorrect sandbox bind-mount parsing for relative drive-letter paths | medium |
| 114207 | Paths | Misclassifies same-path sandbox binds as aliases | medium |
| 123176 | Node | Node exec stops after system.run.prepare; no approval event or UI card | medium |
| 112051 | Installer | Cannot repair stale Winget Node registrations | medium |
| 95072 | Gateway | /restart falls back to in-process restart without changing PID | medium |
| 111595 | Paths | Equivalent Windows cwd spellings split catalog project groups | low |
Note the clustering: four separate open bugs on drive letters and path resolution. That is a structural weakness, not four coincidences.
dbus-launch true rather than /bin/true in the boot task to keep a child-of-init alive./ru SYSTEM for the scheduled boot task — per-user WSL distros are invisible to SYSTEM, so the task appears to run but the distro never starts. Use /ru "$env:USERNAME".netsh interface portproxy, and the WSL IP can change after restarts, so the rule needs refreshing.127.0.0.1.🪟 How well does OpenClaw run on Windows? Short answer: use WSL2. It's the only path rated Beta. 📊 OpenClaw's own maturity scores: • Windows via WSL2 — BETA (M3), quality 69 • Native Windows CLI+Gateway — ALPHA (M2), quality 63 • Windows companion app — Planned (M0) ⚠️ The reason quality is low: Windows CI runs 66 of 10,979 test files. That's 0.60% of the suite. 23 of the 43 Windows-named test files never even run on Windows, and a SKIPPED Windows job counts as PASSING. Regressions basically can't be caught. 🐛 46 open Windows issues, including: • Gateway exits silently (code 0), no auto-recovery • exec/read silently return EMPTY OUTPUT (regression) • CLI gateway commands take 10–30 seconds • 4 separate drive-letter/path bugs ✅ Verdict: WSL2 for anything real. Windows Hub is fine for a desktop app — it sets up a WSL gateway under the hood. Don't put load-bearing work on the native Windows Gateway. Full details 👉 https://artifact.sahirm.com/a/openclaw-on-windows/
Confidence: maturity scores read directly out of docs/maturity-scores.yaml in the locally installed OpenClaw 2026.6.10 — score run dated 2026-05-30. Issue counts and titles queried live from the openclaw/openclaw tracker on 29 Aug 2026 (46 open with "windows" in the title, 200+ closed). Two caveats: the claim that the Hub's M0 rating is stale is my inference from the date gap, not something confirmed upstream; and individual issues were not re-tested against the current release, so some may be fixed but not yet closed.