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

Profile with custom environment for PATH causes WSL to lose standard PATH values #23455

New Issue
Closed
opened 2026-01-31 08:42:45 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:42:45 +00:00
Owner
Copy Link

Originally created by @reduckted on GitHub (Jul 20, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.19045.0

Other Software

WSL: 2.5.9.0
Ubuntu: 22.04.3 LTS

Steps to reproduce

Install WSL and a distro (I'm using Ubuntu, but it doesn't seem to matter which one you use).

Use the standard profile for cmd, as well as a custom profile that prepends to the PATH envrionment variable:

{
    "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
    "name": "cmd"
},
{
    "guid": "{324dd25d-8c2a-4ffb-a877-92b93f2bb404}",
    "name": "cmd with custom PATH",
    "commandline": "cmd.exe",
    "environment": {
        "PATH": "C:\\Code;%PATH%"
    }
}

Note

This also occurs when using pwsh, but it's easier to demonstrate using cmd because you don't need to escape the $ symbol.

Open Windows Terminal and use the standard cmd profile. Run wsl echo $PATH. The output will be something like this:

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Windows/System32:/mnt/c/Windows:<...snip...>

Use the custom "cmd with custom PATH" profile. Run wsl echo $PATH. The output will be something like this:

/usr/lib/wsl/lib:/mnt/c/Code:/mnt/c/Windows/System32:/mnt/c/Windows:<...snip...>

Expected Behavior

The value of $PATH in WSL when using the "cmd with custom PATH" profile includes the standard /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games values.

Actual Behavior

The standard PATH values are missing.

Originally created by @reduckted on GitHub (Jul 20, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.19045.0 ### Other Software WSL: 2.5.9.0 Ubuntu: 22.04.3 LTS ### Steps to reproduce Install WSL and a distro (I'm using Ubuntu, but it doesn't seem to matter which one you use). Use the standard profile for `cmd`, as well as a custom profile that prepends to the `PATH` envrionment variable: ```json { "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "cmd" }, { "guid": "{324dd25d-8c2a-4ffb-a877-92b93f2bb404}", "name": "cmd with custom PATH", "commandline": "cmd.exe", "environment": { "PATH": "C:\\Code;%PATH%" } } ``` > [!NOTE] > This also occurs when using `pwsh`, but it's easier to demonstrate using `cmd` because you don't need to escape the `$` symbol. Open Windows Terminal and use the standard `cmd` profile. Run `wsl echo $PATH`. The output will be something like this: ``` /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Windows/System32:/mnt/c/Windows:<...snip...> ``` Use the custom "cmd with custom PATH" profile. Run `wsl echo $PATH`. The output will be something like this: ``` /usr/lib/wsl/lib:/mnt/c/Code:/mnt/c/Windows/System32:/mnt/c/Windows:<...snip...> ``` ### Expected Behavior The value of `$PATH` in WSL when using the "cmd with custom PATH" profile includes the standard `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games` values. ### Actual Behavior The standard PATH values are missing.
claunia commented 2026-01-31 08:42:48 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 30, 2025):

Ah, we should probably not add PATH to WSLENV. It looks like that upsets WSL.

... I'm somewhat surprised that WSL doesn't handle that more gracefully.

Anyway, we should be able to fix it locally.

@DHowett commented on GitHub (Jul 30, 2025): Ah, we should probably not add `PATH` to `WSLENV`. It looks like that upsets WSL. ... I'm somewhat surprised that WSL doesn't handle that more gracefully. Anyway, we should be able to fix it locally.
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 Area-TerminalConnection Issue-Bug Needs-Tag-Fix Priority-2 Product-Terminal
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#23455
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?