>The only way to have the EXE autostart when Windows starts is to make it a service. Otherwise, it autostarts when the user logs in.

Ok, I see. So, basically, if I have a Windows Service which I need to control its update, I need to have another EXE, which will know when an update is needed, stop the service, update the service and restart the service. This is what I have right now. But, in order to have that automatically, it then means that the Updater need to be a service as well. Presently, the Updater is an EXE for the user, where the user can access as a post EXE setup to configure the service. And, that Updater need to be available to the user as well in production. So, am I correct to say that I might have to move from one service + one GUI EXE to one service + another service for the Updater + the actual GUI?