ADB Driver: How to Install It on Windows and Fix Detection

What an ADB driver is and when Windows needs one

Android Debug Bridge (ADB) is the command-line tool a computer uses to talk to an Android device. On Windows, the computer also needs a USB driver that recognizes the phone's debugging interface. Without it, Windows may still show the phone for file transfer while adb devices stays empty. Android Developers says macOS and Linux do not need this driver.

Google devices, such as Pixel phones: use the Google USB Driver, which Android Developers says is required for ADB debugging on Windows with Google devices.
Every other brand: the phone's manufacturer provides the driver. The Android Developers page on OEM USB drivers links to driver sites for makers such as Samsung, Motorola, Lenovo and Xiaomi. If yours is not listed, search the manufacturer's support site for its USB driver.
Check first: Windows sometimes already has a suitable driver, for example one delivered through Windows Update. If adb devices already lists your phone, you do not need to install anything.

The driver is only one of three pieces. You also need the ADB program on the computer and a phone with USB debugging turned on. A driver does not replace either one.

First, enable Developer options on Android and turn on USB debugging

A driver cannot help until the phone offers a debugging connection. Android hides that switch until you enable Developer options: open Settings, find Build number (on Pixel phones it is under About phone) and tap it seven times, as the Android Developers guide to developer options describes. Then turn on USB debugging inside Developer options.

Menu names vary by brand and Android version. Our guide on how to enable USB debugging on Android covers the steps for common phones, USB modes and wireless debugging, so this page focuses on the computer side.

Get ADB itself: download SDK Platform-Tools

Google publishes ADB in SDK Platform-Tools, a free download for Windows, macOS and Linux. You do not need Android Studio. If you already use it, its SDK Manager keeps a copy up to date in the platform-tools folder of your Android SDK.

Download the Platform-Tools ZIP for your system from the Android Developers page and accept the license terms.
Extract it to a short path you will remember, such as C:\platform-tools.
Open Command Prompt in that folder: in File Explorer, type cmd in the address bar and press Enter.
Run adb version. If it prints a version number, ADB is ready. In PowerShell, type .\adb instead of adb unless the folder is on your PATH.

How to install the ADB driver on Windows with Device Manager

Download the right driver first: the Google USB Driver ZIP from Android Developers (or Tools › SDK Manager › SDK Tools › Google USB Driver in Android Studio), or your manufacturer's package. Extract any ZIP. Some manufacturers ship an installer program instead; run it, reconnect the phone and skip to the next section.

Connect the phone with a USB cable that carries data, unlock it and make sure USB debugging is on.
Right-click the Start button and select Device Manager.
Find the phone under Other devices or Portable Devices, or look for an entry with a yellow warning icon.
Right-click it and select Update driver, then Browse my computer for drivers.
Select Browse…, choose the folder you extracted (for the Google driver installed through Android Studio, android_sdk\extras\google\usb_driver\) and select Next.
Let Windows finish. If it reports that the best drivers are already installed, the current driver is the same or newer. Unplug the phone, plug it back in and continue.

Microsoft documents the same Device Manager steps for Windows 10 and 11. Once the driver works, the debugging interface usually shows up with a name like Android Composite ADB Interface, though the exact label depends on the driver.

Check the connection with adb devices and approve the computer

With the phone connected and unlocked, run adb devices.
On the phone, a prompt asks whether to allow USB debugging and shows the computer's RSA key fingerprint. Tap Allow.
Run adb devices again. A working connection lists a serial number followed by device.

According to Android Developers, that prompt appears on Android 4.2.2 and newer, and ADB commands cannot run until you unlock the phone and accept it. Only tick Always allow from this computer on a computer you own.

What the status column means:

device: connected and ready.
unauthorized: the driver works, but the phone has not approved this computer yet.
offline: the device is not connected to ADB or is not responding.
An empty list: ADB sees nothing. On Windows, that usually points to the cable, USB debugging or the driver.

ADB not detecting your device? Fixes that start with the driver

