This is an emergency fix applicable only to Windows. It appears that a change in our CI/CD pipeline for Windows builds has occurred, likely related to the version of Inno Setup used in the windows-latest runner image from GitHub Actions.

The issue emerges post-installation: while %LOCALAPPDATA%/Robomotion/bin is added to the PATH, it does not become immediately active. Opening a new Command Prompt and verifying with echo %PATH% does not reveal this path, although it is listed in the PATH under Environment Variables when checked manually. The path becomes active only after either rebooting the system or by adding any other entry to the PATH variable, which also triggers the activation of the PATH added by the Robomotion Installer.

The problem did not occur if your PATH already included %LOCALAPPDATA%/Robomotion/bin.

Incorporating ChangesEnvironment=yes into the Inno Setup script has resolved the issue of PATH resolution when a new Command Prompt process is initiated following installation.

To further address this issue, we have developed an additional launcher binary. This launcher internally adds the PATH before launching robomotion-tray.exe. This solution allows the launcher to function immediately after installation or when double-clicked, without encountering any PATH issues.