Windows installer is truncating the user's `PATH` variable about desktop HOT 1 OPEN

Nice catch!

From what I see, there are a few possible workarounds:

1. Edit that env var in the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment) but that doesn't broadcast WM_SETTINGCHANGE to other processes so they can grab he new value. I see some ideas like using setx right after that to set a variable to its own value.
2. Write a native Node module that uses System.Environment.SetEnvironmentVariable and use that instead of setx.
3. Use a PowerShell script to do this job with [Environment]::SetEnvironmentVariable('PATH', "$newPath",'Machine');
4. Detect when the resulting PATH is longer than 1024 and don't do anything in that case (other than somehow surface that problem to the user).

With registryjs (1) should be pretty simple, although I can't tell how reliable that hacky use of setx right afterwards is. (3) also sounds simple but not sure if there could be other potential issues with the use of external scripts.

from desktop.