starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Path variable from the environment is not respected #22376

New Issue
Closed
opened 2026-01-31 08:11:20 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 08:11:20 +00:00
Owner
Copy Link

Originally created by @0xEDApps on GitHub (Oct 10, 2024).

Windows Terminal version

1.22.240926002-preview

Windows build number

10.0.22621.819

Other Software

No response

Steps to reproduce

run:
cmd.exe
type:
set path=c:\tweet;%path%
type your path to terminal:
"C:\Users\Admino\AppData\Local\Temp\WindowsTerminal\x64\WindowsTerminal.exe"
open a cmd window in terminal and type:
path

WindowsTerminal.exe shows the right path "c:\tweet;...."
OpenConsole.exe also shows the right path "c:\tweet;...."
but then cmd.exe has a different path

Expected Behavior

to see the active environment
to see "c:\tweet"

Actual Behavior

shows the wrong path
probably the environment is retrieved from the registry instead of the environment

Originally created by @0xEDApps on GitHub (Oct 10, 2024). ### Windows Terminal version 1.22.240926002-preview ### Windows build number 10.0.22621.819 ### Other Software _No response_ ### Steps to reproduce run: cmd.exe type: set path=c:\tweet;%path% type your path to terminal: "C:\Users\Admino\AppData\Local\Temp\WindowsTerminal\x64\WindowsTerminal.exe" open a cmd window in terminal and type: path WindowsTerminal.exe shows the right path "c:\tweet;...." OpenConsole.exe also shows the right path "c:\tweet;...." but then cmd.exe has a different path ### Expected Behavior to see the active environment to see "c:\tweet" ### Actual Behavior shows the wrong path probably the environment is retrieved from the registry instead of the environment
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:11:20 +00:00
claunia commented 2026-01-31 08:11:22 +00:00
Author
Owner
Copy Link

@0xEDApps commented on GitHub (Oct 10, 2024):

Checked with ProcessHacker to see the environment of individual executables

WindowsTerminal.exe shows the right path "c:\tweet;...."
OpenConsole.exe also shows the right path "c:\tweet;...."
cmd.exe has a different path

@0xEDApps commented on GitHub (Oct 10, 2024): Checked with ProcessHacker to see the environment of individual executables WindowsTerminal.exe shows the right path "c:\tweet;...." OpenConsole.exe also shows the right path "c:\tweet;...." cmd.exe has a different path
claunia commented 2026-01-31 08:11:22 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 10, 2024):

Windows Terminal treats each tab and pane like a "container" of sorts. Each one gets its own fresh environment variables. You can disable that behavior here:

Image

@lhecker commented on GitHub (Oct 10, 2024): Windows Terminal treats each tab and pane like a "container" of sorts. Each one gets its own fresh environment variables. You can disable that behavior here: ![Image](https://github.com/user-attachments/assets/d192fdce-9f59-4654-8894-a4130a11e0c7)
claunia commented 2026-01-31 08:11:22 +00:00
Author
Owner
Copy Link

@0xEDApps commented on GitHub (Oct 10, 2024):

i see, indeed that works for new tabs but not for the one that is there when launched.

i also use these settings
default profile: Command Prompt
when terminal starts: open tab with default profile

@0xEDApps commented on GitHub (Oct 10, 2024): i see, indeed that works for new tabs but not for the one that is there when launched. i also use these settings default profile: Command Prompt when terminal starts: open tab with default profile
claunia commented 2026-01-31 08:11:22 +00:00
Author
Owner
Copy Link

@0xEDApps commented on GitHub (Oct 10, 2024):

Also it does not show the correct path wen a tab is created with a new instance.

i have this setting
new instance behavior: attach to the most recently used window

@0xEDApps commented on GitHub (Oct 10, 2024): Also it does not show the correct path wen a tab is created with a new instance. i have this setting new instance behavior: attach to the most recently used window
claunia commented 2026-01-31 08:11:23 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 16, 2024):

Thanks for filing! Assuming Windows Terminal is set as your default terminal, start cmd should create a new window and immediately hand off to windows terminal, which would then have the expected environment block. This can be used as a workaround for your scenario. If you do wt new-tab -w0 cmd, that should work too. Does that work for you ?

Note #16226 may be involved here.

@carlos-zamora commented on GitHub (Oct 16, 2024): Thanks for filing! Assuming Windows Terminal is set as your default terminal, `start cmd` should create a new window and immediately hand off to windows terminal, which would then have the expected environment block. This can be used as a workaround for your scenario. If you do `wt new-tab -w0 cmd`, that should work too. Does that work for you \? Note #16226 may be involved here.
claunia commented 2026-01-31 08:11:23 +00:00
Author
Owner
Copy Link

