Adding a folder to the PATH environment variable makes command-line tools runnable from any working directory without typing full executable paths. A correctly configured PATH simplifies scripting, build steps, and day-to-day terminal work by keeping common commands consistently available.
On Windows, executable lookup checks the current directory and then searches each directory listed in PATH in order. The Environment Variables editor maintains separate values for User variables and System variables, and new processes inherit updated values only after the change is saved.
Incorrect edits can change which executable runs for a given command name or break tools that depend on existing entries. Prefer adding trusted directories only, avoid deleting or overwriting current entries, and reopen terminal sessions after changes so new processes load the updated PATH.
The search shortcut opens the System Properties dialog used for editing PATH.

Editing the system-wide Path typically requires administrator permission and affects all users.
Removing or overwriting existing entries can break built-in commands and installed applications.

Enter a directory path only (for example C:\Program Files\7-Zip), and avoid adding untrusted writeable folders. Ordering matters when multiple executables share the same name.


Already-open terminal windows keep the old PATH value until restarted.
C:\> where 7z C:\Program Files\7-Zip\7z.exe
If INFO: Could not find files appears, re-check the folder entry and reopen the terminal session.