Terminal only sets up WSLENV if it exists in Windows in all caps #17986

Closed
opened 2026-01-31 06:00:23 +00:00 by claunia · 1 comment
Owner

Originally created by @ashemedai on GitHub (Jul 21, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

  1. Open a command or PowerShell prompt
  2. setx wslenv whatever
  3. Start Windows Terminal
  4. Open a WSL environment
  5. env | grep WSL

Expected Behavior

WSLENV=WT_SESSION:whatever:WT_PROFILE_ID

Actual Behavior

WSLENV=

Originally created by @ashemedai on GitHub (Jul 21, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce 1. Open a command or PowerShell prompt 2. `setx wslenv whatever` 3. Start Windows Terminal 4. Open a WSL environment 5. `env | grep WSL` ### Expected Behavior `WSLENV=WT_SESSION:whatever:WT_PROFILE_ID` ### Actual Behavior `WSLENV=`
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 06:00:23 +00:00
Author
Owner

@ashemedai commented on GitHub (Jul 21, 2022):

Doing some more digging, this seems to be a WSL issue. Closing this accordingly.

See https://github.com/microsoft/WSL/issues/8639 for the issue in the WSL project.

@ashemedai commented on GitHub (Jul 21, 2022): Doing some more digging, this seems to be a WSL issue. Closing this accordingly. See https://github.com/microsoft/WSL/issues/8639 for the issue in the WSL project.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17986