adb cannot start daemon, CreateProcess failure, error 2
adb, android
Solution
I solved this problem long ago, but did not update this question.
I was having this issue because I was running the incorrect adb executable. I had one executable in `C:\Windows\system32` and another in a different directory. The version in `C:\Windows\system32` had did not have all the files needed by adb whereas the version in the other directory did. I'm not sure what those files were, but the adb executable was the same version in both directories. Since `C:Windows\system32` was in the PATH first, that version was executed first. I removed adb from the Windows directory, and the problem went away.
Problem
I an unable to run `adb root` or any adb command. I get the following error. I set `ADB_TRACE=1`: ``` C:\WINDOWS\system32>adb root system/core/adb/adb.c::main():Handling commandline() system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:version system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client: could not connect to tcp:5037 system/core/adb/adb_client.c::adb_connect():adb_connect: service root: * daemon not running. starting it now on port 5037 * CreateProcess failure, error 2 * failed to start daemon * error: cannot connect to daemon ``` I am using Windows 7. From `netstat -a` I don't see anything else using port 5037. When I run adb, I observe that adb momentarily is displayed on Task Manager, but then it goes away. Windows Firewall is turned off. I get the same results if I run `cmd` as administrator.