Why apps can't find installed tools even when PATH is correctly set on Windows
On Windows, every process inherits a fixed copy of the environment from its parent at launch time, meaning changes to PATH made afterward are not passed to already-running applications. When a tool like ffmpeg or git is added to PATH, Windows updates the registry and notifies the shell via a WM_SETTINGCHANGE broadcast, but only newly launched processes benefit from this refresh. Apps such as IDEs, code agents, and desktop tools that were open before the PATH change continue using their original, stale environment block. The reliable fix is to fully quit the application — including any background helper processes or tray icons — and relaunch it after the PATH update. For machine-wide changes or stubborn apps, logging off and back on ensures a clean session environment, though services and scheduled tasks require a separate restart to pick up the new PATH.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in