Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6636533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T23:11:52+00:00 2026-05-25T23:11:52+00:00

While extending a WIX-installer that I have to maintain, I ran into the following

  • 0

While extending a WIX-installer that I have to maintain, I ran into the following problem – when shown the tree of features and components, the product feature is not selected by default.

I tried different variations, including adding InstallDefault ='local', TypicalDefault ='install', and Absent = 'disallow', however, the feature is still disabled.

Here is the code that describes the feature:

<Feature    Id="Complete" Level="1"
  Display='expand'
  InstallDefault ='local'
  TypicalDefault ='install'
  Absent = 'disallow'
  Title="$(var.ProductName)">
  <ComponentGroupRef Id="Required_files"/>
  <?ifdef InstallDriver?>
    <ComponentGroupRef Id='driver_files'/>
  <?endif?>
  <ComponentRef Id="ProgramMenuShortcuts"/>
  <ComponentRef Id="ProductInfo"/>
  <?ifdef RemoveAllRegKeys?>
    <ComponentRef Id="RegRemoveAll"/>
  <?endif?>
  <ComponentGroupRef Id="FBmodule"/>
</Feature>

Having examined the logs, I see some entries that seem to be related to this (this is happening when I manually set the feature to “install to local hard disk”).

MSI (c) (FC:90) [16:43:57:559]: PROPERTY CHANGE: Adding MsiSelectionTreeSelectedFeature property. Its value is 'Complete'.
MSI (c) (FC:90) [16:43:57:559]: PROPERTY CHANGE: Adding MsiSelectionTreeSelectedAction property. Its value is '2'.
MSI (c) (FC:90) [16:43:57:559]: PROPERTY CHANGE: Adding MsiSelectionTreeSelectedCost property. Its value is '0'.
Action 16:43:57: FeaturesDlg. Dialog created
MSI (c) (FC:90) [16:51:44:645]: Note: 1: 2727 2:  
 .... many repetitions of Note: 1: 2727 2:  
MSI (c) (FC:90) [16:51:45:146]: Note: 1: 2727 2:  
MSI (c) (FC:90) [16:51:45:630]: Note: 1: 2205 2:  3: MsiAssembly 
MSI (c) (FC:90) [16:51:45:630]: Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,  `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE  `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? 
MSI (c) (FC:90) [16:51:45:630]: Note: 1: 2205 2:  3: _RemoveFilePath 
MSI (c) (FC:90) [16:51:45:639]: Note: 1: 2727 2:  
MSI (c) (FC:90) [16:51:45:647]: PROPERTY CHANGE: Modifying MsiSelectionTreeSelectedAction property. Its current value is '2'. Its new value: '3'.
MSI (c) (FC:90) [16:51:45:647]: PROPERTY CHANGE: Modifying MsiSelectionTreeSelectedCost property. Its current value is '0'. Its new value: '7318'.

I suspect that this could be related to the fact that there is a custom dialog in the installer – but having looked through the source I could not find anything that would indicate a relationship between the state of the feature and something else in the project.

What are the recommended troubleshooting steps?

Here is the full installation log.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T23:11:53+00:00Added an answer on May 25, 2026 at 11:11 pm

    I found the culprit. The installer itself is fine, the problem is in how it is started.

    There is a BAT file that I use for testing purposes, it runs the MSI with some command line arguments that simulate different conditions.

    The command line arguments REINSTALL=ALL REINSTALLMODE=vomus must only be applied when the installer updates the program; when started that way on a clean system – the progress bar moves and everything goes as expected, but nothing is actually installed.

    In other words, the error was in the method of testing.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

While going through university and from following the development of SO, I've heard a
While cross-site scripting is generally regarded as negative, I've run into several situations where
I have a new web app that is packaged as a WAR as part
While the C# spec does include a pre-processor and basic directives (#define, #if, etc),
While I've seen rare cases where private inheritance was needed, I've never encountered a
While setting up CruiseControl, I added a buildpublisher block to the publisher tasks: <buildpublisher>
While working in a Java app, I recently needed to assemble a comma-delimited list
While in the final throws of upgrading MS-SQL Server 2005 Express Edition to MS-SQL
While Ctrl X works fine in vim under windows, Ctrl A selects all (duh).
While I grew up using MSWindows, I transitioned to my much-loved Mac years ago.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.