PRB: Custom Path Ignored When Feature is Advertised

ID: Q193368

The information in this article applies to:

SYMPTOMS

If you select a custom installation path for a feature, it is not honored if the feature is set to Advertised. The custom path selected for the feature is only used if the feature is installed at that time. When you install an advertised feature that has a custom path selected as the destination directory, the feature will be installed in its default location.

Note also that setting the INSTALLLOCATION property on the command line while advertising will behave in exactly the same manner: 


   msiexec /i Test.msi "INSTALLLOCATION=c:\test ADVERTISE=ALL"


NOTE: If the parent feature is installed to a custom path, all advertised children will also be installed to that custom path when they are installed.


CAUSE

Currently there is no mechanism for remembering directories tied to a feature if no component tied to that feature is installed.


RESOLUTION

If you need a custom installation path for a feature, install the feature instead of advertising the feature. This ensures that the feature is installed to the correct location.


STATUS

This behavior is by design.


MORE INFORMATION

Steps to Reproduce Behavior

  1. Run an .msi file.


  2. On the SelectionDialog, browse through a parent feature.


  3. Change the target directory so that it points to a custom location.


  4. Set the InstallState of that parent feature to Advertised.


RESULT: The custom path is no longer visible and the browse option is disabled.

Additional query words: 


Keywords          : kbsetup 
Version           : WINDOWS:1.0
Platform          : WINDOWS 
Issue type        : kbprb

Last Reviewed: May 3, 1999