An ADB driver for Windows 11 is the USB driver that lets the adb tool on your PC talk to an Android phone with USB debugging turned on. For Pixel and other Google devices that driver is the Google USB Driver; for every other brand it is the phone maker’s own driver. Below are the exact steps to install it on Windows 11, connect with ADB, and fix the driver problems that stop ADB from seeing your phone.

Requirements

  • A Windows 11 PC. Google notes that macOS and Linux do not need a USB driver for ADB. Only Windows does.
  • SDK Platform-Tools from developer.android.com. This is where adb and fastboot come from. The latest stable release is 37.0.1 (July 2026).
  • The right driver for your phone (see the table below).
  • A USB data cable and a phone you can unlock.
Phone ADB driver to use Where to get it
Google Pixel and other Google devices Google USB Driver (current file: usb_driver_r13-windows.zip) Get the Google USB Driver or Android Studio’s SDK Manager
Samsung Galaxy Samsung Android USB Driver for Windows v1.9.5.0 Samsung Developer
Other brands The manufacturer’s USB driver Google’s OEM USB drivers list, or the brand’s support site

For the full list of brands, see our Android USB Driver for Windows 11 guide.

Step 1: Turn On USB Debugging

  1. Find Build number on the phone. On a Pixel it is in Settings > About phone. On a Samsung Galaxy it is in Settings > About phone > Software information.
  2. Tap Build number seven times until you see “You are now a developer!”.
  3. Go back and open Developer options. Google lists it under Settings > System on Android 9 and later (on some phones under Advanced). On other phones, look near the bottom of the Settings list.
  4. Turn on USB debugging.

Step 2: Install SDK Platform-Tools

  1. Download SDK Platform-Tools for Windows from Google’s Platform-Tools page and accept the license terms.
  2. Extract the ZIP, for example to C:\platform-tools.
  3. Open Command Prompt and go to that folder:
cd C:\platform-tools

If you use PowerShell instead, type .\adb instead of adb. PowerShell does not run programs from the current folder unless you add .\ in front.

Step 3: Check Whether Windows 11 Already Has a Working Driver

Connect the phone, unlock it, and run:

adb devices

This only lists devices. It does not change anything on the phone. If you see a serial number with device or unauthorized next to it, Windows already has a working ADB driver (Windows Update or an earlier install may have added it). Skip to Step 5. If the list is empty, install the driver in Step 4.

Step 4: Install the Google USB Driver on Windows 11

These steps are for Google devices. For Samsung and other brands, run the maker’s own installer instead, restart the PC, and go back to Step 3.

Get the driver

  • Direct download: on Google’s Google USB Driver page, accept the terms and download the ZIP. Extract it. The folder you get is usb_driver and contains the file android_winusb.inf.
  • Android Studio: click Tools > SDK Manager, open the SDK Tools tab, tick Google USB Driver and click OK. The files go to android_sdk\extras\google\usb_driver\, and the SDK Manager tells you when a newer driver is available.

Install it with Device Manager

  1. Connect the phone with USB debugging on, and unlock it.
  2. Right-click the Start button and select Device Manager.
  3. Expand Portable Devices or Other devices and find your phone. It may have a yellow warning icon.
  4. Right-click it and select Update driver.
  5. Choose Browse my computer for drivers, click Browse, select the usb_driver folder, and click Next.
  6. When Windows finishes, click Close. The phone now appears as Android Composite ADB Interface.

Google warns that editing android_winusb.inf to add other phones causes security warnings during installation, and that other changes to the driver files can break it. For a non-Google phone, use the manufacturer’s driver instead of editing Google’s.

Fastboot mode needs the driver too

When the phone is in bootloader (fastboot) mode, Windows sees it as a different device and may ask for a driver again. Repeat the same Update driver steps while the phone is in fastboot mode. The Google driver’s setup file includes an entry called Android Bootloader Interface for this mode. Then check the connection with fastboot devices. Our fastboot commands list explains the rest.

Step 5: Authorise the PC and Test ADB

  1. Run adb devices again.
  2. On phones with Android 4.2.2 or later, a dialog asks whether to accept the computer’s RSA key and allow USB debugging. Unlock the phone and tap Allow.
  3. Run adb devices -l. The -l option adds the model name, which helps when several phones are connected.

