starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Open in Terminal" from Explorer doesn't load the system PATH variable #18795

New Issue
Closed
opened 2026-01-31 06:24:31 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:24:31 +00:00
Owner
Copy Link

Originally created by @dalemyers on GitHub (Oct 31, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

This assumes PowerShell as your default shell. Adjust for cmd as needed.

  1. Go to the start menu and find terminal and launch it. (Or use the run dialog).
  2. Run $Env:Path and see that it lists everything in the users PATH as well as the system PATH
  3. Open any folder in Explorer.
  4. Right click and select "Open in Terminal"
  5. Run $Env:Path and see that it lists only the users PATH.

Expected Behavior

Terminal should behave exactly the same no matter how it is opened.

Actual Behavior

Different PATH variables are loaded depending on where you loaded the terminal from. There appears to be no way to tell either, so some software behaves differently.

Originally created by @dalemyers on GitHub (Oct 31, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce This assumes PowerShell as your default shell. Adjust for cmd as needed. 1. Go to the start menu and find terminal and launch it. (Or use the run dialog). 2. Run `$Env:Path` and see that it lists everything in the users PATH as well as the system PATH 3. Open any folder in Explorer. 4. Right click and select "Open in Terminal" 5. Run `$Env:Path` and see that it lists only the users PATH. ### Expected Behavior Terminal should behave exactly the same no matter how it is opened. ### Actual Behavior Different PATH variables are loaded depending on where you loaded the terminal from. There appears to be no way to tell either, so some software behaves differently.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:24:31 +00:00
claunia commented 2026-01-31 06:24:32 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 2, 2022):

This seems to be duplicated with #12808 and #12602 which in turn seems to be duplicates themselves: https://github.com/microsoft/terminal/issues/12602#issuecomment-1060709230

@zadjii-msft You might have a better feeling which issue to best pick as the one to keep track of.

@lhecker commented on GitHub (Nov 2, 2022): This seems to be duplicated with #12808 and #12602 which in turn seems to be duplicates themselves: https://github.com/microsoft/terminal/issues/12602#issuecomment-1060709230 @zadjii-msft You might have a better feeling which issue to best pick as the one to keep track of.
claunia commented 2026-01-31 06:24:32 +00:00
Author
Owner
Copy Link

@dalemyers commented on GitHub (Nov 3, 2022):

It seems that #12808 is the opposite of this one. It loads system but not user. I see user being loaded but not system.

#12602 could be either way round. Note: this happens to me even if no terminal processes are running, so it's not a WM_SETTINGCHANGE thing.

@dalemyers commented on GitHub (Nov 3, 2022): It seems that #12808 is the _opposite_ of this one. It loads system but not user. I see user being loaded but not system. #12602 could be either way round. Note: this happens to me even if no terminal processes are running, so it's not a WM_SETTINGCHANGE thing.
claunia commented 2026-01-31 06:24:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 8, 2022):

Hmm over in https://github.com/microsoft/terminal/issues/13046#issuecomment-1127806813 I linked a bunch more of these.

/dup #12602 looks the closest though

@zadjii-msft commented on GitHub (Nov 8, 2022): Hmm over in https://github.com/microsoft/terminal/issues/13046#issuecomment-1127806813 I linked a bunch more of these. /dup #12602 looks the closest though
claunia commented 2026-01-31 06:24:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 8, 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 (Nov 8, 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18795
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?