> What isn’t fine, is that they’re stored in the Windows Registry, apparently? If you update these, either using setx %var% value, or the GUI… you have to rest

> What isn’t fine, is that they’re stored in the Windows Registry, apparently? If you update these, either using setx %var% value, or the GUI… you have to restart your shell - i.e. you type exit, the window/tab goes away, and you open another one. Just let that sink in for a moment. I mean, it's the same story, sort of, on Linux. Edit your profile, rc files, whatever on Linux to define/change an environment variable, and it doesn't magically update in your current shell, either. Use "set" instead of "setx" and it'll affect the current shell, but not other currently running processes. Change your profile? Yeah, restart whatever app to pick up the changes. Somehow expecting this to change environment variables of already running processes? Yeah, no, not so much. Doesn't work that way on Linux, either. Processes inherit env variables from the parent process by default on both Linux & Windows. Not really sure what the concern or issue is here other than a lack of understanding of how environment variables work.