Install and run OpenClaw on Windows 11

OpenClaw on Windows 11 uses a native binary distribution that packages the complete runtime environment, including Node.js runtime, Python interpreter for skill dependencies, and all required native libraries. This approach eliminates dependency on Windows Subsystem for Linux or separate package manager installations that introduce configuration complexity.

The native binary approach ensures consistent behavior across Windows versions and configurations by shipping known-good dependency versions rather than relying on system-installed packages that may vary between machines. When you deploy OpenClaw across multiple Windows machines, each installation uses identical runtime versions.

Windows Defender and other antivirus software may interfere with the installation process or flag the OpenClaw binary as potentially unwanted software. Configure antivirus exceptions before installation to prevent blocked operations during the installation sequence.

Verify your Windows 11 installation is current by checking for available updates in Settings Windows Update. The installation requires the latest cumulative updates to ensure compatibility with the bundled runtime components. Open PowerShell as Administrator and run the health verification prerequisites before downloading the installer.

Approximately 2GB of free disk space is required in the installation directory and working data location. The default installation path is Program Files OpenClaw, but you can specify an alternative location during installation if your system drive has limited capacity.

Windows Firewall may prompt you to allow network access during installation when the agent attempts to verify its license and check for updates. Allow both inbound and outbound connections on private networks to ensure full functionality for model provider communication.

If you have an existing OpenClaw installation from an earlier version, use the uninstall utility before installing the new version to cleanly remove previous files and prevent architecture conflicts between old and new binary formats.

Download the Windows installer executable from the official releases page. Verify the file signature using the provided SHA256 checksum to confirm the package has not been tampered with during download. Right-click the downloaded file and select Run as Administrator to initiate the installation with necessary privileges.

The installer presents options for installation directory, whether to add OpenClaw to the system PATH for command-line access, and whether to create a desktop shortcut for the management interface. Accept the defaults unless your organization requires non-standard installation paths for compliance reasons.

During installation, the binary extracts bundled runtime components and creates the necessary directory structure for configuration files, log files, and working data. This process takes approximately two to three minutes depending on disk performance.

When installation completes, the installer displays a summary with the installed version, installation path, and instructions for accessing the management interface. It will also prompt you to run initial verification before closing.

Windows Defender SmartScreen may warn about the installer or flag the installed binary after installation. This occurs because the binary is not yet widely recognized by Microsoft's reputation database. After confirming the installer checksum is correct, you can dismiss the warning and proceed.

To prevent future interference, add the OpenClaw installation directory to Windows Defender exclusion lists. Open Windows Security, navigate to Virus and threat protection settings, and add an exclusion for the directory where OpenClaw is installed. This prevents antivirus scans from interrupting agent operations.

If your organization uses third-party antivirus software, consult the antivirus documentation for adding application exclusions. Most enterprise antivirus products support directory or process exclusions that allow OpenClaw to operate without interference.

After configuring exclusions, run the health verification command in PowerShell to confirm the agent can access all necessary resources without antivirus blocking. Successful verification indicates the exclusion configuration is correct.

The installer configures system PATH entries automatically when you select that option during installation. Open a new Command Prompt or PowerShell window after installation completes to access the openclaws command from any directory without specifying the full installation path.

The command-line interface provides management operations including health verification, configuration editing, log access, and service management. The command interface is particularly useful for automation scripts and CI/CD pipeline integration.

If the PATH configuration fails during installation or you need to reconfigure it later, manually add the OpenClaw binary directory to your user or system PATH environment variable. The default binary directory is C Program Files OpenClaw bin on English-language Windows installations.

Test PATH configuration by running openclaws version in a new terminal window. Successful output confirms the command-line interface is accessible and the agent binary can execute properly.

After installation and health verification pass, run a simple validation task to confirm end-to-end functionality. The validation task should be something straightforward that exercises model connectivity and basic task execution without depending on advanced capabilities like browser relay.

Enable verbose logging during the validation run by setting the environment variable OPENCLAWS_LOG_LEVEL to debug before executing the task. Detailed logs help identify any warnings or degraded functionality that does not prevent task completion but may cause issues under specific conditions.

Windows-specific logging considerations include log file rotation to prevent the log directory from filling the system drive, and appropriate permission configuration for the log directory to allow the agent to write operational data.

Schedule periodic health verification using Windows Task Scheduler to detect configuration drift or antivirus exclusion issues before they impact production task execution. A nightly health check with alerting ensures proactive maintenance.