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

Inno "Installed apps" registration stays at the original version after in-app updates — the stale-metadata sequence behind #1592

Open
  • Is something wrong?
#1,676 4 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
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

Start with App.xaml.cs and inspect how Updatum applies updates and whether it refreshes the Inno uninstall registration. Then examine the Inno Setup script to see how upgrades handle the existing _is1 key. Define the fix with maintainers, covering successful in-app updates and Setup reinstalls, and verify that Windows' registered display version matches the installed executable.

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2

Summary

The Windows uninstall registration for the Inno-installed Companion (HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\{M0LTB0T-TRAY-4PP1-D3N7}_is1) keeps the version and install date of the first install after the app is upgraded, both by the built-in updater and by running a newer OpenClawCompanion-Setup-x64.exe. Settings → Apps and anything that reads this key (support checks, inventory tools, and possibly the Store migration's previous-installation validation, see #1592) see a version that no longer exists. #1592 notes that "the earlier update sequence that produced the stale registration has not been established"; this report documents one such sequence.

Environment

  • Windows 11 Home, build 10.0.26300, x64; per-user Inno install in %LOCALAPPDATA%\OpenClawTray
  • Inno Setup version recorded in the key: 6.7.1

Sequence observed (one machine, all dates 2026)

Date Action Exe version afterwards Uninstall key afterwards
Oct 3 Fresh Setup install, v2026.9.5-alpha.93 2026.9.5-alpha.93 DisplayVersion 2026.9.5-alpha.93, InstallDate 20261003
Oct 5 ~19:59 Ran OpenClawCompanion-Setup-x64.exe for v2026.9.5-alpha.97 over the existing install (signature valid, SHA-256 matched the release asset) 2026.9.5-alpha.97 unchanged: still 2026.9.5-alpha.93 / 20261003, although unins000.exe/unins000.dat in the install folder were rewritten at 2026-10-05 19:59 (so Setup did run)
Oct 7 21:00 Built-in updater: "Update available: v2026.9.8-1" → Download → "Installing update and restarting..." 2026.9.8-1 (2026.9.8-1+2ba89f37…, signature Valid, OpenClaw Foundation) unchanged: still 2026.9.5-alpha.93 / 20261003
Oct 7 21:04 Windows reboot 2026.9.8-1 unchanged

Current key (non-sensitive fields): DisplayName = OpenClaw Companion version 2026.9.5-alpha.93, DisplayVersion = 2026.9.5-alpha.93, InstallDate = 20261003, MajorVersion = 2026, MinorVersion = 9, Publisher = OpenClaw Foundation, InstallLocation = %LOCALAPPDATA%\OpenClawTray\, Inno Setup: Setup Version = 6.7.1.

Likely causes (two paths)

  1. Built-in updater: App.xaml.cs configures Updatum with InstallUpdateSingleFileExecutableName = "OpenClaw.Tray.WinUI", so the in-app update replaces the program files directly rather than running the Inno installer, and nothing rewrites the Inno uninstall key. Every in-app update widens the gap between the registration and the real version.
  2. Setup reinstall: a newer Setup run over an existing install rewrote unins000.* but did not refresh DisplayVersion/DisplayName/InstallDate in the existing _is1 key. I haven't determined why (installer script settings vs. Inno behavior with this AppId).

Expected

After any successful upgrade path, the uninstall registration reflects the installed version (at least DisplayVersion/DisplayName), so Settings → Apps, support diagnostics and the Store migration's previous-installation checks see the truth.

Suggested direction (maintainers' call)

  • After an in-app update succeeds, refresh DisplayVersion/DisplayName (and optionally MinorVersion/InstallDate) in the Inno _is1 key, or have the updater run the signed Setup package instead of replacing files.
  • Check that the Setup script updates the existing uninstall key on reinstall.
  • For #1592: if migration validation reads this key, validate against the executable's version (or both), since the key can be stale.

Screensnip of the previous version showing in Windows' "Settings"->"Apps"

Image
Dominant language
C#
Stars
2.2k
Forks
321
Avg merge
4d 14h
Merged PRs (30d)
187

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.