When you plug in an Android phone and see a yellow exclamation mark in Device Manager under an entry called "Android Composite ADB Interface" or simply "Android ADB Interface," Windows is telling you it found the device but cannot load a suitable driver for it. This is one of the most common obstacles people hit when trying to use ADB for the first time, and it is fixable without third-party driver installers or sketchy downloads.
The yellow exclamation mark means Windows detected the USB device but could not match it to a driver. Several things can trigger this state. The most common is that Windows never had an appropriate OEM driver for your phone's vendor ID, so it shows the device as unrecognized. A second cause is that Windows Update automatically pushed a generic composite USB driver that conflicts with the ADB interface entry, resulting in a code 10 or code 43 error even though a driver file is technically loaded. A third scenario occurs after upgrading Windows: the old driver entry becomes orphaned and the new OS build cannot use it.
The generic fix that works across most Android devices uses the android_winusb.inf file bundled with Android Platform Tools. This INF file contains USB vendor IDs for dozens of manufacturers and instructs Windows how to bind the ADB interface correctly. You do not need a phone-specific driver to get basic ADB working in most cases; the generic INF is enough. You only need an OEM driver when you want features beyond ADB, such as MTP file transfer through Windows Explorer, or when your device uses a chipset that Windows refuses to enumerate via the generic path.
Before jumping to the fix, identify the error code shown in the device Properties dialog. Open Device Manager, right-click the problem device, choose Properties, and look at the Device Status box on the General tab.
| Error Code | Meaning | Recommended Action |
|---|---|---|
| Code 28 | Drivers for this device are not installed | Install the driver manually using android_winusb.inf or the OEM package |
| Code 10 | Device cannot start — driver loaded but device failed | Uninstall the current driver entry, reconnect, and install correct driver |
| Code 43 | Windows stopped the device because of reported problems | Often caused by Windows Update overwriting the driver; re-apply OEM driver and block Windows Update for this device |
| Code 52 | Driver signature enforcement blocked an unsigned driver | Enable test signing mode or use a signed version of the driver; see notes below |
| Code 1 | Device is not configured correctly | Re-run the driver install; verify USB Debugging is enabled on the phone |
This method works for Code 28 and most Code 10 cases. It uses the driver files that ship with Android Platform Tools, so nothing extra needs to be downloaded beyond what you should already have for ADB use.
C:\platform-tools. Do not extract to the Downloads folder, which may be reorganized later.usb_driver subfolder inside your Platform Tools directory. Select the file android_winusb.inf and click Open, then OK.adb devices. Your device should appear with status device after you approve the RSA key prompt on the phone.The generic android_winusb.inf driver handles ADB and fastboot communication reliably on most devices, but it does not cover every scenario. If your phone is from a brand that uses a proprietary USB mode, or if MTP file transfer does not work after the generic install, you should switch to the manufacturer's driver package. Samsung phones in particular should use Samsung USB Driver for Mobile Phones rather than the generic INF, because Samsung's ADB interface uses a different Windows driver class. MediaTek-based phones that need VCOM mode for firmware flashing require the MTK VCOM driver entirely separate from the ADB path. In both cases, uninstall the generic driver through Device Manager first, then install the OEM package cleanly.
Windows Update occasionally replaces manually installed drivers with whatever it finds in its catalog, which can break your ADB setup without warning. To prevent this, open Device Manager, right-click your correctly-installed ADB device, select Properties, go to the Driver tab, and click Update Driver. Choose "Browse my computer" and on the next screen click "Let me pick from a list." Check the box that says "Only show compatible hardware." Select the correct Android ADB entry and click Next. This re-affirms the driver binding. Then open Group Policy Editor (run gpedit.msc), navigate to Computer Configuration → Administrative Templates → System → Device Installation → Device Installation Restrictions, and enable the policy "Prevent installation of devices that match any of these device IDs," adding your device's hardware ID. On Windows 10 and 11 Home, where Group Policy is not available, you can achieve the same result by setting the driver update to manual via the optional updates settings in Windows Update.
Code 52 indicates that Windows Driver Signature Enforcement blocked the driver because it lacks a valid Microsoft signature. The generic android_winusb.inf included in recent Platform Tools releases is WHQL-signed and should not trigger Code 52. If you see it anyway, verify you are using a current Platform Tools release (33.0 or later). Older driver packages, especially redistributed ones from unofficial sites, may carry expired or missing signatures. Download fresh Platform Tools from the official Android developer site and repeat the manual install. As a last resort only, you can disable signature enforcement temporarily by restarting Windows into Advanced Startup Options and selecting "Disable Driver Signature Enforcement," but this is not recommended for production machines.