Do I need WSL2 to run AI agents on Windows?

Not for every agent. OpenClaw and Hermes work natively on Windows. WSL2 is strongly recommended because it avoids file-path quirks, improves npm compatibility, and lets you follow Linux-based install guides directly. Claude Cowork's local environment requires the VM platform that WSL2 also uses.

How do I fix OpenClaw rename or file-approval errors on Windows?

Two known Windows-specific issues: (1) A rename-error when OpenClaw tries to move files appeared in the v2026.5 release — see the voice-and-caching fixes release notes for the patch. (2) A sandbox block preventing access to your Windows home folder appeared in the 5.12 update — see the stability-fixes release notes for the workaround.

Last updated: 2026-06-02

Run AI Agents on Windows: WSL2 Setup, Fixes & Every Platform Note (2026)

Q: Can I run OpenClaw on Windows?

Yes. OpenClaw installs fine on Windows native or inside WSL2. For the smoothest experience, use WSL2 (Ubuntu): Unix paths, package managers, and file-system behaviour all match what the docs expect. Install WSL2, then follow the Linux path in the OpenClaw setup guide.

Q: Can I run Hermes Agent on Windows?

Yes. Hermes installs on Windows natively. WSL2 is not required, though some users find it smoother. The curl installer and npm setup work in PowerShell. See the Hermes setup guide for the install command.

Q: Why won't Claude Cowork install on Windows?

Claude Cowork's local environment requires the Windows Virtual Machine Platform (the same feature WSL2 uses). This needs administrator rights to enable and is blocked on managed or corporate machines. If you can't enable it, run inside WSL2, use a Linux VPS, or switch to a CLI agent such as OpenClaw or Hermes that doesn't need the VM platform.

Windows works — but most CLI-based AI agents run best inside WSL2 rather than native PowerShell. This page collects every Windows-specific note, known error, and fix across all the platforms we cover, so you don't have to dig through individual setup guides.

The short answer

Use WSL2 + Ubuntu for OpenClaw, NemoClaw, IronClaw, and Hermes. It avoids Windows path quirks and lets you follow Linux install steps directly. For Claude Cowork, WSL2's Virtual Machine Platform is required — and it must be enabled as admin. If you're on a managed corporate machine, that may be blocked.

WSL2 Quick-Start

If you're starting fresh on Windows, this is the fastest path to a working agent environment:

Enable WSL2
Open PowerShell as Administrator and run:
```
wsl --install
```
This enables the Virtual Machine Platform, installs WSL2, and sets Ubuntu as the default distro. Reboot when prompted.
Open Ubuntu from the Start menu
Set a username and password when prompted. This is your Linux environment — everything from here follows Linux install guides.

Install Node.js inside WSL2 via nvm

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source ~/.bashrc
nvm install --lts
node --version

Follow the Linux path for your chosen agent
OpenClaw, Hermes, NemoClaw, and IronClaw all have standard curl/npm installers that work inside this environment. See the per-platform notes below.

Native Windows (without WSL2)

Most agents will install in PowerShell with Node.js for Windows from nodejs.org. You may hit file-path issues, permission errors, or behaviour differences not covered in the docs. WSL2 is strongly recommended for anything beyond basic use.

Windows Fixes & Known Issues

These are documented Windows-specific issues with known fixes:

OpenClaw — Rename error (v2026.5)

A EPERM: operation not permitted, rename-style error appeared in the v2026.5 release when OpenClaw tried to move files on Windows. The patch and workaround are documented in the OpenClaw v2026.5 Voice, Caching & Fixes release notes.

OpenClaw — Home-folder sandbox block (5.12 update)

The 5.12 update introduced a sandbox change that blocked access to the Windows home folder in some configurations. Workaround and fix are in the OpenClaw 5.12 Stability Fixes release notes.

Claude Cowork — Virtual Machine Platform / admin blocker

Claude Cowork's local environment depends on the Windows Virtual Machine Platform feature, which needs administrator rights to enable. On managed/corporate laptops this feature is often disabled by IT policy. If you can't enable it, your options are: run inside WSL2 (which already uses the VM platform), use a Linux VPS, or switch to a CLI agent. Full details on the pre-flight checklist page.

Per-Platform Windows Notes

OpenClaw on Windows

OpenClaw installs on both native Windows and WSL2. WSL2 is recommended for multi-agent setups and anything involving file manipulation. The two known Windows bugs (rename error, sandbox block) above are fixed in recent releases. Start at the OpenClaw setup guide. If you hit problems, check the OpenClaw troubleshooting page and FAQ.

Hermes Agent on Windows

Hermes installs natively on Windows with its standard curl installer — WSL2 is not required, though some users prefer it. Telegram is the recommended messaging channel on Windows as on every OS. Start at the Hermes setup guide. For issues, see the Hermes troubleshooting page and FAQ.

Claude Cowork on Windows

Claude Cowork's local environment requires the Virtual Machine Platform feature — see the blocker note above. If you can enable it, the install proceeds normally. If you can't, use WSL2 or a CLI agent instead. The pre-flight checklist has the full rundown on what needs admin rights and what doesn't. Check the Claude Cowork FAQ for additional questions.

NemoClaw, IronClaw, Kilo Code on Windows

All three are CLI agents with standard Node.js installers. WSL2 is the easiest path. Follow the Linux instructions inside WSL2 for each: NemoClaw setup, IronClaw setup, Kilo Code setup.

Frequently Asked Questions

Can I run OpenClaw on Windows?

Yes. OpenClaw works on native Windows and inside WSL2. WSL2 gives the smoothest experience — Unix paths and package managers behave as the docs expect. See the OpenClaw setup guide.

Can I run Hermes Agent on Windows?

Yes. Hermes installs natively on Windows without WSL2. The curl installer and npm setup work in PowerShell. See the Hermes setup guide.

Why won't Claude Cowork install on Windows?

Claude Cowork's local environment requires the Virtual Machine Platform Windows feature, which requires administrator rights. On managed or work machines it may be disabled by IT policy. If you can't enable it, use WSL2 (which uses the same feature), a Linux VPS, or switch to OpenClaw or Hermes. Full details at /start/.

Do I need WSL2 to run AI agents?

Not for every agent. OpenClaw and Hermes work natively on Windows. WSL2 is strongly recommended to avoid file-path quirks, improve npm compatibility, and follow Linux-based guides directly. Claude Cowork requires the VM platform feature that WSL2 also uses.

How do I fix Windows rename or file-approval errors in OpenClaw?

Two known bugs: a rename error in v2026.5 (patch notes here) and a home-folder sandbox block in 5.12 (fix notes here). Both are fixed in current releases.

Where can I find more Windows troubleshooting help?

Start with the OpenClaw troubleshooting page, the Hermes FAQ, or the cross-platform troubleshooting hub. For OS-level issues, the pre-flight checklist covers the most common blockers before you even install.