Opening a new tab does not update $env:Path #18286

Closed
opened 2026-01-31 06:09:23 +00:00 by claunia · 3 comments
Owner

Originally created by @serialhex on GitHub (Aug 23, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  1. Open Windows terminal
  2. Change your $env:Path in Windows, OUTSIDE of that tab (Example: install Rust for the first time; or Rt click My Computer -> Properties -> Advanced System Settings -> Environment Variables -> Add a new entry to Path)
  3. Open a New tab
  4. Check the output of $env:Path from both tabs. Neither tab has the updated $env:Path.

Expected Behavior

The new tab should have the updated $env:Path just as if you opened a new PowerShell / cmd window. I just tested with a new Terminal window, and a fresh Terminal instance has the updated $env:Path.

Actual Behavior

It seems that new terminal tabs keep the same $env:Path for each Terminal window.

Originally created by @serialhex on GitHub (Aug 23, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce 1. Open Windows terminal 2. Change your $env:Path in Windows, *OUTSIDE* of that tab (Example: install Rust for the first time; or Rt click My Computer -> Properties -> Advanced System Settings -> Environment Variables -> Add a new entry to Path) 3. Open a *New* tab 4. Check the output of `$env:Path` from both tabs. Neither tab has the updated `$env:Path`. ### Expected Behavior The new tab should have the updated `$env:Path` just as if you opened a new PowerShell / cmd window. I just tested with a new Terminal window, and a fresh Terminal instance has the updated `$env:Path`. ### Actual Behavior It seems that new terminal tabs keep the same `$env:Path` for each Terminal window.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:09:23 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Aug 23, 2022):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1125 for more discussion.

/dup #1125

@zadjii-msft commented on GitHub (Aug 23, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1125 for more discussion. /dup #1125
Author
Owner

@ghost commented on GitHub (Aug 23, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Aug 23, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@serialhex commented on GitHub (Aug 23, 2022):

Awesome, thank you @zadjii-msft! I did try and search for an open issue, but I guess my GitHub searching skills aren't up to snuff. Hopefully this will help other people who search for something similar find the proper issue.

@serialhex commented on GitHub (Aug 23, 2022): Awesome, thank you @zadjii-msft! I did try and search for an open issue, but I guess my GitHub searching skills aren't up to snuff. Hopefully this will help other people who search for something similar find the proper issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18286