A bit of important background: my company has a generic login VBS script that makes modifications to the user PATH environment variable upon login and allows me to run software that has dependencies on mapped DFS fileshares. I also recently installed the Windows Powershell SDK to my Windows 7 Enterprise machine and attempted to try out modifying my PATH environment variable from the Powershell command line.
Following this, I noticed that I could no longer run applications that correspond to these login PATH modifications and that the environment variable editor PATH was set to something different than what was showing up when I issued an
'echo %PATH%' from the command prompt.
So for example (simplification), from the environment variable editor (
My Computer properties -> Advanced System Settings -> Environment Variables) I had
whereas when I did
'echo %PATH%' from a command prompt I got:
Has anyone else had a similar issue and was there some sort of resolution? When I googled for help, I came upon this:
It occurred to me that if the login script was initiated by something other than my Explorer.exe environment, then that was the problem. However, when I ran the login script myself, my PATH from command prompt was unchanged. What would this have to do with PowerShell? I'm missing how this is connected to that install completely.