title: Why is npm prefix always set to system32 on Windows 10?
body: <p>I've just installed Node v4.4.7 on Windows 10 but I am having an issue where <code>npm</code> doesn't find the package.json file when I run <code>npm install</code> in the proper directory.</p>
  
  <p>The error I get is <code>ENOENT: no such file or directory, open 'C:\Windows\System32\package.json'</code>
  Which seems odd as I am not currently in <code>C:\Windows\System32</code> but rather <code>pwd</code> would reveal that I am in <code>C:\ao\AO Hybrid</code></p>
  
  <p>This let me to check <code>npm prefix</code> which returned <code>C:\Windows\System32</code>.
  I've tried this with both npm v.2.15.8 and v.3.10.8 with the same results.</p>
  
  <p>How can I make sure npm searches for the packages locally instead of in system32?</p>