we have the following situation:
- Our latest major version was released in May (we call it Update 0)
- A short time later, a new version was released (Update 1), which has fixed some major glitches of U0
- We want now to release the next version (Update 2) as a normal patch update
I realized today, that this setup is violating a lot of MSI patch rules, nevertheless it was published with "install MSI as minor update if applicable" and the same product code as the first version.
We have now created the Update 2 patches (32- and 64-bit), for targeting Update 1 installations only. On the first tests it seems, that these patches are working as expected, at least as long as you try to install the patches manually as administrator. But we have also implemented the AI Updater mechanism, that we would like to use to update non-admin users to the latest version. Here the trouble starts.
Issue A): When installing Update 2 using the resulting .msp files an UAC dialog pops up, and the following error is written to the MSI log file
Code: Select all
MSI (s) (28:20) [15:14:57:290]: Note: 1: 3
MSI (s) (28:20) [15:14:57:290]: SECUREREPAIR: SecureRepair Failed. Error code: 3B6DBE438
MSI (s) (28:20) [15:14:57:307]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (28:20) [15:14:57:307]: User policy value 'DisableRollback' is 0
MSI (s) (28:20) [15:14:57:307]: Machine policy value 'DisableRollback' is 0
Action ended 15:14:57: InstallExecute. Return value 2.I also found somewhere in the microsoft Daniel's posts and somewhere else another guy stated, that the issue might be depending of the author of the package, because it does not seem to be an MS issue.
Issue B) When installing the setup.exe file (same method as with Update 1), the Advanced Updater starts, it takes a while and an UAC dialog is shown.
No log file is written until this point, independently if this was configured in the update.txt file or not.
Issue C) When installing the setup.exe as Major Update (after changing product code) the same behavior happens as with issue B) - the UAC dialog is shown.
Issue D) When installing the setup.exe over an Update 0 installation, everything works fine. No UAC pops up, installation is continued and at the end we have Update 2 installed.
My final conclusion is, without better knowledge we have something destroyed with Update 1. We cannot even update to a new major version now (to fix something general), without entering the Administrator credentials on the UAC dialog (I can already hear our customers yelling at me, yeah
).This might be an side effect of some other issue, but I noticed another problem in the scenarios with setup.exe + UAC dialog: When I compare the installation of setup.exe over Update 0 with the installation over Update 1 + UAC + Admin credentials, then the command line statement was missing in the second case and the UI was starting not silently. I can provide further log files for that too, if required.
Any ideas how to analyze the underlying issue and to solve it?
I will send our project files of U0, U1 and U2 and the patch project to support@....staller.com with the same subject as this post to speed up analysis of this issue.
Thanks for helping,
Roland