title: powershell start-process doesn't know about environment variable (PATH) changes
body: <p>I use powershell to set a number of system environment variables, including the path. I then start some task with Start-Process. Unfortunately the new process has the same environment variables as those which powershell was started in. To reproduce the issue</p>
  
  <p>1) Modify your path. I'm deleting <code>%JAVA_HOME%/bin</code>, open a command window and see that the <code>java</code> command does not work.</p>
  
  <p>2) Start Powershell ISE</p>
  
  <p>3) Add <code>%JAVA_HOME%/bin</code> to the system PATH. Open a new command window and see that the <code>java</code> command works.</p>
  
  <p>4) In the previously opened Powershell window, submit the command <code>start cmd</code> to cause powershell to open a <code>cmd.exe</code> command window ("Command Prompt"). In the new command window verify that <code>java</code> does not work.</p>
  
  <p>My expectation would be that a newly launched process would have its own fresh copy of the environment variables. </p>
  
  <p>Can you tell me how to get powershell to launch a new task and have that task know the current environment?</p>
  
  <p>I've tried</p>
  
  <pre><code>start cmd
  
  Start-Process -FilePath "cmd"
  
  Start-Process -FilePath "cmd" -UseNewEnvironment
  
  &amp; cmd
  </code></pre>
  
  <p>Thanks!</p>