Has anyone seen strange behaviour of installing using the .msi
association?  We have been seeing our setups being installed in the
advertise mode when running them from a script file using the .msi
association way of running them.  ie, we use the following commandline
style in a bat file to automatically install our apps:

start/wait %systemdrive%\path\somesetup.msi /qn

Everything runs ok, but when you go to use the app installed by
somesetup.msi, it has been installed as advertise and not actually
installed.

This only happens with the msi setups we have developed.  They are all
made using the Visual Studio Installer.

Any ideas why?  Are there any special setting somewhere that could
cause this?

Thanks in advance!
---JHG