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

[Bug]: Store uninstall leaves managed Gateways behind and reinstall does not refresh them

Closed
  • Is something wrong?
#1,712 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
43/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend, devops

Research direction

Start with NativeGatewayPackageAcquisition.cs and NativeGatewayMsixInstaller.cs, which the report identifies as skipping acquisition for installed packages and disabling WinGet upgrades. Trace the WSL and native setup and uninstall paths, then check how Companion-managed Gateway ownership is tracked. Done means uninstall removes only Companion-managed Gateways and their owned artifacts, while reinstall checks compatibility and updates outdated managed Gateways; validate the listed uninstall, reinstall, and application update cases.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🦪 silver shellfish P2

Bug

Windows Settings uninstall leaves Companion-managed Gateways installed. Reinstalling the latest Store Companion does not ensure that the retained Gateway is current and compatible, making reinstall ineffective as a recovery step.

Reproduction

  1. Install Store Companion with an existing app-managed local Gateway.
  2. Uninstall Companion through Settings > Apps > Installed apps and inspect the Gateway.
  3. Reinstall the current Store Companion, launch it, and inspect the Gateway version again.

Actual behavior

Observed on Windows 11 ARM64, build 28000.2525:

Stage Store Companion WSL Gateway CLI
Before uninstall 2026.9.803.0 2026.9.8
After uninstall Package absent 2026.9.8, distro retained
After reinstall and launch 2026.9.803.0 2026.9.8, unchanged

A separate Store Gateway MSIX 2026.9.900.0 also survived Companion removal. It was acquired directly through WinGet because native onboarding was unavailable on the test host.

This used a pre-existing WSL Gateway. Full Gateway reprovisioning and a two-version Store Companion upgrade were not exercised.

The inspected native setup path skips acquisition for an installed package and disables WinGet upgrades:

Expected behavior

  • Windows Settings uninstall automatically removes Companion-managed Gateway installations and their owned artifacts. Preserve Gateways outside Companion's ownership.
  • Installation/reinstallation checks Gateway version and compatibility and updates outdated managed Gateways before reuse.
  • Validate WSL and native paths, uninstall while Companion is closed, and application updates that must preserve the Gateway.

Related

#1691 ([Bug] Companion cannot connect: Gateway MSIX missing isolated-session contract) reports a compatibility failure after Companion reinstall with a retained Gateway.

Dominant language
C#
Stars
2.1k
Forks
315
Avg merge
2d 1h
Merged PRs (30d)
127

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.