Running ADB on Windows lets you communicate directly with Android devices from your computer. This guide walks you through installing the Android platform tools, enabling USB debugging, and executing common ADB commands on Windows.
With ADB set up correctly, you can automate tasks, troubleshoot device issues, and run powerful shell commands. The following sections cover installation, drivers, common commands, and troubleshooting specific to Windows.
| Step | Action | Expected Result | Notes |
|---|---|---|---|
| 1 | Download platform-tools ZIP from Google | Compressed folder on your PC | No installer required |
| 2 | Extract to a simple path like C:\adb | adb.exe and adb-server.exe present | Avoid spaces in folder names |
| 3 | Enable Developer Options and USB Debugging on device | Device appears in ADB devices list | Revoke USB debugging authorizations if needed |
| 4 | Install USB drivers or use ADB interface | Device shows as 'device' not 'unauthorized' | Google USB Driver or OEM drivers |
| 5 | Add adb to PATH or use full path | Commands run from any command prompt | test with adb version |
Setting Up ADB on Windows
To run adb on Windows, first download the official platform-tools from the Android developer site. Save the ZIP to a location you can easily access, such as your user folder.
Extract the contents to a clean folder without spaces, for example C:\adb. Keeping the path simple prevents many common command-not-found errors when you open Command Prompt or PowerShell.
After extraction, verify the files are present by opening the folder and confirming that adb.exe and adb-server.exe exist. You can also test by opening a command prompt inside that folder and running adb version.
Installing USB Drivers on Windows
Windows often needs proper USB drivers so your phone can be recognized by adb. You can use the Google USB Driver included in Android Studio or download OEM-specific drivers from your device manufacturer.
To use Google USB Driver, install Android Studio, then open the SDK Manager and ensure Google USB Driver is selected. You can then manually install the driver by updating the device driver in Device Manager and pointing to the driver folder inside the Android SDK.
For many modern devices, enabling USB debugging on the phone and connecting via USB is enough for ADB over TCP/IP, but having the correct drivers ensures reliable wired connections and fast sideload operations.
Authorizing ADB Debugging on Device
After connecting the phone with USB, you must enable USB debugging in Developer Options. On your device, go to Settings > About phone and tap Build number seven times to unlock Developer Options.
Return to Settings, open Developer Options, and toggle USB debugging to on. When you connect the device to your Windows PC, a dialog will appear asking you to allow USB debugging. Confirm the prompt and optionally check "Always allow from this computer."
If the device shows as unauthorized or offline in adb devices, revoke USB debugging authorizations in Developer Options and reconnect the USB cable to restart the authorization flow.
Basic ADB Commands on Windows
Once your device appears in adb devices, you can run common commands to interact with the Android system. Use adb shell to open a remote shell session and adb push or adb pull to transfer files.
For app management, commands like adb install, adb uninstall, and adb shell pm list packages help you debug and manage applications. Logcat is especially useful for viewing system and app logs in real time.
To avoid path issues, either navigate to the folder containing adb.exe before running commands or add the ADB folder to your system PATH environment variable so you can run adb from any terminal.
Advanced ADB Usage on Windows
For network-based debugging, you can connect to devices over TCP/IP using adb connect with the device IP address and port. This is helpful for wireless debugging or when working with multiple devices on the same network.
You can forward ports with adb forward, run screen record commands, and capture bug reports for submission. Combining ADB with scripts on Windows PowerShell or batch files enables automated testing and repetitive task execution without manual intervention.
Final Checklist for Running ADB on Windows
- Download and extract platform-tools to a simple path like C:\adb
- Add the ADB folder to your system PATH or use full paths for commands
- Enable Developer Options and USB Debugging on the Android device
- Install appropriate USB drivers via Google USB Driver or OEM sources
- Authorize USB debugging on the device when prompted
- Verify device detection with adb devices before running further commands
- Use common ADB commands for installation, log capture, and file transfer
- Explore advanced options like TCP/IP connections and port forwarding
FAQ
Reader questions
How do I fix 'adb command not found' on Windows?
Ensure the folder containing adb.exe is added to your system PATH, or open Command Prompt inside the ADB folder and run commands from there. Restarting the terminal after changing PATH settings is required.
Why does adb devices show unauthorized or offline?
This usually means USB debugging authorization was not accepted or the RSA key expired. Revoke USB debugging authorizations on the device, reconnect the USB cable, and confirm permission on the phone to resolve this.
Can I use ADB over Wi-Fi instead of USB on Windows?
Yes, enable USB debugging temporarily, connect the device and your PC to the same network, then use adb connect IP_ADDRESS:PORT to establish a wireless connection without a USB cable.
What should I do if Windows does not recognize my Android device at all?
Install the correct OEM or Google USB driver, check Device Manager for driver errors, enable USB debugging, and try different USB ports or cables to establish a reliable connection.