@0xEDApps commented on GitHub (Oct 17, 2024):

Thanks for filing! Assuming Windows Terminal is set as your default terminal

Don't even know how to do that, it most likely can't be automated as MS implemented encryption for default file associations, so no it is not the default

Does that work for you ?

it does, but not my preferred solution

Note #16226 may be involved here.

Good find buddy
Indeed, seems to be a reoccurring issue, you can not expect all users to start hunting for command line parameters, when the default behaviour is that a app inherits the environment from the caller.
I used --inheritEnvironment from there as the cleaner outcome

To bad MS does not respect the environment and reads the registry instead, now many other devellopers also do that, a example WindowsTerminal writes to %LocalAppdata% but uses the one from the registry, i am not gonna mess with that, i attempted it years ago, but that is a global change and all other crappie apps will start to write at the new location too, so sad :(
Maybe that should be a different issue.

@0xEDApps commented on GitHub (Oct 17, 2024): > Thanks for filing! Assuming Windows Terminal is set as your default terminal Don't even know how to do that, it most likely can't be automated as MS implemented encryption for default file associations, so no it is not the default > Does that work for you ? it does, but not my preferred solution > Note [#16226](https://github.com/microsoft/terminal/issues/16226) may be involved here. Good find buddy Indeed, seems to be a reoccurring issue, you can not expect all users to start hunting for command line parameters, when the default behaviour is that a app inherits the environment from the caller. I used `--inheritEnvironment` from there as the cleaner outcome To bad MS does not respect the environment and reads the registry instead, now many other devellopers also do that, a example WindowsTerminal writes to %LocalAppdata% but uses the one from the registry, i am not gonna mess with that, i attempted it years ago, but that is a global change and all other crappie apps will start to write at the new location too, so sad :( Maybe that should be a different issue.
claunia commented 2026-01-31 08:11:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 17, 2024):

i am not gonna mess with that, i attempted it years ago, but that is a global change and all other crappie apps will start to write at the new location too, so sad :(
Maybe that should be a different issue.

You must know that redirecting the known folders like AppData/LocalAppData is not supported. Please don't file bugs on us, or anyone else, for that.

@DHowett commented on GitHub (Oct 17, 2024): > i am not gonna mess with that, i attempted it years ago, but that is a global change and all other crappie apps will start to write at the new location too, so sad :( Maybe that should be a different issue. You must know that redirecting the known folders like AppData/LocalAppData is not supported. Please don't file bugs on us, or anyone else, for that.
claunia commented 2026-01-31 08:11:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 17, 2024):

Thanks for filing! Assuming Windows Terminal is set as your default terminal

Don't even know how to do that, it most likely can't be automated as MS implemented encryption for default file associations, so no it is not the default

Windows Terminal is the default console host on your version of Windows unless you've turned it off explicitly, and it does not work by using "file associations".

@DHowett commented on GitHub (Oct 17, 2024): > > Thanks for filing! Assuming Windows Terminal is set as your default terminal > > Don't even know how to do that, it most likely can't be automated as MS implemented encryption for default file associations, so no it is not the default Windows Terminal _is_ the default console host on your version of Windows unless you've turned it off explicitly, and it does not work by using "file associations".
claunia commented 2026-01-31 08:11:24 +00:00
Author
Owner
Copy Link

@0xEDApps commented on GitHub (Oct 17, 2024):

Windows Terminal is the default console host on your version of Windows unless you've turned it off explicitly, and it does not work by using "file associations".

Doubt that, i am on win 11 and never have i seen "windows terminal" it always shows cmd.exe or consolehost.exe

@0xEDApps commented on GitHub (Oct 17, 2024): > Windows Terminal _is_ the default console host on your version of Windows unless you've turned it off explicitly, and it does not work by using "file associations". Doubt that, i am on win 11 and never have i seen "windows terminal" it always shows cmd.exe or consolehost.exe
claunia commented 2026-01-31 08:11:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 23, 2024):

At its heart, this is a /duplicate of #15496.

You can use the --inheritEnvironment argument or the profile setting compatibility.reloadEnvironmentVariables (set to false).

@DHowett commented on GitHub (Oct 23, 2024): At its heart, this is a /duplicate of #15496. You can use the `--inheritEnvironment` argument or the profile setting `compatibility.reloadEnvironmentVariables` (set to `false`).
claunia commented 2026-01-31 08:11:24 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Oct 23, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 23, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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#22376
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?