The command runs an older installation than expected

Identify the selected executable

A working GUI shortcut and a terminal command can start different installations. The Windows review found this situation directly; a successful launch alone did not identify the intended release.

# PowerShell: list the commands found, in resolution order
Get-Command inductex -All
Get-Command josim-pro-cli -All

# Linux/macOS: show the selected command
command -v inductex
command -v josim-pro-cli

Check and correct the intended route

1. Run the version command using the full executable path. InductEx® 8 documents --version and --build-info; JoSIM®-Pro documents -v.
2. Compare the result with the article's version and the package you intended to install.
3. Use the full path for the diagnostic run. Repair the appropriate installer/PATH configuration and open a new terminal when changing command discovery.
4. Repeat the small example with the intended tool and matching inputs. Preserve existing installations until their role and removal procedure are understood.

Keep component versions separate

InductEx®, Studio, TetraHenry®, JoSIM®-Pro and the daemon have separate identities. Do not infer the engine or broker version from the frontend's version number.