title: Reading environmental variables in PowerShell or cmd yield different results
body: <p>I have been puzzling over an issue with environmental variables in Windows&nbsp;7.</p>
  
  <p>We have a Jenkins server which cannot find the SSH keys in the <code>%HOME%</code> environmental variable as it wants to access the path:</p>
  
  <pre><code>/c/users/jenkins
  </code></pre>
  
  <p>However if I use</p>
  
  <pre><code>echo %HOME%
  </code></pre>
  
  <p>in a normal command prompt window as my Jenkins user then the result is </p>
  
  <pre><code>C:\users\jenkins
  </code></pre>
  
  <p>However, if I use the environment command in Windows PowerShell I also get</p>
  
  <pre><code>/c/user/jenkins
  </code></pre>
  
  <p>In the normal GUI accessible from the system properties - advanced tag -> environmental I get the following</p>
  
  <pre><code>C:\users\jenkins
  </code></pre>
  
  <p>I have tried setting them back, but the issue persists. In so far as Jenkins gets the same output as PowerShell.</p>
  
  <p>How do I set them back? (Not that cmd and the Windows system think that they are set wrong.)
  How on earth does accessing the same environmental variable give me different outputs?
  Is there a way in which this can occur?
  Where are they stored so I can manually edit where they are stored?</p>