[wix-users] confused about bundle (upgrades/downgrades)

[Steve Ogilvie]

hi all,


so I have a product 17.2.0.6 and installed it. its in Add/remove programs


Then I ran a previous version same product, the bundle ran (nothing else did, i.e. the products MSI) but it "completed" as if it ran normally, and it is now listed in Add/Remove Programs.


So now I have 2 of the same product different version listed in ARP, but different versions...


Bundle 1 has higher version and the MSI installed as expected

Bundle 2 has lower version, bundle upgrade code is same, product GUID is different.


Shouldn't the bundle realize that it is already installed AND a newer version is already installed??


here is the logging from the 2nd installer (bundle 2) which is the lower version:


Detected related bundle: {a GUID}, type: Upgrade, scope: PerMachine, version: 17.2.0.1, operation: Downgrade
Detected related package: {another GUID}, scope: PerMachine, version: 17.2.0.27, language: 0 operation: Downgrade
Detected related package: {same as another GUID}, scope: PerMachine, version: 17.2.0.27, language: 0 operation: Downgrade
Detected package: MainInstall_NoGUI, state: Obsolete, cached: None
Detected package: MainInstall_GUI, state: Obsolete, cached: None

A newer version of this product is installed but downgrade failure has been suppressed; continuing...
Plan begin, 3 packages, action: Install
Planned package: MainInstall_NoGUI, state: Obsolete, default requested: None, ba requested: None, execute: None, rollback: None, cache: No, uncache: No, dependency: None
Planned package: MainInstall_GUI, state: Obsolete, default requested: None, ba requested: None, execute: None, rollback: None, cache: No, uncache: No, dependency: None
Planned related bundle: {same as a GUID}, type: Upgrade, default requested: None, ba requested: None, execute: None, rollback: None, dependency: None
Plan complete, result: 0x0
Apply begin

Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{e8df902d-1572-4ff7-960f-c0cd5f3e8199}, options: 0x7, disable resume: No
Caching bundle from: 'C:\Users\Steve\AppData\Local\Temp\{BA0A6A8E-3B0D-407B-99EE-96EFC03CDAFC}\.be\MyProduct.exe' to: 'C:\ProgramData\Package Cache\{e8df902d-1572-4ff7-960f-c0cd5f3e8199}\MyProduct.exe'
Registering bundle dependency provider: {e8df902d-1572-4ff7-960f-c0cd5f3e8199}, version: 16.5.14.4
Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{e8df902d-1572-4ff7-960f-c0cd5f3e8199}, resume: Active, restart initiated: No, disable resume: No
Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{e8df902d-1572-4ff7-960f-c0cd5f3e8199}, resume: ARP, restart: None, disable resume: No
Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{e8df902d-1572-4ff7-960f-c0cd5f3e8199}, resume: ARP, restart initiated: No, disable resume: No
Apply complete, result: 0x0, restart: None, ba requested restart:  No
Shutting down, exit code: 0x0



Why would the bundle register itself in ARP?


thanks,


Steve