Skip to content
Last updated

OpenClaw on Windows (Beginner-Friendly)

⚠️ Security note: test on a spare machine, VM, or separate Windows account first.
OpenClaw can run high-privilege actions, so avoid your primary work environment.

What you'll achieve

  • Install OpenClaw with PowerShell
  • Complete onboarding on Windows
  • Start OpenClaw, verify it responds, and learn how to restart it
  • Fix common Windows setup problems such as ExecutionPolicy, PATH, Defender, and firewall blocks

Before you start

  • Prefer an English username and simple file paths if possible
  • Prepare a working model API key
  • Confirm network access to the install script

Step 1: Run PowerShell as administrator

Start menu -> PowerShell -> right click -> Run as Administrator

Command
whoami

Step 2: Allow script execution

Command
Set-ExecutionPolicy RemoteSigned -Scope CurrentUserGet-ExecutionPolicy -Scope CurrentUser

Step 3: Install OpenClaw

Command
iwr -useb https://openclaw.bot/install.ps1 | iex

Verify the install

Command
openclaw --versionwhere openclaw

Step 4: If the command does not work

  • Close PowerShell and open it again
  • Re-run openclaw --version
  • If needed, remove old packages and install again
Command
npm uninstall -g clawdbotnpm uninstall -g moltbotnpm uninstall -g openclaw

Step 5: Run onboarding

Command
openclaw onboard --flow quickstart

Use Telegram first if you want the easiest first proof that OpenClaw works.

Step 6: Start and run OpenClaw

Command
openclaw start

After config changes:

Command
openclaw gateway restart

Verify startup

  • Logs do not show recurring errors
  • Your chosen channel responds to a test message

Step 7: Windows setup pitfalls

ExecutionPolicy error

Recheck Step 2 and confirm the current user scope is set correctly.

PATH or command issues

Use where openclaw and reopen PowerShell after installation.

Firewall or Defender issues

  • Allow the relevant process through Windows Firewall
  • Add your OpenClaw data folder to Defender exclusions only if necessary

If you want a 24/7 environment, do not keep using a desktop-only workflow. Continue with Docker / VPS deployment.

If you need routing, gateway token, or skills configuration, continue with advanced configuration.