2

CMD commands:

setx SOMEVARIABLE "newpath" /M
setx SOMEVARIABLE "%SOMEVARIABLE%;newpath2" /M

Expected output on ECHO %SOMEVARIABLE%:

newpath;newpath2

Actual output:

%SOMEVARIABLE%

Actual value stored (From System Properties->Environment Variables GUI):

%SOMEVARIABLE%;newpath2

The only way i can get the expected output is, if i restart the command prompt every time i modify the environment variable. I'm using this command to automate environment variable value appending multiple times during the same process.

  1. Why doesn't environment variable get updated in cmd without restart?
  2. Is it possible to get the updated value of %SOMEVARIABLE% without restarting the command prompt?

1 Answer 1

4

The problem is that setx modifies the global environment, not the local environment. Therefore, you have to restart the command prompt to pick up the change.

You have two options:

  • Use a different tool that modifies the global environment and the local environment
  • Create a batch-file that does both and use that:

    ::setenv.bat
    @echo off
    set %1=%2
    setx %1 %2 %3
    
1
  • 1
    That's not always true. Quite often a reboot is required after setx :( Nov 30, 2016 at 12:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .