我的Windows 8也遇到了同样的问题。Android/SDK USB驱动程序安装正确，但我忘记从我的手机安装USB驱动程序。安装手机USB驱动后，ADB工作正常。

我希望这能有所帮助。

Edit: I recommend you DO NOT run ADB under VirtualBox if you are using a Windows Host. Somehow I got VirtualBox to lock the device drivers on the host, eventually making it so that the ADB wouldn't work on the client nor the host for any device I plugged in. To fix, I removed VirtualBox extensions on the host and ran http://www.nirsoft.net/utils/usb_devices_view.html to delete the incorrect drivers. I could not get the correct drivers to load while VirtualBox extensions were installed, and this problem was a complete bastard to diagnose and fix.

编辑2:以下也可能是过时的，现在谷歌已经发布了一个集成的ADB扩展Chrome。

真是一场安装噩梦……下面是让我的Nexus 10在VirtualBox下运行的XP虚拟机上被识别的步骤:

If you get asked to install Nexus 10 drivers, make sure to untick "don't ask again" (you WANT to be asked again!). Plug in the Nexus 10 USB connection Turn on debugging in the Nexus 10 settings Developer menu (tap "About Tablet" 7 times to get that menu). In your virtual machine settings (host), add the samsung Nexus 10 device to the USB Device Filters (important - selecting it from the devices menu didn't seem to work). In guest install java jre (if you don't have java installed). In Control Panel, change Java settings so that java doesn't run in the browser (to help prevent security issues). In guest get the adk zip file and put it somewhere permanent. I needed to delete the .android config directory from the user directory because I moved the directory. Run the SDK Manager.exe - if it doesn't work, try running sdk\tools\android.bat which seems to give better error reporting. From SDK Manager install the Google USB driver package. Unplug the Nexus 10 and plug it in again, and install the Google USB driver package. Restart the guest. running c:>[...]\sdk\platformtools> adb devices finally shows me the device...

此外，在android工作室，你可以通过SDK管理器安装谷歌USB驱动程序，你应该在这之后设置。

确认您拥有正确的平台SDK工具

对于Windows 10，由于Visual Studio 2017 EMDK为Xamarin提供的版本不够，不得不从Android手动下载最新的平台SDK工具。除了adb.exe设备，其他设备都正常工作。

https://developer.android.com/studio/releases/platform-tools

手动下载平台工具后，无论USB配置(充电、MTP等)，设备都显示出来。

在此阶段安装模拟器设备还有助于查看问题是出在adb还是物理设备上。

List of devices attached
12345D1234      device
emulator-5554   device

For the Blu Studio 5.5s ADB drivers, you have to go through this hoop. I am certain it is the same with all Blu phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the Blu device with USB cable and USB Debuggin off, you will see that Windows 7 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, BLU STUDIO 5.5 S (or the device you are working with). Do not bother getting the hardware ID yet - just observe that this happens (which indicates you are good so far and don't have a bad cable or something).

Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the BLU STUDIO 5.5 S or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices, in this example the name that appears is BLU STUDIO 5.5 S. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.

对于BLU STUDIO 5.5 S，我得到:

USB\VID_0BB4&PID_0C02&REV_0216&MI_00
USB\VID_0BB4&PID_0C02&MI_00

(注意，如果你不按顺序这样做，HW ID将与手机USB调试关闭时不同。你想复制的值，它改变时，USB调试是ON)

现在按照上面的说明进行操作，当然要定制添加INF文件的行，使用与您自己的手机相关的行，而不是与Nexus 10相关的行。下面是要定制的内容;当你下载SDK时，你应该有一个从ZIP扩展而来的文件结构，如下所示:

\adt-bundle-windows-x86_64-20140321\sdk\extras\google\usb_driver

找到名为android_winusb的文件。usb_driver文件夹中的Inf 复制它并命名为任何名称，比如myname.inf 编辑myname。Inf和添加行如上所述，只修改为您的特定电话。例如，对于BLU STUDIO 5.5 S，我根据提示在2个位置添加了以下2行。

;BLU STUDIO 5.5 S
%SingleAdbInterface%        = USB_Install, USB\VID_0BB4&PID_0C02&REV_0216&MI_00
%CompositeAdbInterface%     = USB_Install, USB\VID_0BB4&PID_0C02&MI_00

请注意，您将这些行添加到32位和64位部分中，以与教程中的示例相匹配。

Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the myname.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.

现在您可以开始使用adb命令了。

这种情况似乎出现在一些ADB驱动程序中。我在一些谷歌设备上遇到过同样的问题，安装Universal ADB windows驱动程序每次都为我解决了这个问题。