Ug, a reboot just to update the PATH environment? Can you not use the
ServiceInstall elements and schedule the Environment actions before the
Service actions (if they aren't already) so that your services start up with
the system environment updated? This may work because the Windows Installer
is supposed to do all the magic to cause the system environment to get
updated right away.
I have a Wix installation that was working "as designed", however I
decided to make it a bit better. The core product being installed uses
several Windows services that are installed by a configuration utility
that is run via a custom action at install time. There are several
satellite DLLs included with the product that are required by the
service executables and thus I have to modify the default system Path to
include the search path for the DLLs. I add the paths to the "Path"
environment variable by using the following line in a wxs file:
Since the Service Control Manager (SCM) is unaware of the Path change,
the system needs to be rebooted before the Path change will take effect.
Normally I make the user manually reboot the system, however I decided
to be nice and add a reboot with the following line:
<ScheduleReboot After="PublishProduct" />
Unfortunately, the addition of the reboot seems to make the environment
modification not work during silent installs (/qn)!
Has anyone else seen a similar issue and possibly resolved it???