Why We Tested on Server 2019 #

We had a Windows Server 2019 environment running in-house, and we wanted to control that server directly with OpenClaw. With WSL2, the Linux environment becomes isolated, and access to Windows file systems, processes, and registry becomes mediated through the WSL boundary. With native Windows installation, OpenClaw can call Windows APIs directly, which makes sense for server operation use cases.

Environment Configuration #

The Journey to Confirming WSL2 Unavailability #

Initially, we followed the official documentation and tried wsl --install. However, we hit issues right from the start.

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

After investigation, the root cause became clear: Windows Server 2019 is incompatible with WSL2, and Microsoft has decided not to backport it. WSL2 is only available on Windows Server 2022 and later.

Pitfalls List #

Complete Installation Procedure #

1. Install Git for Windows

   curl.exe -L -o git.exe "https://github.com/git-for-windows/git/releases/download/v2.47.1.windows.1/Git-2.47.1-64-bit.exe"
   .\git.exe /VERYSILENT /NORESTART
   Start-Sleep -Seconds 30

   Close and reopen PowerShell.
2. Manually install Node.js 22 LTS

   curl.exe -L -o nodejs.msi "https://nodejs.org/dist/v22.14.0/node-v22.14.0-x64.msi"
   msiexec /i nodejs.msi /quiet /norestart
   Start-Sleep -Seconds 30

   Close and reopen PowerShell, verify with node --version.
3. Enable script execution and set up pnpm

   Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force
   npm install -g pnpm
   pnpm setup

   Close and reopen PowerShell.
4. Install OpenClaw with pnpm

   pnpm add -g openclaw@2026.4.5

5. Approve build scripts and reinstall

   pnpm approve-builds -g
   # Select all (space to select all) → Enter → y
   pnpm add -g openclaw@2026.4.5

   OpenClaw build takes approximately 2 minutes.
6. Persist PATH at Machine level

   $paths = @(
     'C:\Program Files\nodejs',
     "$env:APPDATA\npm",
     "$env:LOCALAPPDATA\pnpm"
   )
   $current = [System.Environment]::GetEnvironmentVariable('PATH','Machine')
   $entries = ($current -split ';') + $paths | Select-Object -Unique
   [System.Environment]::SetEnvironmentVariable('PATH', ($entries -join ';'), 'Machine')
   $env:PATH = ($entries -join ';')

7. Onboarding

   $env:NODE_OPTIONS=""
   openclaw onboard

   Select Custom Provider for model provider, GPUStack /v1 endpoint as Base URL, and OpenAI-compatible for compatibility.
8. Manually fix contextWindow

   $config = Get-Content "$env:USERPROFILE\.openclaw\openclaw.json" | ConvertFrom-Json
   $config.models.providers.'custom-10-255-253-205'.models[0].contextWindow = 32768
   $config.models.providers.'custom-10-255-253-205'.models[0].maxTokens = 8192
   $config | ConvertTo-Json -Depth 20 | Set-Content "$env:USERPROFILE\.openclaw\openclaw.json" -Encoding UTF8

   Adjust provider name to match your environment.
9. Launch Gateway and verify operation

   $env:NODE_OPTIONS=""
   openclaw gateway run

   Once [gateway] ready appears, open another window and run openclaw dashboard.

GPUStack Configuration (vLLM Backend Parameters) #

To enable tool use (function calling), add the following to the model’s backend parameters in the GPUStack management dashboard.

--max-model-len 32768
--generation-config vllm
--enable-auto-tool-choice
--tool-call-parser hermes

Session Recovery Procedure #

Repeated context overflow can cause the main session to be recognized as heartbeat, preventing normal conversation. Delete the sessions directory to reset.

openclaw gateway stop
Remove-Item "$env:USERPROFILE\.openclaw\agents\main\sessions" -Recurse -Force
New-Item "$env:USERPROFILE\.openclaw\agents\main\sessions" -ItemType Directory
openclaw gateway run

Operations Support Tool Created: OpenClaw PATH Manager #

To eliminate the manual PATH configuration overhead, we created a PowerShell script and a browser-based diagnostic UI tool.

Contents of ocstart.ps1 #

param([switch]$Stop)

$env:NODE_OPTIONS=""

$paths = @(
  'C:\Program Files\nodejs',
  "$env:APPDATA\npm",
  "$env:LOCALAPPDATA\pnpm"
)
foreach ($p in $paths) {
  if (($env:PATH -split ';') -notcontains $p) { $env:PATH += ";$p" }
}

if ($Stop) {
  Write-Host "Stopping Gateway..."
  & openclaw gateway stop
  exit
}

Write-Host "OpenClaw PATH configured"
Write-Host "openclaw: $((Get-Command openclaw -EA SilentlyContinue).Source)"

$action = Read-Host "[1] Start Gateway  [2] Stop Gateway  [3] Dashboard  [4] TUI  [5] Status`n> "

switch ($action) {
  '1' { openclaw gateway run }
  '2' { openclaw gateway stop }
  '3' { openclaw dashboard }
  '4' { openclaw tui }
  '5' { openclaw gateway status; openclaw doctor }
  default { Write-Host "Cancelled" }
}

Save to Desktop and Create Shortcut #

# Save script to desktop
$script | Out-File "$env:USERPROFILE\Desktop\ocstart.ps1" -Encoding UTF8

# Create shortcut
$ws = New-Object -ComObject WScript.Shell
$sc = $ws.CreateShortcut("$env:USERPROFILE\Desktop\OpenClaw Launcher.lnk")
$sc.TargetPath = "powershell.exe"
$sc.Arguments = '-ExecutionPolicy Bypass -File "C:\Users\Administrator\Desktop\ocstart.ps1"'
$sc.WorkingDirectory = "$env:USERPROFILE\Desktop"
$sc.IconLocation = "powershell.exe,0"
$sc.Save()

Operational Verification Checklist #

• Dashboard displays in browser (http://127.0.0.1:18789)
• Model provider connection shows Verification successful
• Chat gets responses in main session
• GPUStack logs show POST /v1/chat/completions HTTP/1.1" 200 OK
• Gateway is registered as Scheduled Task and auto-starts on login
• SearXNG search is configured
• Session screen TOKENS display shows xxxxx / 32768 (not 16000)

Summary #

Deploying OpenClaw to the unsupported Windows Server 2019 environment proved challenging due to multiple known bugs and environment-specific constraints. The three most critical insights from this work are:

• Use pnpm instead of npm: npm 2026.4.x has a critical bug breaking dependencies
• Check PATH and NODE_OPTIONS every time: They disappear when opening new windows; automate with ocstart.ps1
• Add --enable-auto-tool-choice --tool-call-parser hermes to GPUStack vLLM parameters: Without these, tool use returns 400 error