Unable to create Debug Bridge: Unable to start adb server: Unable to obtain result of 'adb version'

Question

I am running Android Studio on Windows 10 64 bit. I upgraded to the latest build and SDK the morning of 5/20, and since then I get the above error when opening Android Studi

Answer 1

I probably should have done this as part of my initial troubleshooting, but I ended up disabling Windows Firewall and my anti-virus (Trend Micro). The firewall did nothing, but disabling Trend Micro completely solved the issue....

Somehow, for some reason, Trend Micro decided to start not liking the daemon being created by ADB. 4 days of tears and frustration over such a small thing. Hopefully this helps someone else one day avoid it.

Answer 2

The solution is very simple. Open 'Command Prompt' as 'Administrator', run adb kill-server, then adb start-server. It worked for me.

Answer 3

From the information you've provided, I'm not sure that what I'm about to type applies to your situation. But since no one else has answered, you might want to consider it.

I had a very strange situation in which I kept getting the 'Nothing to show' message even though I had defined multiple emulated types of Android equipment, and also had a physical Android device.

I tried all sorts of things to solve the problem without success. Then I eventually tracked down an adb.log file that had been created in a directory outside any of the usual directory trees managed by the Android tools; a directory that is usually used for temporary storage. The access permissions on the file had somehow been changed so that one of the programs involved in debugging, could no longer access the file, and so failed to start properly. Removing the file solved the problem. The next time I attempted to begin debugging, everything worked as it should.

Although I was working with Linux, if the Android tools work in a similar manner with Microsoft Windows, the file might be in a directory tree identified by an environment variable, either TMP or TEMP.

Answer 4

Just update your platform tools from the SDK manager and restart your editor

Answer 5

Geez, I can't it's the TrendMicro antivirus !! ... many Thanks !

This also works for me on my 64bit Win 10, took me a day to reinstall AS and ADK and trying to figure out why ... adb kill-server, then try disable/enable Antivirus and you'll see the difference.

For finer-grain of control, add the bin\studio64.exe of AS into the Exception List of Trendmicro Antivirus and it'll bring up adb just fine.

Answer 6

I got this fix by following this link: https://stackoverflow.com/a/38447003/5521389

going into GenyMotion settings -> ADB tab, instead of Use Genymotion Android tools (default), I chose Use custom Android SDK Tools and then browsed to my installed SDK.