problem after remove package

[sbmrodrigo]

I have a problem that occurs in the following steps

1 - I install my package. OK

2 - I run the package again and in this execution I only have the option to remove the package

3 - after completing the removal, some processes remain open (figure attachment 2). windows installer processes (msiexec.exe) and setup processes (VistoSoftSetup.exe)

4 - after this, if I run it again the installation does not allow it and displays the message that there is already an instance running.

On some administrator machines the problem does not occur, but on others there is some policy in which the problem occurs.

The way I am closing the installer upon removal is this (figure attachment 1)

Is there anything else I can do at this end to get around this problem, which is possibly a policy on some machines?

Attached the .aip project

[Catalin]

Hello Rodrigo,

It's quite strange that the MSI process stays stranded after the uninstall.

Do you launch any app in the background during the uninstall process / is there any app that the installer can not remove during the uninstall that keeps the process in use?

You mentioned that this mostly happens for users with no admin rights, which makes me think that perhaps something is not properly removed and keeps the process in use.

Your approach with killing the process at the end of the installation seems ok, as that would be the only way (besides the user manually killing the process from task manager).

Best regards,
Catalin

[sbmrodrigo]

No, I don't start anything.

the only thing I did outside of the standard scope was remove some screens that I didn't need.

I've noticed that the problem always occurs at the end of the uninstallation. After uninstalling it seems to execute something and the msiexec.exe processes run and don't end.

The .aip project is attached.

[Catalin]

Hello Rodrigo,

Apologies for the quite delayed reply on this!

I did not quite manage to reproduce this myself, but one of my colleagues did.

We suspect that one of the custom actions is at fault here, but for now I can not say for sure.

Please allow us some more time to investigate this and I'll followup here as soon as I have a conclusive answer.

Best regards,
Catalin

[Catalin]

Hello Rodrigo,

I've actually managed to reproduce this myself just now and also found the culprit to this.

Screenshot_227.png (12.03 KiB) Viewed 10116 times

Your terminate process action did not have the "Wait for custom action to finish before proceeding" option checked.

Could you please check the option and let me know if everything is working as expected?

Additionally, please note that you can remove the custom action that tries to kill msiexec, as I do not see any issues caused by that. Did you have any issues in the past with this?

Best regards,
Catalin