Service not deleted when uninstalling (requires reboot) - Advanced Installer Community
vbjeff
Posts: 23
Joined: Tue May 14, 2013 3:08 pm

Service not deleted when uninstalling (requires reboot)

I have been running into a problem while trying to upgrade my software. My application is installed as a service and I also install the updater as a service. I have found that if I install and then uninstall (using Add/Remove Programs) on a Win7 64-bit computer, that both services are stopped and the files are removed, but the reference(s) in the Service Management Console are usually not removed and requires me to reboot my computer to finish removing them. I do have the "On Uninstall" Actions for Stop and Delete checked for both services.

If they remain referenced in the Service Management Console (which has them as marked for deletion), then I can not install a new version without rebooting. I have found that it does work properly once in a while, but frequently will leave one or both services still referenced. Is there anything I can do to make sure the services are properly deleted when uninstalling?
vbjeff
Posts: 23
Joined: Tue May 14, 2013 3:08 pm

Re: Service not deleted when uninstalling (requires reboot)

I think I found the problem. The program "Process Explorer" was running and preventing the services from deleting properly. After I closed Process Explorer the problem went away. I guess I can add a Custom Action to the uninstall to terminate the procexp.exe and procexp64.exe processes so that it does not cause a problem. How would I know if there are any other processes running that may cause a similar issue?
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Service not deleted when uninstalling (requires reboot)

Hello,
Is there anything I can do to make sure the services are properly deleted when uninstalling?
I'm not sure why you encountered this behavior. We also have process explorer on our testing and development machines and the services removal works as expected.
Maybe you have some custom settings for the process explorer and this cause this unexpected behavior.

If you have other questions, please let us know.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”