Windows Companion v2026.9.4: Allow Windows UI APIs reverts to false after confirmation/relaunch
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- csharp, nodejs, powershell
- Domain
- desktop, operating-systems
Research direction
Reproduce the confirmation and relaunch flow, then trace where SystemRunAllowWindowsUi is persisted and reloaded in settings.json. Compare the setting with allowWindowsUi and uiAllowWindows in the MXC logs, and rerun the documented Node PowerShell checks. Done means the toggle and settings.json remain true after relaunch and later executions succeed.
Written by the indexing model from the issue text.
Description
Environment:
- Windows 11 build 26200.9457
- Companion v2026.9.4, Unpackaged
- Gateway v2026.9.6
Observed:
- Enable Allow Windows UI APIs and confirm the warning.
- settings.json shows "SystemRunAllowWindowsUi": true.
- Node PowerShell tests succeed: "node-ok", exitCode 0.
- Later executions fail with 0xC0000142.
- MXC logs show allowWindowsUi=False and uiAllowWindows=False.
- After closing and reopening Companion, the toggle is Off and
settings.json shows "SystemRunAllowWindowsUi": false.
The exact point and cause of the setting being overwritten are unknown.
Local PowerShell works. Node cmd.exe /c dir can read Downloads.
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 315
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 135
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openclaw/openclaw-windows-node
-
clawsweeper:source-repro impact:ux-release-blocker issue-rating: 🦞 diamond lobster P0
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openclaw/openclaw-windows-node#1723 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openclaw/openclaw-windows-node#1516 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-info clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🦐 gold shrimp P1 stale
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openclaw/openclaw-windows-node#1145 · 5 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
openclaw/openclaw-windows-node#1755 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug impact:ux-friction issue-rating: 🦪 silver shellfish P2
Difficulty 3/5 Half a day Newbie friendliness 50/100
openclaw/openclaw-windows-node#1753 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in openclaw/openclaw-windows-node
Similar issues
-
area: design documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eyalgolan/statecraft-israel#883 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
area/indexing bug package/core triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
elastic/docs-builder#4495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day