Libxa Desktop 0.8.3

Two bugs that kept Node and PHP resolving to the old install even after the elevated fix reported success.

Shims left as empty directories

The elevated step created a real, empty directory exactly where the junction had to go. That directory then sat at the front of the machine PATH resolving nothing — so the runtime you replaced kept winning, and the panel had no way to explain why.

Now only the shim's parent is created; the junction is made in one place, a stray plain directory is cleared out of the way, and the result is verified afterwards (mklink can report success while leaving nothing usable behind).

Machines already in this state repair themselves. Opening the PHP, Node or Python tab recreates a shim that exists but isn't a link — safe, because it only restores a link you already asked for.

pip resolved to the wrong Python

python-build-standalone ships pip as an importable module but doesn't generate its console scripts, so Scripts\ contained only a placeholder. The directory was on PATH, and ahead of other installs — yet pip still resolved elsewhere while python -m pip worked fine, which is a genuinely confusing way to fail.

ensurepip doesn't help (it sees pip already installed). Reinstalling the pip package is what regenerates the scripts, and activating a Python now does that first.

Verified end to end

On a machine where all three were shadowed by machine-scope installs:

	before	after
node	25.6.0	26.7.0
npm	—	11.19.0
php	8.4.19	8.5.9
python	3.14.2	3.10.21
pip	25.3 (wrong Python)	26.2.1

All five now resolve through the shims, matching what the app shows.

Install

Download libxa-desktop-0.8.3-x64.exe below. Windows x64. Existing installs update automatically.