title: Are there any issues with a windows service kicking off an installer to update itself?
body: <p>I have a windows service (C#, with ability to <a href="https://stackoverflow.com/a/1450051/567493">install itself</a>). I also have an installer package the can update the windows service. This updater is currently run manually. The (NSIS) installer/updater runs <code>net stop myService</code> to stop the service, then does the install/update and then <code>net start myService</code>. </p>
  
  <p>My goal is to have the service update itself in some way. This <a href="https://stackoverflow.com/q/1608228/567493">excellent question</a>, and its highest rated answer lists all the possible ways one could probably approach the problem. </p>
  
  <p>It seems to me the simplest, best option is to have the service <code>Proces.Start()</code> the installer. The only minor caveat, is that the installer needs to know how to stop the service for the duration of the upgrade - which my installer already has.</p>
  
  <p>I've heard rumors that this is problematic, but in my <a href="https://github.com/davidpricedev/SampleSelfUpdatingWindowsService" rel="nofollow noreferrer">testing</a>, things seem to be working well. What, if any, are the known issues that will cause problems with this?</p>