We have a situation where a patch from MS has somehow killed our uninstall process - we're not sure which one, however updating to the latest AI version did not solve the issue, and traces of the process with Process Monitor shows the Main Uninstall UI thread ends up in hung state trying to start a subprocess MSI.
We did find that if we kill the main UI thread, the rest of the uninstall process completes without error. All the steps are therefore valid - but something is now preventing execution in the sequence we intended.
After some trial and error, we've found that reordering some custom actions involving COM, DCOM and COM+ (this is a very old app) allows the uninstall process to occur properly. My personal belief is that the old code was actually in error, and this is not an AI issue... correcting the order of the custom actions was long overdue.
However, the big question now is how to correct for this.
Is there a way to update the main MSI code associated with an installed package without actually updating the installed payload? Ideally, this would be something that could be done on a live system without requiring a reboot.
FOLLOW US
Get the latest news in Application Packaging