Problem:
The Getting Started page (docs.openclaw.ai/start/getting-started#windows-powershell) presents the PowerShell IRM one-liner as the recommended Windows install method. Meanwhile, the Install page (docs.openclaw.ai/install) and Windows platform guide (docs.openclaw.ai/platforms/windows) explicitly state "we strongly recommend running OpenClaw under WSL2." A new Windows user following the Getting Started page has no indication they should be using WSL2 instead.

What I expected:
A single, consistent recommendation for Windows users, or at minimum a clear callout on the Getting Started page that Windows users should follow the WSL2 path for full feature support and stability.

What actually happens:
A Windows 10 user lands on Getting Started, sees the PowerShell tab labeled as recommended, installs natively, and then encounters the well-documented native Windows issues (no systemd daemon, shell syntax bugs like #10868, installer ENOENT errors like #3917/#4557, gateway scheduled task limitations like #5065/#5549).

Suggested fix:
Add a note/callout box on the Getting Started Windows PowerShell tab that says something like: "For the best experience on Windows, we recommend installing via WSL2. See the Install guide for details. The PowerShell method below works but has known limitations." Alternatively, make the Getting Started page default to showing the WSL2/curl path for Windows users.

Impact:
This creates confusion for new Windows users and may lead to suboptimal installations that need to be redone later.

Environment:

• OS: Windows 10
• Date: February 12, 2026