openclaw / openclaw/openclaw-windows-node

Windows Companion (WinUI) crashes with System.ArgumentException: The parameter is incorrect when opening a chat session

Open
#1,419 1 comment 1 reaction 2 assignees View on GitHub

@bkudiess is already working on this.

Since Sep 14, 2026.

impact:crash-loop impact:ux-release-blocker issue-rating: 🦪 silver shellfish P0
Dominant language
C#
Stars
2.1k
Forks
295
Avg merge
1d 6h
Merged PRs (30d)
99

Description

Describe the bug
The Windows Companion app (OpenClaw.Tray.WinUI) crashes consistently when opening/viewing a chat session. It connects and authenticates with the Gateway successfully, then crashes ~1 second after loading the session's message history or receiving live agent events. No data loss — the Gateway, Telegram channel, and browser Control UI all keep working.

To Reproduce

  1. Install OpenClawCompanion-Setup-x64.exe (v2026.9.3, code-signed build) on Windows 11 (build 26200, x64)
  2. Pair the app to a locally running Gateway (ws://127.0.0.1:18789, token auth)
  3. Open a session that has a large message history (months of messages incl. tool output)
  4. App crashes within ~1s of loading the chat view — repeatable every time

Expected behavior
Chat view renders and stays open; can read and send messages.

Actual behavior
Unhandled System.ArgumentException: The parameter is incorrect. in the WinUI layer; app terminates. Repeatable on every open of the chat view. Crash log shows it immediately after the Gateway returns the full session payload (e.g. Wizard response payload ... len=~276321-339587), i.e. during chat-history rendering.

Crash evidence

• crash.log: System.ArgumentException: The parameter is incorrect. (multiple entries, e.g. 20:00:44, 20:05:00, 20:21:11)
• openclaw-tray.log sequence: handshake complete → chat.history sent → large Wizard response payload → CRASH
• Event Log (Application) also shows WinUI faulting module Microsoft.UI.Xaml.dll and coreclr.dll; exceptions 0xc000027b (stowed/HREXAML) and 0xc0000005 (access violation)

Check first

• Gateway is healthy: other clients (browser Control UI, Telegram) work fine
• Not auth/pairing related — handshake completes and operator scopes granted before crash
• App version 2026.9.3.0; no updates available in-app; v2026.9.4-alpha.1 published but notes mention only MSIX/Store packaging

Happy to attach crash.log and openclaw-tray.log on request.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.