Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Windows ARM64] Companion gives misleading build guidance when Native Gateway capability check fails

Open
#1,754 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

Start from the first-run Gateway setup page, where the disabled Native Gateway option shows the Insider build message. Trace that gate to the probes.isolationSessionAvailable capability probe the issue names, since the source review says the gate depends on it rather than on build number. Reproducing needs Windows ARM64 hardware with a matching Insider build, and the root cause is still open, so this is a poor first pick.

Written by the indexing model from the issue text.

Description

bug clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2

Summary

OpenClaw Companion v2026.9.9-alpha.36 can disable the “Install a local native gateway” option while presenting an Insider build requirement that is already satisfied by the current Windows build. The message does not identify the failed capability check or provide useful remediation.

Environment

  • Lenovo Yoga 9 2-in-1 16N1X11 (NVIDIA RTX Spark N1X), Windows ARM64
  • Windows 11 Pro 26H1, build 28000.2956
  • OpenClaw Companion v2026.9.9-alpha.36 (ARM64)

Steps to reproduce

  1. Launch Companion on the above system.
  2. Open the first-run Gateway setup choice page.
  3. Observe Native Gateway disabled and read the guidance.

Expected

When native support is unavailable, identify the failed capability/feature check and give remediation applicable to the current build.

Actual

The UI says: “Native gateway support is unavailable. Install Windows Insider build 26340.9212 or a newer supported build in Windows Update, then reopen this page. Feature availability can vary by device.” The machine was already on build 28000.2956. A Companion capability probe reported probes.isolationSessionAvailable=false; source review indicates the gate depends on this probe rather than a simple build comparison. After Windows updated to build 28000.3231, the option became enabled; the reason for the change is unknown.

Internal tracking: NVBug 6941780.

Dominant language
C#
Stars
2.2k
Forks
321
Avg merge
3d 20h
Merged PRs (30d)
174

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from openclaw/openclaw-windows-node

All issues in openclaw/openclaw-windows-node

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.