'Adb' is not an internal or external command, or a program or batch file that can be run.

'Adb' is not an internal or external command, or a program or batch file that can be run.
In Android development, we cannot do without using ADB to operate on some things. However, when we use ADB in the command line, 'adb' is sometimes not an internal or external command, it is not a running program or batch processing file. This prompt means that we need to do some processing.
The error occurs because the adb.exe file cannot be found. In the original Android sdkfile, adb.exe is located in the Tools Folder under the SDK directory, because we only need to add the SDK \ tools to the path of the system environment variable, however, later Android sdkmoved adb.exe to platform-tools. In tools, a prompt "adb_has_moved.txt" appears, whose content is
The ADB tool has moved to platform-tools/

If you don't see this directory in your SDK,
Launch the SDK and AVD Manager (execute the android tool)
And install "android SDK platform-Tools"

Please also update your path environment variable
Include the platform-tools/directory, so you can
Execute ADB from any location.

Therefore, there are two solutions here. One is to switch to platform-tools in the command line and specify ADB. Of course, this method is very troublesome because you need to switch every time. The second method is to place platform_tools in the environment variable path, so that you can use ADB anywhere.
Last modified: 2011-10-23