title: SDK Manager won't start Windows 7 64-bit?
body: <p>I know this problem has been addressed before several times, but rather than comment on an old question I decided to make a new one with (hopefully) updated information.</p>
  
  <p>As the title says, no matter what I do I cannot get the SDK Manager to run.  I have tried installing both the 32- and 64-bit versions of jdk1.7.0 but no luck.</p>
  
  <p>Currently I have both the jdk (32-bit) and the sdk installed in the C:\ directory.  As many have said I changed the environment variable below to reflect the locations.  Namely:</p>
  
  <p>Variable name: PATH<br>
  Variable value: </p>
  
  <blockquote>
    <p><strong>C:\Android\android-sdk\tools;C:\Java\jdk1.7.0\;</strong> C:\Program
    Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files
    (x86)\Common Files\Microsoft Shared\Windows
    Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program
    Files (x86)\Windows Live\Shared;C:\Program
    Files\Intel\WiFi\bin\;C:\Program Files\Common
    Files\Intel\WirelessCommon\</p>
  </blockquote>
  
  <p>(Obviously I only added the first two values)</p>
  
  <p>Somebody out there must have had the same difficulty setting this up who can help me out here.  I had no problem installing everything on my 32-bit Win7 machine, but the 64-bit is my main computer and I really need to have the SDK with me if I am going to learn how to use it.</p>
  
  <p><strong>(EDIT: Solved!)</strong></p>
  
  <p>The problem I was having was that a command prompt window would pop up then the SDK Manager would start to load then instantly crash.  </p>
  
  <p>Strangely, someone else with a very similar computer to mine just installed with no problems whatsoever.  Weird.</p>
  
  <p>I finally added another environment variable:</p>
  
  <p>Variable name: JAVA_HOME</p>
  
  <p>Variable value: C:\Java\jdk1.7.0\</p>
  
  <p>and it worked!  </p>
  
  <p>Thanks for all the help everyone.  I hope this can help someone else who might have the same problem.</p>