SDK Manager.exe doesn't work

Question

When I clicked SDK Manager on Program Files or run it in cmd, nothing happened. I did:

1. Installed latest JDK
2. Installed latest Android SDK<

Answer 1

I have Wondows 7 64 bit (MacBook Pro), installed both Java JDK x86 and x64 with JAVA_HOME pointing at x32 during installation of Android SDK, later after installation JAVA_HOME pointing at x64.

My problem was that Android SDK manager didn't launch, cmd window just flashes for a second and that's it. Like many others looked around and tried many suggestions with no juice!

My solution was in adding bin the JAVA_HOME path:

C:\Program Files\Java\jdk1.7.0_09\bin

instead of what I entered for the start:

C:\Program Files\Java\jdk1.7.0_09

Hope this helps others.... good luck!

Answer 2

I had the same issue!

I had installed the ADT bundle 64-bit, so I downloaded Java 64-bit. I messed around with paths and things, but the thing that fixed it in the end was installing Java 32-bit.

The easy fix is to install both versions. You can download them manually here.

Good luck!

Answer 3

When I clicked SDK Manager on Program Files or run it in cmd, nothing happened

One of your problems is Long File Names in Windows. A number of the Android tools cannot handle them. I filed a bug report on them years ago, but I can't find it at the moment. I also seem to recall something about it in the INSTALL or README.

So you should install the tools in a location without spaces. Use something like C:\Android\ or C:\Android-SDK\.

@Steve and @MeatPopsicle already mentioned spaces in the pathames, but it can't be overstated.

---

Actually a black cmd window appears and disappears a milliseconds.
... Even I set path for ANDROID_SWT

Out of curiosity, where did ANDROID_SWT come from?

I know Android does use ANDROID_HOME, ANDROID_SDK_ROOT and ANDROID_NDK_ROOT, and the last two should both be set because the tools use them internally. Here's the reference on ANDROID_SDK_ROOT and ANDROID_NDK_ROOT: Recommended NDK Directory?.

So you should set the three environmental variables (after ensuring the installation directory does not contain spaces):

• ANDROID_HOME
• ANDROID_SDK_ROOT
• ANDROID_NDK_ROOT

ANDROID_HOME is set to the directory where the hidden directory .android is.

ANDROID_SDK_ROOT is set to the directory where the SDK is installed, like C:\Android-SDK\.

ANDROID_NDK_ROOT is set to the directory where the NDK is installed, like C:\Android-NDK\. If its not installed, then don't set it.

---

Once you have ANDROID_SDK_ROOT set, you can put %ANDROID_SDK_ROOT%\tools and %ANDROID_SDK_ROOT%\platform-tools on PATH. Then, you can drop into a command line and issue something like this (and it just works):

adb list

Answer 4

I fixed this issue by reinstalling it in Program Files, it originally tried to install it in c:/Users/.../AppData/Android/....

Mine was caused by a user permission issue that running as admin didn't seem to fix (perhaps because they call batch files?).

Answer 5

Similar to sixty9 I renamed java.exe, javaw.exe, javaws.exe (I never delete files when troubleshooting) after I created a JAVA_HOME environment variable and added path variables.

I had installed the Java SDK on my D:\ drive ( instead of the default).

1. Create a JAVA_HOME variable: Variable Name: %JAVA_HOME% Value: D:\Program Files\Java.

2. Added the following to the Path variable:

   %JAVA_HOME%\jre7\bin;%JAVA_HOME%\jdk1.7.0_03\bin;
   

3. Renamed java.exe, javaw.exe and javaws.exe.

4. Restarted the system and the Android SDK installer found my JDK and installed successfully.

Answer 6

My issue was the following error on windows 7:

C:\dev\Android\android-sdk-windows\tools>android
[INFO] Starting Android SDK and AVD Manager
No command line parameters provided, launching UI.
See 'android --help' for operations from the command line.
Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-win32-3550 or
swt-win32 in swt.library.path, java.library.path or the jar file
        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.C.<clinit>(Unknown Source)
        at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)
        at com.android.sdkmanager.Main.showMainWindow(Main.java:292)
        at com.android.sdkmanager.Main.doAction(Main.java:276)
        at com.android.sdkmanager.Main.run(Main.java:99)
    at com.android.sdkmanager.Main.main(Main.java:88)

The solution was to disable McAfee 8.8. Apparently some recent update is now blocking my Android environment.