Hey guys,

Quick question: do I need to set something special in my MSI (Wise Package Studio) in order to have my environment variables applied to user accounts as well as the installers account?

As it stands now, all the variables are visible with the account that installed the software, but when I log in my test user's account, the variables are no where to be found.

I'll go do some googling while you guys try and give me a hint!

As always, help is always appreciated!

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer


Are you setting System or User variables? If System, you need to restart the machine before they apply, unless you use a function in a custom DLL to tell Windows that there has been an environment update. From what I recall, Windows Installer is *supposed* to send that message (WM_UPDATE[something, is it?) but experience suggests to me that it isn't 100% fallible. This is one reason why I avoid System variables: no-one likes to reboot their user's workstations, do they?

If User, bear in mind that child processes inherit their parent's environment, so testing a session immediately after an install may not necessarily show the change e.g. if you run the installation using MSIExec from an OS prompt, typing 'SET' when the installation completes won't show you the new variable, whereas opening a new OS prompt and typing 'SET' will.
Answered 04/16/2008 by: VBScab
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Thanks VB!

But I found it... I hadn't checked the box which says "Windows NT based system environment variables"

Uninstalled, reinstalled, and bingo, voilà! My variables were visible for my users as well!!!

Thansk again for all the help!
Answered 04/16/2008 by: Fau
Senior Purple Belt

Please log in to comment