title: Alternative to "Allow service to interact with desktop"?
body: <p>I have a windows service (C#) installed on a server that launches every 10 minutes an executable file (C#) to process some images from one directory to another. No interaction is required with any user. Nevertheless, since the executable file as an output window, to make the service run I have to enable the "<strong>Allow service to interact with desktop</strong>" checkbox <strong>which is considered as an <a href="http://asprosys.blogspot.com/2009/03/allow-service-to-interact-with-desktop.html" rel="noreferrer">insecure and bad practice</a></strong>. How would I go about this problem? I like to have the executable separated from my windows service because</p>
  
  <ul>
  <li>it makes it easier to debug and
  doesn't require a full windows service redeploy.</li>
  <li>sometimes I use the same windows
  service to launch several
  executable files at different
  intervals (but all related to the same
  project).</li>
  </ul>
  
  <p><strong>EDIT:</strong></p>
  
  <p>When the interaction with the desktop is not enabled, the console application does not get executed correctly and the following error appears inside the Windows Logs:</p>
  
  <pre><code>Faulting application myapp.exe, version 1.0.0.0, time stamp 0x4b8304c3, 
  faulting module KERNEL32.dll, version 6.0.6002.18005, time stamp 0x49e03821, 
  exception code 0xc0000142, fault offset 0x00009eed, process id 0x10ec, 
  application start time 0x01cab736950a64b5.
  </code></pre>
  
  <p>Once the desktop interaction is enabled, application gets executed normally.</p>
  
  <p>Any thoughts? </p>
  
  <p>Thanks a lot for your time.</p>