1

In my Installscript project I need a reboot to register the values of Environment variables. But I want that application should setup without a reboot. So is their any way to refresh the values of Environment variable so that my application gets registered and no reboot is required? I am already using following code line :

define WM_WININICHANGE 0x001A'
define HWND_BROADCAST 0xffff'
szEnv = "Environment";
pEnv = &szEnv;
SendMessage( HWND_BROADCAST, WM_WININICHANGE, 0, pEnv );`

Is their is any other way to refresh the Environment variable values? I am running this on Windows xp.

Awais Qarni
  • 17,492
  • 24
  • 75
  • 137
nvivekgoyal
  • 484
  • 9
  • 15
  • 1
    If you're using **InstallShield 2010 or later** - the above code will not work. See here for the solution: http://stackoverflow.com/questions/2103790/batch-file-cant-immediately-see-environment-variables-created-by-installshield/20362751#20362751 – Derek W Dec 03 '13 at 22:15

2 Answers2

0

A Windows process which sets an environment variable cannot access that variable for reading. This is a limitation in Windows. The idea is that if your process sets a variable, it already knows the variable value.

So if your installer is setting an environment variable, your application must run in a separate and unrelated process to read that variable. This is why launching the application when the installation finishes doesn't work.

A solution is to pass the variable value through your application command line when launching it during install. Any future launches will still access the variable directly.

Cosmin
  • 21,216
  • 5
  • 45
  • 60
0

Sending the WININICHANGE message to the broadcast address is the correct thing to do. However there is no requirement that all running processes correctly subclass that message and update their environment variables for that process. They are supposed to, but it doesn't always happen. The most notorious example of this is the Service Control Manager. You have to reboot for the SCM to see the new variable/value.

Now if you are asking "how do I get my current running process to see this value?" ( Cosmin seems to think that's what you are asking but I'm not sure if you are or not ) then the answer lies in understanding that the environment space has four collections:

User Machine Process Volatile

http://msdn.microsoft.com/en-us/library/6s7w15a0(v=vs.85).aspx

What your code does is set the environment var for SYSTEM. This is like the old days when you would put a line in your autoexec.bat ( SET FOO=BAR ) and reboot. But you could also create a new dos prompt from windows and do SET SOMETHING=ELSE and it would only be seen for the life of that process and child processes but no other processes. This is the "Process" space vs the "System" space. Also if you updated AUTEXEC.BAT with a new variable and created a new process without rebooting it wouldn't see the new variable but you could always set it yourself and see it ( although not technically the same one ).

I know, with SendMessage you shouldn't need the reboot but regardless not all processes will get the message.

So, if you need the current InstallScript process to also have this new variable, you'll want to call Kernel32's SetEnvironmentVariable function which according to MSDN "Sets the contents of the specified environment variable for the current process."

Interesting InstallScript has a GetEnvVar function but not a SetEnvVar function so you'll have to prototype this as an external function and then call it.

A discussion with samples can be found here.

Christopher Painter
  • 54,556
  • 6
  • 63
  • 100