How to fix a broken uninstaller? - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

billzitomer
Posts: 4
Joined: Tue Jan 12, 2010 9:32 pm

How to fix a broken uninstaller?

I added a custom action to call a DLL function and I think it is causing my uninstaller to fail because it is returning an error code. The error is: "Fatal error during installation". If I try to install over the existing one with a fixed version, it just says the software is already installed. If I bump the version, it appears to do the update, but it does not replace the broken uninstaller and continues to fail when I try to uninstall it. How can I get around this problem?
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: How to fix a broken uninstaller?

Hello,

Please make sure your custom action has the:

Code: Select all

NOT Installed
execution condition set, so it does not try to execute during uninstall.

If you still can not troubleshoot this issue, please send the .aip project files both for the first installer and the second to support at advancedinstaller dot com so we can further investigate the problem.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
billzitomer
Posts: 4
Joined: Tue Jan 12, 2010 9:32 pm

Re: How to fix a broken uninstaller?

Thanks. I actually need to run the custom command during uninstall. I know how to fix it, and to ignore errors (this was in dev). The thing I am concerned about is that it is possible to install something with a broken command like that, and there is apparently no way to uninstall or repair the application. If this ever happened in production we could end up with millions of broken users and a nightmare scenario.

I guess this is more of a Windows Installer issue, but I thought you folks might know a way handle it, not that we would ever let this happen, but just in case. :)

I was able to fix my development box by using this utility: http://support.microsoft.com/kb/290301.

Return to “Common Problems”