The environment variables of "Open in Windows Terminal" and "Manually Start Windows Terminal" are inconsistent.

[TigerBeanst]

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

First, add D:\DHYProjects\Las2Osgt\osg; to Path in environment variable.

1. Right click in Explorer, then click "Open in Windows Terminal"（Chinese: 在 Windows 终端中打开）

Mark as WT1:

and Manually Start Windows Terminal, mark as WT2:

2. Check Path environment variable:

Expected Behavior

Their values should be exactly the same.

Actual Behavior

I can't find D:\DHYProjects\Las2Osgt\osg in WT1, which is started by right-click in explorer.

I have trid to kill explorer.exe and restart it in Task Manager. It doesn't work.

It looks like I'll have to reboot my computer to get it work.

[wkl007]

I have the same issue

[zadjii-msft]

• Is the Terminal already running when you open a new tab via the Explorer context menu? (If so, this is probably a riff on Feature Request: Terminal should listen for the WM_SETTINGCHANGE for environment variable updates #1125).
• If this is a "cold launch" (there aren't any other running Terminal windows), then this is something else. Windows terminal path is different if launched with wt.exe #11777 looks a bit related, so does Open alias "wt" have unexpected behavior. #12545

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[TigerBeanst]

• Is the Terminal already running when you open a new tab via the Explorer context menu? (If so, this is probably a riff on Feature Request: Terminal should listen for the WM_SETTINGCHANGE for environment variable updates #1125).
• If this is a "cold launch" (there aren't any other running Terminal windows), then this is something else. Windows terminal path is different if launched with wt.exe #11777 looks a bit related, so does Open alias "wt" have unexpected behavior. #12545

Is the Terminal already running when you open a new tab via the Explorer context menu?
No. I closed all Terminal windows and try it.

A screenrecord:
https://drive.google.com/file/d/1CKwLFEboC46t7Na4dYGSk8XcpTQJFLib/view?usp=sharing

[MrDach]

Any updates on this? It's slightly annoying having to open Terminal via the start menu and having to navigate to the folder every time.

[madmax91]

This is what worked for me to fix this issue:
Go to Settings > Apps > Apps & Features > Terminal and click on Terminate, this will kill all the Terminal processes and related processes and will refresh the cached variables I suppose. After this even if I launch the Terminal from context menu it has the correct variables loaded.

It looks like that windows allows this app and its processes to run in the background even after you close the window. So if you closed the window and changed some Environment variables if any of these processes are left running in the background it will not refresh them fully. It is still strange as why it is refreshing the variables for the instance launched via start menu but not for the instance that is launched via context menu.

[bestK]

If you use autohotkey, see #8862 (comment)

[TheComputerM]

Having the same problem with pnpm. Opening the terminal from the start menu works properly but opening the terminal from the right click context menu will not have PNPM_HOME environment variable set correctly.

[zadjii-msft]

This almost certainly was resolved by #14999.

Yep, I just checked this on a fresh off main build of the Terminal, and this looks fixed to me. This'll be fixed in 1.18, which should be coming out sometime Q2-ish. That's about as accurate as I can be with a release date. Thanks all!