Hello,

RefreshEnv.cmd has been a godsend! Thank you!

This works well in a currently open command window.

However, I've learned that the WM_SETTINGCHANGE signal needs to be broadcasted to the system for the Path change to take effect for all command windows .

Anecdotally, I've found I've had to close all command windows and reopen a new one for the Path change to take effect. (Because... Windows).

Recommending that you broadcast WM_SETTINGCHANGE when you set the PATH. As an idea, keeping the broadcast message in a different script might help with reusability and maintain separation-of-duties.