Fix OpenClaw Gateway Errors on Windows
Seeing gateway closed (1006 abnormal closure), zombie node.exe on port 18789, or schtasks Last Result: 1? Use this page to jump to the exact OpenClaw Windows fix in under 2 minutes.
Next Step
Fix now, then reduce repeat incidents
If this issue keeps coming back, validate your setup in Doctor first, then harden your config.
npm Install Errors
PSSecurityException, EBUSY, exit code 3221225477, spawn git ENOENT, icacls permissions
Gateway Service Errors
Zombie process on port 18789, crash loop, schtasks failure, post-update instability
Find Your Error Fast
PSSecurityException / npm.ps1 cannot be loadednpm Install Errors →npm error code 3221225477 / postinstall crashnpm Install Errors →EBUSY — resource busy or lockednpm Install Errors →spawn git ENOENTnpm Install Errors →zombie node.exe on port 18789Gateway Service →gateway crash loop / schtasks Last Result: 1Gateway Service →gateway closed (1006 abnormal closure)Gateway Service →token mismatch after Windows restartGateway Service →Local Models (Ollama) on Windows
Problem: Not Enough Space on C: Drive
Large models (8–15 GB+) can fill your system drive. Redirect Ollama's storage to another drive:
setx OLLAMA_MODELS "D:\ollama\models" # Restart Ollama, then pull your model ollama pull cas/hermes-2-pro-llama-3-8b
Problem: Model Doesn't Appear in OpenClaw
OpenClaw filters for models that support tool calling. Models without tool-calling capability are hidden to prevent broken agent behavior. Use models known to work:
| Model | Size | Tool Calling | RAM Needed |
|---|---|---|---|
| hermes-2-pro (8B) | ~5 GB | Yes | 16 GB+ |
| mistral:7b | ~4 GB | Yes | 16 GB+ |
| llama3.1:8b | ~5 GB | Yes | 16 GB+ |
| gemma3:4b | ~3 GB | No | 8 GB+ |
Sandbox / Docker ENOENT
The Gateway is trying to run Docker for agent sandboxing, but Docker isn't installed or isn't in PATH. Two options:
Quick Fix: Disable Sandbox
If you don't need sandboxing (most local setups):
Proper Fix: Install Docker
For production or if you want agent isolation:
Browser Tools Not Working
After stabilizing the Gateway, browser automation commands fail. OpenClaw defaults to the chrome browser profile (which requires a browser extension relay). On a single-machine Windows setup, use the built-in openclaw managed profile:
openclaw config set browser.defaultProfile "openclaw" openclaw config set gateway.nodes.browser.mode "off" openclaw gateway restart
Canvas vs. Dashboard Confusion
The Dashboard/Control UI at http://127.0.0.1:18789/ is for settings and chat. The Canvas tool (canvas.*) requires a paired node device — it reports "no nodes connected" without one.
Complete Troubleshooting Checklist
Git is installed and in PATH (git --version works)
Using .cmd shims or ExecutionPolicy is RemoteSigned
Config file permissions restricted with icacls
No zombie node.exe on ports 18789, 18791, 18792
Ollama model supports tool calling (hermes-2-pro, mistral:7b)
Ollama models stored on a drive with enough space
Sandbox mode is off or Docker Desktop is installed
Browser profile set to "openclaw" for single-machine setup
No Scheduled Task pointing to stale paths
Break-glass auth settings are disabled
After update: ran openclaw gateway install --force
Still Stuck?
npx clawkit-doctor@latestRelated Guides
Windows errors often come with these:
Fix It Faster With Our Tools
Did this guide solve your problem?