Windows 10: Different $Env:Path on Powershell

Discus and support Different $Env:Path on Powershell in Windows 10 Gaming to solve the problem; Depending on how I start Powershell the $Env:Path variable is different. Opening from Start is different from the File Explorer context menu Terminal... Discussion in 'Windows 10 Gaming' started by theking2, Sep 11, 2022.

  1. THEKING2
    theking2 Win User

    Different $Env:Path on Powershell


    Depending on how I start Powershell the $EnvDifferent $Env:Path on Powershell :path variable is different. Opening from Start is different from the File Explorer context menu Terminal here.Is this by design?vs

    :)
     
    theking2, Sep 11, 2022
    #1
  2. DALCHINA
    dalchina Win User
    dalchina, Sep 11, 2022
    #2
  3. KURSAH
    Kursah Win User
    PowerShell instead of Commandline in Creators Update

    Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

    Edit: Not that it matters...I use both regularly. *Toast :toast:
     
    Kursah, Sep 11, 2022
    #3
  4. FEUER
    Feuer Win User

    Different $Env:Path on Powershell

    Feuer, Sep 11, 2022
    #4
Thema:

Different $Env:Path on Powershell

Loading...

  1. Different $Env:Path on Powershell - Similar Threads - Different $Env Path

  2. Adding a path doesn't make any difference to finding powershell scripts

    in Windows 10 Gaming
    Adding a path doesn't make any difference to finding powershell scripts: I've created a Powershell script folder in a certain place, and I'm trying to make it part of my PSModulePath. I've added this to $PROFILE file and also tried this on the command-line but none of the scripts in this folder get seen, unless I explicitly put the full pathname...

  3. Adding a path doesn't make any difference to finding powershell scripts

    in Windows 10 Software and Apps
    Adding a path doesn't make any difference to finding powershell scripts: I've created a Powershell script folder in a certain place, and I'm trying to make it part of my PSModulePath. I've added this to $PROFILE file and also tried this on the command-line but none of the scripts in this folder get seen, unless I explicitly put the full pathname...

  4. Adding a path doesn't make any difference to finding powershell scripts

    in Windows 10 Network and Sharing
    Adding a path doesn't make any difference to finding powershell scripts: I've created a Powershell script folder in a certain place, and I'm trying to make it part of my PSModulePath. I've added this to $PROFILE file and also tried this on the command-line but none of the scripts in this folder get seen, unless I explicitly put the full pathname...

  5. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 Gaming
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...

  6. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 BSOD Crashes and Debugging
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...

  7. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 Software and Apps
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...

  8. Different $Env:Path on Powershell

    in Windows 10 Software and Apps
    Different $Env:Path on Powershell: Depending on how I start Powershell the $Env:Path variable is different. Opening from Start is different from the File Explorer context menu Terminal here.Is this by design?vs...

  9. Path Lengths on Different Drives

    in Windows 10 Network and Sharing
    Path Lengths on Different Drives: I have files on a desktop drive and it does not have an issue with the Path Lengths. On another drive in the same machine if I copy the data it gives me the Path Too Long error if I copy it to that drive. I have already used Regedit to turn on allowing long path names....

  10. Different kinds of Powershell?

    in Windows 10 Support
    Different kinds of Powershell?: I've recently used Powershell, but there appear to be several different versions of this utility. Some of them work--some of them merely report not being able to find something or call up something else. For instance, when I call up Powershell from an elevated command prompt,...