Hello Ana and welcome to our forums,
For Youssef, the problem happened because of shared resources between multiple setups.
If you can notice in the uninstall log file, multiple lines like this:
Code: Select all
Disallowing uninstallation of component: {...} since another client exists
Allowing uninstallation of shared component: {...}. Other clients exist, but installed to a different location
Basically, this means that your files are somehow shared between multiple setups.
Every resource from an installation package has a component assigned. A component is a piece of the application or product to be installed. Examples of components include single files, a group of related files, registry keys, resources, etc.
If you find the above lines in the log file, then this is the reason why your files are not removed. Basically, this can happen if the same components are shared between multiple packages installed on the same machine. Windows Installer keeps a refcount (reference count) for the components and does not allow removing them until all the applications that use them are removed.
Please have a look at the
Why files are left behind after package uninstall article for more information about this.
This may also happen when you are using the same project (or copies) to create different installation packages.
Please keep in mind that when you copy the .aip (project file) and reuse it to build another installer package all the GUIDs for product, components,etc. in the two projects will be identical and thus will conflict if you install it on the same machine. So, if you want to reuse an existing .aip file to build another installation package you should use our
Save As Template... option.
If the software (the setup) is not yet distributed, there is a high chance that this may be particular to your developer machine only.
For testing purposes we always recommend using virtual machines with clean states so that when something goes wrong you can easily revert to a clean state of the virtual machine.
Are you able to reproduce this on a clean machine?
If you cannot resolve this problem, can you please send us by email to
support at advancedinstaller dot com, the following resources:
1. the .AIP (setup project) file.
2. an
uninstallation log.
3. a download link for your setup package.
so we can fully test this scenario.
Best regards,
Liviu