Environmental variables are not reloaded on new console

[gsbabil]

Cmder version: 1.1.3
Windows version: 8.1 (64bit)

To reproduce:

• Run Cmder (it creates the first console). Add a user environmental variable (e.g. TEST=1234)
• Create a new console inside the same Cmder session and run echo %TEST%. It will print %TEST% meaning the variable doesn't exist
• Restart the whole Cmder session (kill and start over). Now run echo %TEST%. It will print 1234 meaning that the %TEST% variable exists for the session this time.

[samvasko]

I am not sure if you used setx or set so I will check both:

With set after I restart the cmder. I don't get 1234 echoed. I am pretty sure variables set by set name=value are tied to lifetime of cmd session.

If you are using setx than the environmental vars first need to be reloaded on the second console to work. If you want this kind of functionality you should try some for this.

[gsbabil]

I didn't use either of set or setx. I added my variable using Windows' built-in tool. In Windows 8.1, it is in Control Panel > System and Security > System > Advanced System Settings > Environmental Variables. Alternatively, one can just search for Environmental Variables in Windows' search to reach there.

[sc0tt]

This is from ConEmu, I'd suggest taking the issue up on that issue tracker.

[samvasko]

But has been a default since forever. Env variables get loaded on start of cmd.exe

[gsbabil]

@Bliker You are right. I was guessing that Cmder might create multiple cmd.exe session as new consoles are created. If not, the ConEmu initialization script that runs at the beginning of every new console session might add something that reloads all the environmental variables.

[Chigogo]

@samvasko I use setx both in CMD and Cmder, I get that whether I start a new console in current session or I restart Cmder session, the result is the same that Cmder wont refreash user-level's variable.

[joeflack4]

Restarting Windows10 fixed for me.