we are running the setup.exe with administrator user logged in,  we are not seeing this issue in clean machine as a well, Could you please confirm are you able to see the issue if you login with admin user ... View more

Hi roman2, Thanks, I tried your solution and various tweaks of it and still cannot get it work. I am able to log the main msi, where I get: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1' and then: Skipping action: ScheduleReboot (condition is false) I am trying to log the prerequisite in the setup.exe using this advice in the help file: Setup.exe and Update.exe Command-Line Parameters  but the setup.exe does not recognize the /debuglog switch and fails to run the setup. When it does run, it is acting as if the prerequisite is running from the setup.exe in a windows installer instance that ends and then the main msi runs in a it's own instance and there is no communication between the two instances. In any case it is definitely not acting as described in the Behavior page documentation says it should. ... View more

I installed the sp6 update to a test machine and it copies .cab files for each control to a folder, I imagine for redistribution. Is there some way to reconcile these .cab files with the merge modules? ... View more

Right, the Upgrade Code setting in the General Information > General view should change only UpgradeCode in the Property table. For the Upgrades view, it depends on the setting "Products sharing my Upgrade Code" vs. "Products having another Upgrade Code". If you choose the first one, the Upgrade table of your project stores special value "{00000000-0000-0000-0000-000000000000}", which is replaced with the value in the Property table in the built MSI database when you build the project. For the other setting, the Upgrade table should store whatever you enter. ... View more