However, I also launch console windows and other things directly from FARR; these also get the old environment settings.
If I restart FARR, then the new environment settings are propagated.
In the latter case, Windows searches for the executable in a list of folders which is configured in environment variables. Initially user specific path environment variable will be empty.
Users can add paths of the directories having executables to this variable.
Administrators can modify the system path environment variable also.
In Vista, Windows 7 and Windows 8 we can set path from command line using ‘setx’ command.
In the “System Variables” box, look for a variable called Path. This is where things are different between the versions of Windows—it’s the same for 7 and 8, but slightly different (and easier) in Windows 10. In Windows 10, this process is both easier and less confusing.
In 7 and 8, the variable value for Path is nothing more than a long string of text with various locations around the system. Once you’ve clicked the edit button, a new dialog box will appear with each location in the path on a separate line.
Now in the new window that comes up, select Environment Variables... @Alex Szabó: I was wrong when I said "no longer produces such result". But clicking of the first result (highlighted in your picture) in current Windows 10 does nothing for non-admin accounts. This is the same bug, introduced by 1511 update as the one described in my answer. As for the bug, I have a fresh install of Win10 with latest patches/upgrades as of this date (2016-08-06, winver 10.0.14393) and searching for "variable" in menu start produced correct 2 hits (edit-vars-for-system and edit-vars-for-this-account). "account" version does not require them and works correctly.
** UPDATE ** I switched to linux & later to mac so I really don’t spend any time in Windows anymore, but it seems I get a lot of traffic and the most useful information is in this comment below… Here is how I do it (I’m really hoping someone will comment and tell me a better way) … (But it will not work in all cases, which is why I don’t like it, so please, if you know of a batch script or something I can run that will apply the changes made to the environment variables without reboot, please post a comment.) Open a comment window and type SET PATH=%PATH%; C:\Cmd Shortcuts You can type PATH again to see your path variables. The problem with this is that this new path variable is only good inside this command window.
— I find it quite annoying that whenever I read instructions that include adding an environment path variable you are asked to reboot your machine for changes to take effect. If you are doing command line stuff this works, but if you close your cmd window the change is lost.
In the old MS-DOS environment we used the PATH= command, located in the file.
Additional information about the MS-DOS path command that is still usable in Windows 2000 and Windows XP can be found on our path command page, additional information about the MS-DOS command can be found on our set command page.