Well, I appreciate you taking the time to look at this, Friedrich. However, there's very little chance that this is happening because there is corruption on the PC I used to take those screen captures. I've tried this in my PC lab on several Windows 7 and Windows 8.1 machines -- same results. However, I also wrote another little script where the Edit Environment Variable command is the ONLY command in the script, and it seemed to work just fine in changing the PATH environment variable. So, that probably means there is something inside the other script that is causing the Edit Environment Variable command to do something other than what it was intended to do. I know it seems unlikely, but I can think of no other explanation. I've watched it in debug mode and the Edit Environment Variable command just will not add to the existing value of the PATH variable, so it creates another one although I'm at a loss as to why Windows even would allow that.