Powershell doesn't inherit new PATH after applying it outside

[murder]

Windows Terminal version

1.14.1963.0

Windows build number

10.0.22000.0

Other Software

PowerShell 7.2.5
PowerShell 7.3.0-preview.6

Steps to reproduce

1. Open Windows Terminal
2. Open a new Powershell session in Windows Terminal
3. Change the 'User variables' or 'System variables' Path environment variable by going through %WINDIR%\system32\SystemPropertiesAdvanced.exe 'Environment Variables...' option or even straight to regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path key
4. Apply it
5. Bring up a new Powershell tab in Terminal, whichever Powershell version you wish
6. Path is the same - the new path is not re-read

Expected Behavior

I expected that NEW tabs would of course re-read NEW configurations, especially regarding environment variables

In order to make it work, you have to kill the entire Terminal process (and all tabs that you are working on), reload Terminal, and then you will notice that the new environment variable was inherited.

Actual Behavior

Nothing.

In order to make it work, you have to kill the entire Terminal process (and all tabs that you are working on), reload Terminal, and then you will notice that the new environment variable was inherited.

[zadjii-msft]

/dup #1125

[ghost]

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!