Change one thing at a time and run adb devices after each step, so you know which change fixed it.

Device Manager shows an unknown device or a warning icon. The driver is missing or wrong. Repeat the Device Manager steps with the driver for your brand.
The phone appears only as a media or file-transfer device. Windows has a file-transfer driver but does not see the debugging interface. Check that USB debugging is still on, then switch the USB mode to File transfer, or back again.
Nothing changes when you plug in. Try another data cable and a USB port on the computer itself instead of a hub or dock.
The status is unauthorized and no prompt appears. In Developer options, tap Revoke USB debugging authorizations (the label varies), turn USB debugging off and on, reconnect and accept the new prompt.
The status is offline. Reconnect the cable, restart the phone and update Platform-Tools.
ADB stops responding. Run adb kill-server, then adb devices to start a fresh server. Close other programs that bundle their own copy of ADB: every copy uses the same local port (5037), so an older one can get in the way.
It worked before and stopped. Check Device Manager again. If the phone now shows a warning icon, reinstall its driver.

ADB on macOS and Linux: no driver, different setup

On macOS, Android Developers says no additional configuration is required: install Platform-Tools, connect the phone and run ./adb devices from the folder.

On Ubuntu Linux there is no driver to install either, but the hardware device guide asks for two things:

Your user must be in the plugdev group. Add yourself with sudo usermod -aG plugdev $LOGNAME, then log out and back in.
udev rules must cover the device. The android-sdk-platform-tools-common package installs a community-maintained default set: sudo apt-get install android-sdk-platform-tools-common.

Other distributions package these rules differently, so check your distribution's documentation if you are not on Ubuntu.

Keep the ADB driver and USB debugging safe

Download drivers only from Google, Windows Update or your phone's manufacturer. Skip the all-in-one driver packs offered on download sites.
Get ADB from the official Platform-Tools page and keep it current.
Turn USB debugging off when you finish, and approve only computers you own.
Revoke USB debugging authorizations before you sell the phone or send it for repair, and when you stop using a computer.
Never accept the debugging prompt on a public charger, a kiosk or a shared computer.

Where ASL ADB Assist fits

The driver lives on the computer; ASL ADB Assist helps with the phone side. It is a free Android app that shows your model, Android version and whether Developer options, USB debugging and its keep-awake override are on. It opens Developer options directly, walks you through the Build number taps and can keep the screen on for up to 30 minutes while you connect.

It needs Android 8 or newer, requests no permissions, not even internet access, and works in English and Spanish. It cannot install or fix a Windows driver, authorize ADB or change protected settings: Android still asks you to approve the computer yourself.

Frequently asked questions

Do I need an ADB driver on a Mac or on Linux?

No. Android Developers says only Windows needs a USB driver for ADB. macOS needs no extra setup. On Ubuntu, add your user to the plugdev group and install the udev rules package described above.

Which driver does a Samsung phone need?

Samsung, like most manufacturers, provides its own Windows USB driver, linked from the Android Developers page on OEM USB drivers. The Google USB Driver is meant for Google devices.

Why is ADB not detecting my device after I installed the driver?

Check, in order: the phone is unlocked, USB debugging is on, the cable carries data and Device Manager shows no warning icon. Then run adb kill-server and adb devices. If the status says unauthorized, accept the prompt on the phone.

Is the Google USB Driver the same thing as ADB?

No. The driver lets Windows recognize the phone's debugging interface; ADB is the program in Platform-Tools that sends commands. On Windows you usually need both.

How do I enable Developer options on Android?

Open Settings, find Build number (often under About phone) and tap it seven times, entering your PIN if asked. Developer options then appears in Settings, often under System. Turn on USB debugging there.

Is it safe to install an ADB driver?

Yes, when it comes from Google, Windows Update or the phone's manufacturer. The bigger risk is leaving USB debugging on and approving computers you do not control.

Related guides

Explore the complete product

Read features, current access and limitations

ADB Driver for Windows: How to Install It and Get ADB to See Your Phone