The simplest Windows installation is Windows Hub, OpenClaw’s native companion app. Terminal users can use the official PowerShell installer, while developers who need Linux-compatible services should run the Gateway in WSL2. OpenClaw supports Node.js 24.16 or newer and 26.1 or newer; Node.js 26 is the recommended line.
Antihost offers VPS plans with one-click OpenClaw, NVMe storage and a 14-day free trial.
This guide explains all three routes, the exact commands, what each installer changes, and how to fix the common “openclaw is not recognized” and unsupported-runtime errors.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Choose the right Windows installation route
OpenClaw has three practical ways to run on Windows. Your choice determines where the Gateway runs, how much Windows integration you receive, and whether you work primarily with Windows or Linux tooling.
| Route | Best for | Main requirement | What you gain | Trade-off |
|---|---|---|---|---|
| Windows Hub | People who want guided setup and a desktop companion | Windows 10 version 20H2 or later, or Windows 11 | Setup wizard, tray status, chat, Command Center diagnostics, and Windows node capabilities | Uses the native companion app and its Gateway setup flow |
| PowerShell installer | Terminal users who want a native Windows CLI and Gateway | PowerShell 5 or later and a supported Node.js runtime | Fast script-based installation with global npm or Git installation methods | PATH, Git, or runtime troubleshooting can be necessary |
| WSL2 Gateway | Linux-compatible services, automation, or existing Linux workflows | A WSL2 distribution with systemd enabled | The most Linux-compatible Gateway runtime on Windows | Requires a Linux distribution and Linux commands |
Windows Hub can also provision an app-owned WSL Gateway or connect to an existing remote Gateway. That makes it a useful front end even when the service itself is not running directly in native Windows.
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
Check requirements before installing
Windows Hub requirements
- Windows 10 version 20H2 or newer, or Windows 11.
- A signed installer matching your computer’s processor architecture: x64 or ARM64.
- Administrator elevation is not required for the Windows Hub installation.
PowerShell requirements
- PowerShell 5 or later.
- Node.js 24.16 or later, or Node.js 26.1 or later. Node.js 26 is recommended.
- Internet access for the installer and, if needed, its runtime and dependency downloads.
WSL2 requirements
- Windows Subsystem for Linux and a Linux distribution such as Ubuntu.
- Permission to install WSL under your organization’s Windows policy.
- systemd enabled inside the distribution so the Gateway can run as a Linux service.
If you are unsure, start with Windows Hub. Choose PowerShell when you specifically want a native command-line installation, and choose WSL2 when Linux compatibility matters more than native Windows integration.
Install OpenClaw with Windows Hub
Windows Hub is the recommended native Windows desktop route. It is a WinUI companion application for Windows 10 20H2 and later and Windows 11. It provides first-run setup, a system-tray status view, chat, Command Center diagnostics, and Windows node capabilities.
1. Download the signed installer
Open the current Windows Hub release page from OpenClaw’s Windows platform documentation and download the signed installer for your architecture. Use the x64 build for most Intel and AMD PCs. Use ARM64 only on a Windows-on-ARM computer.
2. Run it as a normal Windows application
Double-click the downloaded installer and follow the prompts. Windows Hub is designed to install without administrator privileges, so do not use “Run as administrator” unless your organization’s policy requires it.
3. Start the companion
After installation, open OpenClaw Companion from the Start menu. You can also launch it from the system tray after it is running.
4. Complete first-run setup
Follow the setup flow shown by the Hub. It can provision an app-owned WSL Gateway for you, or connect the companion to an existing remote Gateway. Choose the app-owned option if you want the Hub to manage the local Gateway environment; choose the remote option if your Gateway already runs elsewhere.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute5. Use the built-in diagnostics
Open Command Center when you need to inspect setup or connection state. The tray indicator gives you a quick operational status without opening a terminal, while the chat and Windows node features are available from the companion interface.
Install OpenClaw with the PowerShell installer
The PowerShell script is the fastest native Windows command-line route. It installs OpenClaw using the default global npm method unless you select the alternative Git method.
1. Open PowerShell
Start PowerShell from the Windows Start menu. PowerShell 5 or later is required. Use the normal user shell unless your Windows policy or package-management setup requires elevation.
2. Run the standard installer
Paste this command and press Enter:
iwr -useb https://openclaw.ai/install.ps1 | iexThe command downloads the installer script and executes it. The script attempts to obtain a supported Node.js runtime through winget, Chocolatey, or Scoop. If those package-manager paths are unavailable, or they leave an unsupported runtime, the installer can download official portable Node.js 26 into %LOCALAPPDATA%OpenClawdepsportable-node.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Install without starting onboarding
Use the no-onboarding form when you want to install first and configure the Gateway later:
Rank #2
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -NoOnboardThe switch suppresses the initial onboarding step. Installation still completes, allowing you to verify the command and Gateway separately.
4. Understand the installation method
Global npm installation is the default OpenClaw method. A Git-based installation method is also available through the installer. The script may bootstrap a user-local MinGit installation when Git dependencies are needed and Git for Windows is not already available.
5. Reopen PowerShell and verify
Close and reopen PowerShell after installation. A new shell loads PATH changes made by the installer. Then run:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
openclaw --version
openclaw gateway statusThe first command should print the installed OpenClaw version. The second checks Gateway status. If you used -NoOnboard, complete onboarding separately when you are ready to configure the installation.
Install an OpenClaw Gateway in WSL2
WSL2 is the most Linux-compatible Gateway runtime on Windows. This route is appropriate when your automation, service configuration, or existing workflow is already Linux-oriented.
1. Install WSL and Ubuntu
From PowerShell, use the command permitted by your Windows policy. The standard one-command installation is:
wsl --installTo inspect available distributions first, run:
wsl --list --onlineTo install Ubuntu 24.04 explicitly, run:
wsl --install -d Ubuntu-24.04Windows may ask you to restart. After the distribution is installed, launch Ubuntu from the Start menu or by entering wsl in PowerShell and create the Linux user requested by the distribution.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →2. Enable systemd in the distribution
Inside Ubuntu, create or replace /etc/wsl.conf with this configuration:
sudo tee /etc/wsl.conf >/dev/null <<'EOF'
[boot]
systemd=true
EOFThis enables systemd for the distribution. It is required for the documented WSL Gateway setup.
3. Restart WSL
Exit the Linux shell, return to PowerShell, and shut down the running WSL instance:
wsl --shutdownStart Ubuntu again after the shutdown. The distribution will now boot with systemd enabled.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #3
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
4. Install OpenClaw inside Ubuntu
In the Ubuntu shell, run the Linux installer:
curl -fsSL https://openclaw.ai/install.sh | bashThe script installs OpenClaw in the Linux environment, separate from any native Windows installation. A native PowerShell installation and a WSL installation therefore have separate runtimes, PATHs, and package locations.
5. Check the Gateway
Still inside Ubuntu, run:
openclaw gateway statusUse the status result to confirm that the WSL Gateway is available. If you also use Windows Hub, point the Hub at this existing Gateway rather than provisioning another one.
Windows Hub versus PowerShell versus WSL2
The three routes are not simply different download buttons. They place OpenClaw in different operating environments and suit different operating habits.
| Decision question | Windows Hub | PowerShell | WSL2 |
|---|---|---|---|
| Do you want a guided desktop setup? | Yes | No; command-line setup | No; Linux shell setup |
| Do you want native Windows tray integration? | Yes | No companion interface by default | No, unless paired with Windows Hub |
| Do you need Linux-compatible services? | Only when it provisions or connects to WSL | Not primarily | Yes; this is its main advantage |
| Do you need administrator elevation? | Not for the Hub installer | Depends on your package-management and Windows policies | Depends on Windows policy during WSL installation |
| Where does OpenClaw run? | Native companion, with an app-owned or connected Gateway | Native Windows environment | Inside the selected Linux distribution |
| Main troubleshooting area | Hub setup or Gateway connection | PATH, Node.js, Git, or PowerShell | WSL distribution, systemd, Linux PATH, or Gateway service |
Use one primary Gateway environment at a time unless you deliberately need separate native and WSL installations. Installing OpenClaw in both environments does not automatically make them share configuration or status.
Verify an installation completely
Do not stop after the installer window closes. Perform these checks in a newly opened shell or in the WSL distribution where you installed OpenClaw.
- Confirm that the installer finished without an error.
- Close and reopen PowerShell, or restart the WSL shell, so newly written PATH entries are loaded.
- Run
openclaw --versionand confirm that a version is printed. - Run
openclaw gateway statusand inspect the Gateway state. - If you skipped onboarding with
-NoOnboard, complete onboarding later rather than treating the installation as fully configured.
Run the commands in the same environment where you installed OpenClaw. A command that works in Ubuntu WSL is not evidence that the native PowerShell command is installed, and vice versa.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix “openclaw is not recognized” after PowerShell installation
The installer documentation identifies PATH as the most common reason a completed installation leaves the command unavailable.
1. Open a new shell first
Close every PowerShell window that was open during installation and start a new one. This is the least invasive fix because PATH changes are often read only when a process starts.
2. Find npm’s global prefix
Run:
npm config get prefixCopy the directory printed by the command. This is the user-level location that must be discoverable by PowerShell.
3. Add the prefix itself to PATH
Add the exact prefix directory to your user PATH, but do not append bin. On Windows, appending a Linux-style bin folder to this npm prefix is a common mistake and can leave the executable undiscoverable.
4. Reopen PowerShell and test again
Start another new PowerShell window, then run:
openclaw --versionIf the command now returns a version, the installation was present and only the shell’s PATH was incomplete.
Recommended Free Tools
Rank #4
- Video Link to instructions and Free support VIA Amazon
- 24/7 Tech Support!
- key code included
Fix unsupported Node.js runtime errors
OpenClaw supports Node.js 24.16 or newer and 26.1 or newer, with Node.js 26 recommended. A runtime below those supported versions can cause the installer or OpenClaw command to fail.
Check the runtime that PowerShell is using
node --versionCheck the version in the same shell where you run OpenClaw. Multiple Node installations can place different executables earlier in PATH, so a version shown by another terminal is not sufficient.
Let the installer provide portable Node.js
Rerun the official PowerShell installer. It first attempts winget, Chocolatey, or Scoop. If those methods are unavailable or produce an unsupported runtime, the script can download portable Node.js 26 under:
%LOCALAPPDATA%OpenClawdepsportable-nodeThis user-local fallback avoids requiring a system-wide Node installation.
Fix Git-related installation failures
The default installation method is global npm, but dependencies may still require Git. If the installer reports Git-related errors, rerun the PowerShell installer so it can bootstrap user-local MinGit, or install Git for Windows and then run the installer again.
After rerunning, open a fresh PowerShell window and repeat both verification commands:
openclaw --version
openclaw gateway statusFix WSL Gateway problems
The distribution is missing
Run wsl --list --online to see available distributions, then install Ubuntu explicitly with wsl --install -d Ubuntu-24.04. If Windows requests a restart, restart before trying to launch the distribution.
systemd changes do not take effect
Check that /etc/wsl.conf contains the exact [boot] section with systemd=true. Then exit the distribution, run wsl --shutdown from PowerShell, and start Ubuntu again. Editing the file without shutting down WSL leaves the existing instance running with its old configuration.
The Linux command works but Windows Hub cannot connect
Confirm that the Gateway is running in the same WSL distribution where OpenClaw was installed. In Windows Hub, use its option to connect to an existing Gateway instead of starting a second app-owned Gateway. The native and WSL environments have separate command paths and service state.
Which installation should you use?
- Choose Windows Hub if you want the least command-line work, tray status, diagnostics, chat, and Windows node capabilities.
- Choose PowerShell if you are comfortable in Windows terminals and want a native CLI/Gateway installation.
- Choose WSL2 if Linux compatibility, Linux automation, or an existing Ubuntu workflow is the deciding factor.
- Combine Windows Hub with WSL2 when you want the Hub’s desktop controls while keeping the Gateway in a Linux-compatible environment.
Whichever route you choose, verify both the OpenClaw version and Gateway status in the environment where you installed it. That two-command check catches most incomplete setups before you begin using the service.
Frequently Asked Questions
Can I install OpenClaw on Windows without administrator rights?
Yes. Windows Hub is designed to install without administrator privileges. PowerShell and WSL2 permissions depend on your Windows package-management and organization policies.
Do native Windows and WSL2 installations share the same OpenClaw installation?
No. They run in separate environments with separate PATHs and package locations. Install and verify OpenClaw in the environment where you intend to run its Gateway.
What Node.js version should I use?
Use Node.js 24.16 or newer, or 26.1 or newer. Node.js 26 is the recommended version line.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
