Windows Companion 2026.9.8-1: "Install Store version and migrate" fails — "Inno DisplayVersion is not a stable numeric release version"

Troubleshooting
1

Environment

  • OpenClaw Companion (Windows tray) 2026.9.8-1, standard per-user install in %LOCALAPPDATA%\OpenClawTray (installed today with the official installer)
  • Windows 11 Home 23H2 (build 22631)
  • Gateway 2026.10.7 running in WSL2 (Ubuntu); the app is connected and working normally

Steps to reproduce

  1. Open Settings → “Move to the Microsoft Store version”.
  2. Click “Install Store version and migrate”.

Result
The app shows: “OpenClaw could not save migration consent or open the Store listing. Check the app log and retry. Do not uninstall this app.” Retrying gives the same error.

openclaw-tray.log:

[WARN] The Inno DisplayVersion is not a stable numeric release version.
[ERROR] Migration consent handoff failed: System.InvalidOperationException: This process is not the supported current-user Inno installation.
   at OpenClawTray.Helpers.InnoMigrationHandoff.InspectOwnInstallation() in ...\InnoMigrationHandoff.cs:line 84
   at OpenClawTray.Helpers.InnoMigrationHandoff.GrantAndLaunchAsync() in ...\InnoMigrationHandoff.cs:line 61

Likely cause
The uninstall entry (HKCU, {M0LTB0T-TRAY-4PP1-D3N7}_is1) has DisplayVersion = 2026.9.8-1. The -1 packaging suffix appears to fail the stable-version check, so the migration rejects what is otherwise the standard current-user Inno install.

Expected
The migration should accept the packaging revision suffix (or treat 2026.9.8-1 as a stable release) and hand off to the Store version.

Workaround
None needed for day-to-day use: the app keeps working. Just skip the Store migration for now and don’t uninstall the app.

2

Hi Macro welcome! This looks like the correction-version issue fixed in openclaw-windows-node#1675⁠. The migration code now accepts versions such as 2026.9.8-1, while still checking that the installed executable matches the registered version.

The Windows Companion 2026.10.8 includes that change. Since the version rejecting the migration is the installed Companion, I’d update the existing Windows app first using the official signed installer for your architecture⁠, then reopen it and check its version before trying the migration again. The WSL Gateway has its own separate version.

Keep the existing installation and its data in place while updating. Don’t edit DisplayVersion in the registry or uninstall the old app to get past this error; follow the migration prompts only when the app has completed its checks.

The fix has been tested with a 2026.9.8-1 source install, although that test used a test-signed package, so I can’t promise the Store migration will work on your machine. If the updated Companion still refuses, could you share the new warning from the log, with personal paths and credentials removed?