ADB (Android Debug Bridge) is a command-line tool that lets your Windows PC talk to an Android phone or tablet for tasks like installing apps, copying files, and running shell commands. This guide walks you through installing ADB on Windows 10 or 11, either by downloading Google’s official platform-tools or by using a package manager. You’ll end up with a working adb command you can run from any folder.
What You’ll Need
- A Windows PC (Windows 10 or 11 recommended).
- An Android phone or tablet (for actually using ADB, not strictly required for installation).
- USB cable (if you plan to connect a device).
- Internet connection to download the tools.
- Administrator rights on the PC (needed to edit system PATH or install drivers).
Step-by-Step
There are three main ways to install ADB. Choose one that fits your comfort level.
Method 1: Download Official Platform-Tools (Recommended)
- Open your browser and go to the Android developer website:
https://developer.android.com/studio/releases/platform-tools. - Scroll to the “Downloads” section and click the link for Windows to download a ZIP file named something like
platform-tools_r34.0.3-windows.zip. - Once the download finishes, right-click the ZIP file and select Extract All…. Choose a simple location like
C:\platform-tools(avoid spaces and special characters in the path). Click Extract. - Open the extracted folder. You should see files like
adb.exe,fastboot.exe, andAdbWinApi.dll. - To use
adbfrom any command prompt, add this folder to your system PATH:- Press Win + R, type
sysdm.cpl, and press Enter. - Go to the Advanced tab and click Environment Variables….
- Under “User variables” (or “System variables” if you want it for all users), select Path and click Edit….
- Click New and paste the path to your platform-tools folder, e.g.,
C:\platform-tools. - Click OK on all open dialogs to save.
- Press Win + R, type
- Open a new Command Prompt (press Win + R, type
cmd, press Enter) and typeadb version. If you see version information, ADB is installed correctly.
Method 2: Install via Chocolatey (Package Manager)
- If you don’t have Chocolatey, install it first. Open PowerShell as Administrator and run:
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1')) - Close and reopen PowerShell as Administrator.
- Run the command:
choco install adb -y - Chocolatey will download and install the platform-tools automatically, and it will add the tools to your PATH.
- Open a new Command Prompt or PowerShell and run
adb versionto confirm.
Method 3: Use Windows Subsystem for Android (WSA) Tools (for Windows 11)
This method is more complex and generally not recommended for most users. It involves enabling WSA and sideloading the platform-tools. The official platform-tools ZIP is simpler and works on both Windows 10 and 11. Stick with Method 1 or 2.
Common Mistakes
- Forgetting to extract the ZIP – Running
adbfrom inside the ZIP won’t work. Always extract first. - Not updating PATH – If you get “adb is not recognized”, the PATH wasn’t set or the command prompt wasn’t reopened after changing it.
- Using a 32-bit vs 64-bit mismatch – The official platform-tools are 64-bit only for modern Windows. If you’re on an older 32-bit system, you may need an older version (not recommended).
- Antivirus blocking the download – Some antivirus programs flag adb.exe as a potential threat. If so, temporarily disable the real-time scanner or add an exclusion, but only if you downloaded from the official source.
Tips
- Keep the platform-tools folder somewhere permanent, like
C:\platform-tools. Don’t put it in a temp folder that might get cleaned. - To connect a device, enable Developer options and USB debugging on your Android phone (go to Settings → About phone → tap “Build number” 7 times, then enable USB debugging in Developer options).
- Use a good-quality USB cable. Cheap cables often fail to establish a stable ADB connection.
- If you plan to use ADB often, create a desktop shortcut to Command Prompt that opens in the platform-tools folder: right-click the folder, choose “Open in Terminal” (Windows 11) or copy the path and use
cd. - For wireless debugging, you can use
adb pairandadb connecton Android 11 and later, but you still need the platform-tools installed first.
Troubleshooting
“adb is not recognized as an internal or external command”
This means the PATH isn’t set correctly. Check that you added the correct folder path (e.g., C:\platform-tools) and that you opened a new Command Prompt after saving. If you still have issues, you can always run adb by typing the full path, like C:\platform-tools\adb.exe.
“adb server version doesn’t match this client”
This happens when you have multiple ADB installations (e.g., one from Android Studio and one from platform-tools). Uninstall the older one or make sure the correct version is first in your PATH. You can also run adb kill-server and then adb start-server.
“Device unauthorized” when connecting a phone
On your phone, you’ll see a dialog asking to allow USB debugging. Check the box “Always allow from this computer” and tap OK. If you missed it, disconnect and reconnect the USB cable.
“adb: command not found” in PowerShell or CMD
Same as the first issue – PATH problem. Double-check the environment variables. Also, if you used Chocolatey, make sure you installed it as administrator and reopened the terminal.
“error: device offline”
This often indicates a driver issue. Install the proper USB driver for your phone (most modern phones use a generic ADB driver that Windows installs automatically, but some brands require a specific driver). You can also try a different USB port (preferably a USB 2.0 port on the back of the PC).
“adb.exe – System Error: The code execution cannot proceed because VCRUNTIME140.dll was not found”
You need the Microsoft Visual C++ Redistributable. Download and install the latest “vc_redist.x64.exe” from Microsoft’s official site, then restart your PC.
Frequently Asked Questions
Do I need to install a separate driver for ADB?
For most modern Android phones, Windows will automatically install a generic ADB driver when you enable USB debugging and connect the device. If you have an older phone or a niche brand, you may need to install the manufacturer’s USB driver.
Can I use ADB over Wi-Fi?
Yes, since Android 11, you can use wireless debugging. Enable “Wireless debugging” in Developer options, then use adb pair with the pairing code and adb connect with the IP:port shown. For older Android versions, you can use adb tcpip 5555 after a USB connection, but it’s less straightforward.
Is ADB the same as Fastboot?
No. ADB is for when the Android system is running. Fastboot is a separate tool that runs when the device is in bootloader mode. Both are included in the platform-tools package.
Will installing ADB void my phone’s warranty?
Simply installing ADB on your PC doesn’t affect your phone. Using ADB to modify system files or unlock the bootloader might void the warranty, but basic ADB commands like installing apps or taking screenshots are safe.
How do I uninstall ADB?
If you used the ZIP method, just delete the platform-tools folder and remove the PATH entry. If you used Chocolatey, run choco uninstall adb -y.
Can I use ADB on Windows 7?
The latest platform-tools may not support Windows 7. You can try an older version (e.g., r28) but it’s not recommended for security reasons. Consider upgrading to Windows 10 or 11.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Windows Not Saving Remote Desktop Credentials
- Fix Error 0x8007025d in Windows 10
- Fix Alexa App Stuck on Setup
- Android Camera for 7 Office Tasks: Step-by-Step
- Pair Phone to Pioneer Stereo After Bluetooth Reset
- Essential Tips for macOS Users Switching to Windows