title: XP Embedded attempts to start application as service
body: <p>I'm having a lot of problems trying to start an application as administrator on an application I'm writing when running it on XP Embedded.</p>
  
  <p>The application runs as the shell for a limited user account and is touch-screen and keyboard-less with one user command being to run the touch screen vendor's calibration tool. This must be run as administrator.</p>
  
  <p>No problem I thought, add user and password information to the ProcessStartInfo and all should be fine. No. The error I get is:</p>
  
  <pre><code>System.ComponentMode.Win32Exception: The specified service does not exist as an installed service.
  </code></pre>
  
  <p>From some investigation, I've found that:</p>
  
  <ul>
  <li>My Process starting code is correct:
  
  <ul>
  <li>any application can be started successfully on XP Embedded when run as the limited user</li>
  <li>any application can be run as Administrator on my own laptop</li>
  </ul></li>
  <li>on XP Embedded, <em>any</em> application is regarded as being a service in the same way, including <em>notepad</em></li>
  <li>if I attempt to start a program from within process explorer, I simply get <code>"Unable to execute process: Access is Denied"</code></li>
  </ul>
  
  <p>I'm not an XP Embedded expert in anyways so I'd very much appreciate some help. I suspect that there's a configuration setting that has been set when building the XP image that specifically denies access to process creation and that the errors I'm being reported are actually mis-reports from software that's not assuming XP Embedded error codes.</p>
  
  <p>Unfortunately, the people who make the base image aren't around right now so I can't get the current settings.</p>
  
  <p>Thanks in advance if anyone's ever seen this before!</p>
  
  <p>Kev</p>