Installation of a Basic MSI setup in Non-User Interface mode(Reduced UI, Basic UI, No UI - means a silent installation that displays no UI) fails without adding ADDLOCAL to command line
Summary
Discussion regarding Windows Installer property ADDLOCAL and how this property is expected to behave at runtime.Synopsis
ADDLOCAL stores a list of features, separated by commas, that are to be installed locally. Each feature has a Remote Installation property that determines whether features selected for installation are to be installed locally or run from the source medium.Discussion
The SetupType dialog sets the ADDLOCAL property to ALL. When ADDLOCAL is equal to ALL the features are first set to run-local and then all features are set to run-from-source.There are different ways to establish ADDLOCAL. The nature of the SetupType dialog using a Basic MSI project sets the ADDLOCAL Property is set to ALL and all the features are installed based on the default behavior of the Next button control.
To work around or change the default behavior of the SetupType dialog take the SetupType dialog out of the dialog sequence. You can create your own dialog or set the property on the command line at runtime.
Do not enter ADDLOCAL=ALL into the Property Table. Doing so is expected to generate a locally installed package that cannot be correctly removed.
The ADDLOCAL property has an impact on InstallLevel also. When ADDLOCAL=ALL features are installed regardless of what InstallLevel dictates.
Related KB Articles
Reference Microsoft article ADDLOCAL propertyWas this helpful?
© 2026 Flexera. All rights reserved.