Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Sluggish response time and unstable Web GUI and CLI on Windows Server 2022 [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#72922•Fetched 2026-04-28 06:30:14
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Author
jondeafjondeaf
Participants
ExLiNK05ExLiNK05jimdawdy-hubjimdawdy-hubjondeafjondeaf
Timeline (top)
commented ×2labeled ×1

OpenClaw appears to be unstable and very slow when installed natively on Windows Server 2022. The Gateway service does not consistently stay running, and the Web GUI either loads very slowly or fails to work.

Error Message

  • OpenClaw responds very slowly on Windows Server 2022.
  • Web GUI does not work reliably.
  • Gateway sometimes shows as installed but stopped.
  • Health check fails with connection refused:

Root Cause

OpenClaw appears to be unstable and very slow when installed natively on Windows Server 2022. The Gateway service does not consistently stay running, and the Web GUI either loads very slowly or fails to work.

Code Example

connect ECONNREFUSED 127.0.0.1:18789

### Steps to reproduce

1.Install Openclaw in Windows 2022 or Windows 10 using Powershell.
2.powershell -c "irm https://openclaw.ai/install.ps1 | iex"

### Expected behavior

Gateway should remain running after installation/start.
Web GUI should load normally from http://127.0.0.1:18789/.
OpenClaw should respond normally without long delays.
Windows scheduled task should start the same working gateway process as manual foreground execution.

### Actual behavior

OpenClaw is very slow to respond when installed natively on Windows Server 2022.

The Web GUI does not reliably load from:

http://127.0.0.1:18789/
Gateway sometimes shows as installed, but the runtime is stopped.

Health checks fail with:

connect ECONNREFUSED 127.0.0.1:18789

Port test fails when the Gateway is not running:

TcpTestSucceeded : False

In some attempts, the CLI/Gateway fails with:

Failed to start CLI: Error: PlatformAdapter not registered

Manual foreground Gateway startup may work:

openclaw gateway --port 18789 --verbose

But the Gateway does not appear stable when launched through the Windows

### OpenClaw version

2026.4.25

### Operating system

Windows 2022 Server

### Install method

_No response_

### Model

kimi 2.6

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

OpenClaw appears to be unstable and very slow when installed natively on Windows Server 2022. The Gateway service does not consistently stay running, and the Web GUI either loads very slowly or fails to work.

Environment

  • OS: Windows Server 2022
  • Platform: Windows VM running under Proxmox
  • Runtime: Node.js 24.x
  • OpenClaw install method: npm global install
  • Gateway port: 18789
  • Web GUI URL: http://127.0.0.1:18789/

Observed behavior

  • OpenClaw responds very slowly on Windows Server 2022.
  • Web GUI does not work reliably.
  • Gateway sometimes shows as installed but stopped.
  • Health check fails with connection refused:
connect ECONNREFUSED 127.0.0.1:18789

### Steps to reproduce

1.Install Openclaw in Windows 2022 or Windows 10 using Powershell.
2.powershell -c "irm https://openclaw.ai/install.ps1 | iex"

### Expected behavior

Gateway should remain running after installation/start.
Web GUI should load normally from http://127.0.0.1:18789/.
OpenClaw should respond normally without long delays.
Windows scheduled task should start the same working gateway process as manual foreground execution.

### Actual behavior

OpenClaw is very slow to respond when installed natively on Windows Server 2022.

The Web GUI does not reliably load from:

http://127.0.0.1:18789/
Gateway sometimes shows as installed, but the runtime is stopped.

Health checks fail with:

connect ECONNREFUSED 127.0.0.1:18789

Port test fails when the Gateway is not running:

TcpTestSucceeded : False

In some attempts, the CLI/Gateway fails with:

Failed to start CLI: Error: PlatformAdapter not registered

Manual foreground Gateway startup may work:

openclaw gateway --port 18789 --verbose

But the Gateway does not appear stable when launched through the Windows

### OpenClaw version

2026.4.25

### Operating system

Windows 2022 Server

### Install method

_No response_

### Model

kimi 2.6

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix is to investigate and resolve the instability of the OpenClaw Gateway service on Windows Server 2022, potentially by checking the service configuration, dependencies, and system resources.

Guidance

  • Verify the Gateway service status and logs to identify any error messages or patterns that could indicate the cause of the instability.
  • Check the system resources (CPU, memory, disk space) to ensure they are sufficient for the OpenClaw Gateway service to run smoothly.
  • Compare the behavior of the Gateway service when started manually in the foreground versus when launched through the Windows scheduled task to identify any differences in the environment or configuration.
  • Investigate the "PlatformAdapter not registered" error to determine if it is related to the instability of the Gateway service.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be related to the specific environment or configuration of the Windows Server 2022, and further investigation is needed to determine the root cause. The fact that the Gateway service works when started manually in the foreground but not when launched through the Windows scheduled task suggests that there may be a difference in the environment or configuration between the two scenarios.

Recommendation

Apply workaround: Investigate and resolve the instability of the OpenClaw Gateway service on Windows Server 2022, potentially by checking the service configuration, dependencies, and system resources, as this is likely to be a more effective solution than upgrading to a different version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Gateway should remain running after installation/start. Web GUI should load normally from http://127.0.0.1:18789/. OpenClaw should respond normally without long delays. Windows scheduled task should start the same working gateway process as manual foreground execution.

#installation#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Sluggish response time and unstable Web GUI and CLI on Windows Server 2022 [2 comments, 3 participants]