A working connection looks like this (Google’s example):

List of devices attached
0a388e93      device usb:1-1 product:razor model:Nexus_7 device:flo

device means the phone is connected to ADB. offline means it is not connected or not responding. The RSA dialog is a security feature: a new PC cannot run ADB commands until someone unlocks the phone and accepts it, so only allow computers you trust.

No Driver Needed: Wireless Debugging (Android 11 and Later)

Google points out that wireless debugging avoids common USB problems such as driver installation. It works on phones with Android 11 or higher.

  1. Connect the PC and the phone to the same Wi-Fi network.
  2. In Developer options, tap Wireless debugging, allow it on your network, and choose to pair using a pairing code. Note the IP address, port number and pairing code the phone shows.
  3. On the PC, in the platform-tools folder, run the command below with the IP address and port from the phone, then enter the code when asked:
adb pair ipaddr:port

Replace ipaddr:port with the values shown on your phone, then run adb devices to confirm. With Android 17 and adb 37.0.0 or later, Google’s “ADB Wi-Fi 2.0” connects automatically when the phone joins a trusted wireless debugging network. You can read more in our Android 17 guide. If it does not connect, run adb server-status and check that the version is 37.0.0 or higher and mdns_enabled is true.

Troubleshooting ADB Driver Problems on Windows 11

The phone shows “unauthorized”

The driver is working, but the phone has not accepted this PC. Unlock the phone and look for the USB debugging prompt. If it never appears, use the option in Developer options that revokes USB debugging authorizations, unplug and reconnect, and accept the new prompt. You can also run this command, which resets offline or unauthorized connections from the PC side:

adb reconnect offline

Yellow warning icon or an error code in Device Manager

Codes such as 28, 43 and 52, and the Windows 11 message “A driver can’t load on this device”, are general driver errors. Our Windows 11 USB driver guide covers the fix for each one.

ADB works, but fastboot shows “< waiting for any device >”

Fastboot cannot see the phone. Check that the phone is really in fastboot mode, not just switched on. If it is, Windows probably has no driver for the bootloader interface yet: open Device Manager while the phone is in fastboot mode and repeat the Update driver steps above.

Samsung phone not seen even with USB debugging on

Install Samsung’s own driver, not the Google one. Also check Samsung’s Auto Blocker in Settings > Security and privacy. Samsung says it blocks commands sent over a USB cable from a computer.

Error: “more than one device”

When several phones or emulators are connected, Google says you must name the target. Get the serial number from adb devices and add -s before the command. This example opens a command shell on that one phone (type exit to leave it):

adb -s serial_number shell

Still nothing

Restart the ADB server on the PC. These commands only restart the ADB program on your computer and do not touch the phone’s data:

adb kill-server
adb start-server

Then try a second USB cable. Google says that if a second cable does not help, the problem is probably the phone’s setup, so check Step 1 again.

Related Guides

FAQ

Does the Google USB Driver work with Samsung, Xiaomi or other phones?

Google says its driver is for ADB with Google devices, and that drivers for all other devices come from the phone’s manufacturer. Use Samsung’s driver for Galaxy phones and each brand’s own driver for the rest.

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

No driver is needed. On Ubuntu Linux, Google says your user must be in the plugdev group and the system needs udev rules for Android devices, which the android-sdk-platform-tools-common package provides.

Which version of the Google USB Driver is current?

Google’s download is usb_driver_r13-windows.zip, which is revision 13. If you install it through Android Studio’s SDK Manager, it tells you when your driver is out of date.

Do I need root to use ADB?

No. ADB works on a normal phone once USB debugging is on and you accept the RSA prompt. Root is not required.

https://droid-developers.com/wp-content/uploads/2026/11/adb-driver-windows-11-featured-1024x538.jpghttps://droid-developers.com/wp-content/uploads/2026/11/adb-driver-windows-11-featured-150x150.jpgFahim MahmudDriverHelp & TroubleshootingHow ToAn ADB driver for Windows 11 is the USB driver that lets the adb tool on your PC talk to an Android phone with USB debugging turned on. For Pixel and other Google devices that driver is the Google USB Driver; for every other brand it is the phone...Android Help,Troubleshooting  & Stock Rom