Don't require restart of Terminal on updating environment variables #13346

Closed
opened 2026-01-31 03:40:17 +00:00 by claunia · 3 comments
Owner

Originally created by @parthopdas on GitHub (Apr 7, 2021).

Windows Terminal version (or Windows build number)

1.6.10571.0

Other Software

No response

Steps to reproduce

  • Open a bunch of tabs in terminal + customize them by splitting pane
  • Install anything that updates system environment variables
  • Launch a new tab

PS: In my case I had to install Cuda stuff that updates environment variables required by tensorflow gpu libs

Expected Behavior

The new tabs / panes should have the update environment variables

Actual Behavior

I have to kill all existing tabs and restart terminal

Originally created by @parthopdas on GitHub (Apr 7, 2021). ### Windows Terminal version (or Windows build number) 1.6.10571.0 ### Other Software _No response_ ### Steps to reproduce - Open a bunch of tabs in terminal + customize them by splitting pane - Install anything that updates system environment variables - Launch a new tab PS: In my case I had to install Cuda stuff that updates environment variables required by tensorflow gpu libs ### Expected Behavior The new tabs / panes should have the update environment variables ### Actual Behavior I have to kill all existing tabs and restart terminal
claunia added the Resolution-Duplicate label 2026-01-31 03:40:17 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Apr 7, 2021):

Reloading the environment variables is part of https://github.com/microsoft/terminal/issues/1125. It was already implemented but has been repeatedly reverted from stable branches (e.g. https://github.com/microsoft/terminal/commit/ba534aaad693d942ec6da4380005a09f6520d0c5 for release-1.6) because the existing implementation makes an environment block that is not compatible with Windows PowerShell https://github.com/microsoft/terminal/issues/7418.

@KalleOlaviNiemitalo commented on GitHub (Apr 7, 2021): Reloading the environment variables is part of <https://github.com/microsoft/terminal/issues/1125>. It was already implemented but has been repeatedly reverted from stable branches (e.g. <https://github.com/microsoft/terminal/commit/ba534aaad693d942ec6da4380005a09f6520d0c5> for release-1.6) because the existing implementation makes an environment block that is not compatible with Windows PowerShell <https://github.com/microsoft/terminal/issues/7418>.
Author
Owner

@zadjii-msft commented on GitHub (Apr 7, 2021):

Yep, sure is!

/dup #1125

@zadjii-msft commented on GitHub (Apr 7, 2021): Yep, sure is! /dup #1125
Author
Owner

@ghost commented on GitHub (Apr 7, 2021):

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 (Apr 7, 2021): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13346