solution gateway high windows

Windows (WSL2): gateway service install fails (systemd not enabled)

Fix WSL2 gateway daemon install issues by enabling systemd in /etc/wsl.conf, shutting down WSL, and retrying openclaw gateway install.

By CoClaw Team •

Symptoms

  • On Windows you installed OpenClaw inside WSL2, but openclaw gateway install fails.
  • Older notes may mention openclaw onboard --install-daemon; treat that as legacy symptom text and retry with the current gateway install command.
  • systemd user services aren’t available.

Cause

For WSL2 installs, gateway service installation relies on systemd inside the WSL distro. systemd is not enabled by default on some installs.

Fix

Inside WSL:

sudo tee /etc/wsl.conf >/dev/null <<'EOF'
[boot]
systemd=true
EOF

Then from Windows PowerShell:

wsl --shutdown

Re-open your WSL distro and verify:

systemctl --user status

Now retry:

openclaw gateway install

Verify

openclaw gateway status
openclaw status

Verification & references

  • Reviewed by:CoClaw Code Team
  • Last reviewed:March 14, 2026
  • Verified on: Windows

References

Official docs

  1. OpenClaw docs: /platforms/windows
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

Linux: gateway doesn't stay running (systemd service not installed)
Fix
If the gateway only runs in the foreground or stops after you close SSH, install/repair the systemd service and enable user lingering.
Linux/systemd: OpenClaw leaves orphan gateway processes or port 18789 conflicts
Fix
Fix Linux hosts where CLI-triggered gateway respawn collides with a systemd-managed OpenClaw gateway, causing orphan processes, EADDRINUSE, or 'another gateway instance is already listening'.
Gateway fails to start: EADDRINUSE / another gateway instance is already listening
Fix
Fix OpenClaw gateway port conflicts (EADDRINUSE) by stopping the other process or choosing a new gateway port/profile.
Windows: 'openclaw' is not recognized after install
Fix
Fix Windows PATH issues after installing OpenClaw globally (npm prefix not on PATH, terminal not restarted, or multiple Node installs).
OpenClaw Installation Troubleshooting: Node/NPM, PATH, Windows (WSL2), and Docker
Guide
A layered checklist for the most common 'can't install' / 'command not found' / 'service won't start' failures. Covers Node version, global install permissions, PATH issues, WSL2 systemd, and Docker setup gotchas.
OpenClaw on Windows: Native vs WSL2, Install Paths, and When to Switch
Guide
A practical decision guide for Windows users: choose between native Windows and WSL2 based on service model, tool compatibility, and debugging cost, then switch paths cleanly when the platform is the problem.