0

I have a WiX Burn bundle that includes five MSI packages. During an installation - when upgrading a bundle - I see this:

Burn UI

This happens after progressing the MSI packages. I am not sure what happens. Can this be shown as a text string?

Morten Frederiksen
  • 5,114
  • 1
  • 40
  • 72

2 Answers2

1

After installing new version of the package Burn runs cached previous version of bundle with command uninstall and Display property set to embedded. Bundle has an unique ID which cannot be set in .wxs file but assigned in compile time. To fix this in my bootstrapper I filter progress messages and replace GUIDs with user friendly text.

AndreiSh
  • 141
  • 1
  • 2
  • This is exactly what happens. How did you achieve this? Did you implment your own CBalBaseBootstrapperApplication? – Morten Frederiksen Sep 13 '13 at 13:09
  • We've tried creating native bootstrapper inherited from IBootstrapperApplication and now use managed bootstrapper. It seems that Wix team is more concentrated on managed than native version of bootstrapper and it works significantly better. – AndreiSh Sep 16 '13 at 13:34
  • I would detect the GUID via DetectRelatedBundle event (RelationType == Upgrade). – leshy84 Feb 03 '16 at 13:12
  • Did anybody manage to replace the GUID of previous installation by friendly name using standard bootstrapper? – Agustin Berbegall Jan 30 '21 at 02:50
0

In my case, that strange GUID was actually a zombie MSI package that was left behind during one of my previous installation/uninstallation tests (because it was failing during the uninstall operation). Somehow the Burn engine was detecting that package as related to the actual installation, and it was trying to install/uninstall it.

If that's your case, you should see that zombie package in the Burn generated logs, and you will be able to remove it from your MSI database using the Microsoft Fixit tool.

Dani Carbonell
  • 477
  • 5
  • 10