Error in Burn does not reach custom bootstrapper application

[wixbot]

Steps to reproduce:

1. Install a per machine bundle
2. Rename or remove the pseudo bundle located in a directory such as:
3. C:\ProgramData\Package Cache{some guid}
   Start a newer version that would trigger a major upgrade.

In the log, you will find something similar to:

[6308:35C4][2015-12-03T12:44:59]e000: Error 0x80070002: Failed to get size of pseudo bundle: C:\ProgramData\Package Cache{myguid}\myBundle.exe
[6308:35C4][2015-12-03T12:44:59]e000: Error 0x80070002: Failed to initialize package from related bundle id: {myguid}

Version:
Burn v3.10.0.2103

Afaik, there is no way to detect this error in the custom BA. No exception reaches it, event argument value to check etc. The installation just continues as normal, except that OnDetectRelatedBundle is never triggered. One can argue that deleting files under Package Cache is a bad idea. So is deleting files installed by the msi, but there we have repair. We have seen several customers with problems caused by these files being deleted.

It is possible to workaround the problem by copying the correct version of the old (complete) bundle to the path given in the log.

In summary: The problem is not that this occurs but that there is no way (afaik) for the custom bootstrapper application to detect the problem and act on it.

Originally opened by lillegard

[wixbot]

Release changed from v3.10 to v4.0

[wixbot]

Needs discussion about how to handle it; maybe send an HRESULT in OnDetectRelatedBundle or a new message.