Removing product doesn't remove files/service of installed product - Advanced Installer Community
rversteeg
Posts: 4
Joined: Mon Jun 26, 2017 10:53 am

Removing product doesn't remove files/service of installed product

I have a product with a windows service. To make sure the credentials of the service are not removed I have selected "Install new version first and then uninstall old version" in the upgrade page. But when I uninstall the product my service is not uninstalled, and my files are not removed. What am I doing wrong?
Attachments
VaultServiceAI.aip
AIP project
(39.66 KiB) Downloaded 333 times
vault_uninstall.log
verbose uninstall log
(275.21 KiB) Downloaded 222 times
Sorin
Posts: 663
Joined: Mon May 08, 2017 1:03 pm

Re: Removing product doesn't remove files/service of installed product

Hello,

It seems that some components are shared by different product installations, including the component associated with your service, thus they aren't uninstalled.

Code: Select all

MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {9CB18871-AEF0-44ED-B722-41AB65A492DF} since another client exists
MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {D87A232C-7311-45F0-AAF2-1F35374FCB85} since another client exists
MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {2B15FD93-FC8C-4AF7-BF14-C39CDC24C086} since another client exists
MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {940E775F-0AD9-4EDA-BFB4-3FEFF64ADFA9} since another client exists
MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {B9DC68F6-A9B5-46C2-A2FF-E564DE929EBD} since another client exists
MSI (c) (A0:F0) [12:18:25:304]: Disallowing uninstallation of component: {E0673C8D-8A08-4D85-B233-0349D5133239} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {906118EB-0525-444E-AB96-BB5FB88B9ADE} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {BD70A82F-9EA3-4DDF-8FD1-48AAAA2460F9} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {3989EE03-8953-4E3E-86C7-86283EC7F1E6} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {0AC3A111-1BBC-4B19-9A1C-EA251D6A4396} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {855E0140-2EA3-430F-9D21-C1B3017FC36B} since another client exists
MSI (c) (A0:F0) [12:18:25:305]: Disallowing uninstallation of component: {4CA34764-8F0D-4794-9282-E9D42DFBE8AF} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {4A5B0179-697A-407C-BA85-66D6D73E9525} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {27605B57-C776-49EC-BD99-D93BE059E158} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {6F4AAAC4-B400-426A-8DD8-21028743189A} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {E50AC230-637A-4AC9-8395-9F8AFB8C926F} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {9B97D197-5ED3-4244-BC9E-920D62F1C374} since another client exists
MSI (c) (A0:F0) [12:18:25:306]: Disallowing uninstallation of component: {7CCB0BA5-EC88-4E65-B4C0-2330703863E9} since another client exists
MSI (c) (A0:F0) [12:18:25:307]: Disallowing uninstallation of component: {3BCEC5EE-23C4-426D-B57C-8C146D01B797} since another client exists
MSI (c) (A0:F0) [12:18:25:307]: Disallowing uninstallation of component: {97ED57BB-B304-450F-BE6E-1CB4604FB2B5} since another client exists
This is the intended behaviour. These resources will be uninstalled when all the products containing these components are uninstalled. Please take a look on our article : Why files are left behind after package uninstall?

For testing purposes we always recommend to be used virtual machines with clean states so that when something goes wrong you can easily revert to a clean state of the virtual machine.

Best regards,
Sorin
Sorin Stefan - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rversteeg
Posts: 4
Joined: Mon Jun 26, 2017 10:53 am

Re: Removing product doesn't remove files/service of installed product

@sorin, how can I see what product this is, because I can't see any other installation of the product in my programs. Also I don't allow for side-by-side installation.

Edit: I tried it on another virtual machine, and it does remove the files there. So it is just something on my development PC indeed.
Sorin
Posts: 663
Joined: Mon May 08, 2017 1:03 pm

Re: Removing product doesn't remove files/service of installed product

Hello,
@sorin, how can I see what product this is, because I can't see any other installation of the product in my programs. Also I don't allow for side-by-side installation.
You should open the Registry Editor and go to :

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components
Here you will find a series of registry key named after the packed GUID of the components installed on the machine.

A packed GUID can be obtained by applying a transform to a standard GUID. This transform performs the following operations:

-removes the curly braces and separating dashes from a standard GUID
-writes each group of the first three groups of hexadecimals characters in a standard GUID in reverse order
-switches every two characters in the fourth and fifth group in a standard GUID

Let's consider the following example:
Original GUID:
{12345678-ABCD-WXYZ-1234-ABCDEFGHIJKL}
The packed GUID:
87654321DCBAZYXW2134BADCFEHGJILK

So you need to find the packed GUID of your component, using the above method, then select the corresponding registry key.

In this key there will be a value for each product that shares the component. This registry value name is the Product code in Packed form of the product which shares the component. You could convert the packed product code to the actual Product Code of the product using the method I presented above.
Edit: I tried it on another virtual machine, and it does remove the files there. So it is just something on my development PC indeed.
I'm glad that you have sorted things out.

Best regards,
Sorin
Sorin Stefan - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”