ADB Device Not Found Error on Windows: Fixed

If you see “adb: device not found” or “error: device not found” when running ADB commands on Windows, the fix is usually a driver issue, a USB connection problem, or a missing authorization prompt. This article walks through the exact steps to get your Android device recognized by ADB on Windows 10 and 11.

What Causes the ADB Device Not Found Error?

ADB (Android Debug Bridge) is a command-line tool that lets your PC communicate with an Android device for debugging, installing apps, or running shell commands. The “device not found” error means the ADB server cannot see your phone or tablet over USB. Common causes include:

• Outdated or missing USB drivers for your specific phone brand.
• USB debugging not enabled in Developer Options.
• The device is in “charging only” mode instead of “file transfer” (MTP) mode.
• A faulty or non-data USB cable.
• The ADB server is stale and needs restarting.
• The authorization prompt on the phone was dismissed or not accepted.

Step-by-Step Fix for ADB Device Not Found

Follow these steps in order. Most users resolve the issue by step 3 or 4.

1. Enable Developer Options and USB Debugging – On your phone, go to Settings > About phone and tap “Build number” seven times. Then go to Settings > Developer options and turn on “USB debugging.”
2. Connect your phone and choose the right USB mode – Plug in the phone, then pull down the notification shade and select “USB for file transfer” (MTP). Avoid “Charging only” or “No data transfer.”
3. Accept the RSA authorization prompt – When you first connect, your phone shows a dialog asking “Allow USB debugging?” Tap “Allow” and check “Always allow from this computer.” If you missed it, unplug and replug the cable.
4. Restart the ADB server – Open Command Prompt or PowerShell in your platform-tools folder and run:

   adb kill-server
   adb start-server
   adb devices

   This often clears stale connections.

5. Install the correct USB driver – For Pixel/Nexus devices, install Google’s USB driver via Android Studio or the standalone driver. For Samsung, use Samsung USB Driver. For other brands, check the manufacturer’s website for a Windows USB driver. After installing, restart your PC and reconnect.
6. Try a different USB port or cable – Use a rear port on a desktop, and test a cable known to transfer data (not just charge). Some USB-C cables are charge-only.
7. Update or reinstall platform-tools – Download the latest platform-tools zip from Google’s developer site, extract it, and run adb.exe from that folder. Old versions can have bugs.

Check Device Manager for Driver Issues

If ADB still doesn’t see the device, open Device Manager (right-click Start > Device Manager). Look under “Portable Devices” or “Other devices.” If you see a yellow triangle or “ADB Interface” with a warning, the driver is not installed correctly. Right-click it, choose “Update driver,” then “Browse my computer for drivers” and point to the folder where you extracted the platform-tools (or the manufacturer’s driver). If you see “Android Composite ADB Interface” without a warning, the driver is fine.

Common Mistakes and Misconceptions

• Mistake: Using the wrong USB mode. Some phones default to “Charging only”; ADB requires a data connection. Always select “File Transfer” or “MTP.”
• Mistake: Not enabling “USB debugging” after a reboot. Some devices reset the setting after a system update. Re-check it.
• Misconception: “Device not found” means the phone is broken. It usually means the PC can’t talk to the phone, not that the phone is faulty.
• Mistake: Running ADB from a different directory. If you type adb and get “not recognized,” you need to be in the platform-tools folder or add it to your PATH. Use cd C:\path\to\platform-tools first.

If Nothing Works: Advanced Troubleshooting

For persistent cases, try these additional steps:

• Use a different computer – If ADB works on another PC, the problem is your Windows configuration, not the phone.
• Disable and re-enable USB debugging – Toggle it off, wait a few seconds, then on again. This can reset the authorization state.
• Revoke USB debugging authorizations – In Developer Options, tap “Revoke USB debugging authorizations,” then reconnect and accept the prompt again.
• Check for Windows updates – Some Windows updates fix USB driver conflicts. Install all pending updates and restart.
• Use a different ADB variant – Some users report success with the ADB included in Android Studio, which bundles its own driver.

Frequently Asked Questions

Why does ADB say “device not found” but my PC sees the phone as a drive?

This usually means the USB driver is installed for MTP (file transfer) but not for ADB. The phone appears as a storage device, but the ADB interface driver is missing. Install the manufacturer’s USB driver and check Device Manager for “ADB Interface” without a warning.

Do I need to install a separate driver for every phone brand?

Yes, often. Samsung, Xiaomi, OnePlus, and others use proprietary drivers. Google’s generic ADB driver works for Pixel and some other devices, but for reliable detection, use the brand-specific driver from the manufacturer’s website.

What if I don’t see the “Allow USB debugging” prompt?

First, unplug and replug the cable. If it still doesn’t appear, go to Developer Options and tap “Revoke USB debugging authorizations,” then reconnect. Also ensure the USB mode is set to “File Transfer” – some phones suppress the prompt in “Charging only” mode.

Can I use ADB over Wi-Fi to avoid USB issues?

Yes. On Android 11 and later, you can use “Wireless debugging” in Developer Options. Pair with a code, then run adb pair and adb connect. This bypasses USB driver problems entirely.

Why does ADB work on Linux/Mac but not Windows?

Windows requires proper USB drivers, while Linux and macOS often have built-in support for ADB. On Windows, the driver installation step is the most common failure point. Follow the driver steps above, and it should work.

Is it safe to install random “ADB driver” tools from the internet?

No. Only use drivers from the phone manufacturer or Google’s official platform-tools. Third-party driver packs may contain malware or cause system instability. Always download from official sources.

Related

• iPhone Camera Settings for Northern Lights
• RSAT Won’t Install in Windows 10? Real Fixes
• Fix iTunes Won’t Open on Windows or Mac