Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Windows - no powershell reboot #2

Open
cmather opened this issue Aug 31, 2021 · 1 comment
Open

Question: Windows - no powershell reboot #2

cmather opened this issue Aug 31, 2021 · 1 comment

Comments

@cmather
Copy link

cmather commented Aug 31, 2021

In windows, I can see the WM_SETTINGCHANGE means the env variables are picked up by new processes without requiring a system reboot. But, have you found a way to get the currently running process (e.g. powershell, vscode) to pick up the changes?

It seems that you have to restart the program to get it to see the change. Is there some way to call out to the "set" program perhaps?

@coolaj86
Copy link
Contributor

coolaj86 commented Oct 12, 2022

Child processes cannot change the environment of parent processes.

That's a security feature that's the same across Mac, Linux, and Windows.

I don't know what the PowerShell equivalent of source is, but it may have something like that for a process to update itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants