ADB not starting on windows 10

[lands39]

using windows 10 and an S10e, i can't get scrcpy to work, it says the adb server failed to start. i tried seeing if anything's on the same port (there isn't), tried letting it through the firewall, tried running as admin, nothing. tried scrcpy on linux and my phone connects just fine. can i get some help?

[lands39]

verbose adb output, i also tried disabling the windows firewall which made no difference

[lands39]

set ANDROID_ADB_SERVER_PORT=6000 makes the adb server start on port 6000, but it sees no devices and scrcpy fails to connect to anything

[lands39]

what is smartsocket?

[lands39]

tried another windows pc as a troubleshooting step and adb starts, what's wrong with adb on the main pc?

[lands39]

trtied adb from android developer tools sdk, its still not working.

[lands39]

tried the 32 bit version of scrcpy, same problem

[lands39]

tried scrcpy 2.0, same issue. now i'm getting pissed. why is windows so allergic to adb? it literally just works on linux, and it inexplicably works on my other windows 10 box

[lands39]

okay, after checking netstat it seems easytether is bound to that port. unfortunately, easytether is how i get my internet. how can i change the port? i tried #1696 and adb is able to start, but it detects no devices.

[Unarmored7]

I encountered the same difficulty

[rom1v]

@Unarmored7 Because you set the ADB environment variable (to a wrong value). Just unset it.

[Unarmored7]

@Unarmored7 Because you set the ADB environment variable (to a wrong value). Just unset it.

thanks for your reply. But i think i set the correct environment variable
My adb.exe is indeed in the platform-tools folder of the changed path
If this is an incorrect setting, how should it be set?

[rom1v]

adb is included in the scrcpy release, so you don't need to point to another one.

If you really want to use another adb, the path must be the path to the executable (including its filename), not just its directory.

[Unarmored7]

adb is included in the scrcpy release, so you don't need to point to another one.

If you really want to use another adb, the path must be the path to the executable (including its filename), not just its directory.

Thank you very much for your help, the problem was solved perfectly!!!