Doing this is very likely to break your computer, in the sense of invoking DLL Hell. As you invoke each executable, the OS will look through each directory in PATH
to find each DLL or even EXE referenced by that executable. It becomes highly likely that the OS will find the wrong ones as you add more directories to the PATH
.
So, a best practice is to avoid increasing the PATH
, and even to decrease it. Rather than implicit dependencies, make them explicit.
Instead, I recommend this approach:
- Create a
bin
directory within your user home directory
- Add that
bin
directory to your user PATH
variable
- Create a Windows CMD script in the
bin
directory for each application that you want to invoke from the command line (same name as the executable that you would type)
- In each script, invoke
SetLocal
, add the application's install directory (under %ProgramFiles%
) to the PATH
, then invoke the executable with the arguments from the command line
- Remove the relevant directory from the
PATH
, so that this script becomes the only way to invoke the executable