Unknown USB Device

Brian Adshead · Apr 30, 2013

When I plug in my Samsung S3 via USB I get the error 'Unknown USB Device (Invalid Device Descriptor) has a driver problem'. I have installed all the latest Samsung drivers and my Lenovo T420 Laptop is fully updated via Windows Updates. Any help to solve this problem will be appreciated.
Brian

Shubham Verlekar · May 12, 2013

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

Brian Adshead · May 13, 2013

Hi Shubham Verlekar
Thank you for such a long and detailed answer. I went through your list and by the time I got to 2) Worn or faulty ........, I tried a different USB Cable and it worked. I know the old cable is OK but perhaps the resistance was too high! Anyway everything is now OK and once again a sincere Thank You.
Regards
Brian

Shubham Verlekar :

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

Shubham Verlekar · May 13, 2013

Brian Adshead :

Hi Shubham Verlekar
Thank you for such a long and detailed answer. I went through your list and by the time I got to 2) Worn or faulty ........, I tried a different USB Cable and it worked. I know the old cable is OK but perhaps the resistance was too high! Anyway everything is now OK and once again a sincere Thank You.
Regards
Brian

Shubham Verlekar :

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

Your Most welcome but please choose above answer as best it will hep me

goshiga-svani · Jun 21, 2013

Shubham Verlekar :

Brian Adshead :

Hi Shubham Verlekar
Thank you for such a long and detailed answer. I went through your list and by the time I got to 2) Worn or faulty ........, I tried a different USB Cable and it worked. I know the old cable is OK but perhaps the resistance was too high! Anyway everything is now OK and once again a sincere Thank You.
Regards
Brian

Shubham Verlekar :

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

Your Most welcome but please choose above answer as best it will hep me

daniel707 · Jun 22, 2013

You have re-install your all USB drivers but not from your Motherboard DVD. your S3 is not being connecting still so that First all USB drivers have to be Uninstall and then again Install but You have to attached your phone with your PC. you can install from a Driver Solution pack. "DRP" is the software of All drivers combination and can Install every driver in any Configration. Its Generate building process in system and build the drivers/. Your should Try it.

Diman82 · Dec 25, 2013

Make sure that 'USB debugging' option (under development settings) is turned OFF.
That what has resolved this problem in my case IMMEDIATELY!

So, when 'USB debugging' option is ON - problem exists.
When 'USB debugging' option is OFF - no problem.

Guest · Mar 13, 2014

Brian Adshead :

I had a Seagate USB backup drive fail and Windows (Windows 8.1-64) absolutely refused to accept that it was never going to be connected again and kept trying to connect to the device and giving me an "unknown usb device (port reset failed)/ error code 43" error in device manager, and when I tried just uninstalling it it would always reappear. Since I was unable to find a way to make it stop I opened a program I had downloaded a long time ago, USBDeviceview (free at http://www.nirsoft.net/utils/usb_devices_view.html), and it allowed me to tell windows the device was disconnected. All I had to do was find the device in the list, right click on it and select disconnect device (apparently the f9 key would do the same thing after clicking on/selecting the device). What ever you do don't accidentally disconnect your mouse or keyboard or you'll be scrambling to unplug and replug its cable to get Windows to recognize it again!

I tried uninstalling and reinstalling the hubs, but all that did for me was make my mouse and keyboard stop working and make it very hard to reboot (finally had to do a hard reset with the power button). And then when all was "said and done" after that disaster the device and error reappeared.

Guest · Mar 13, 2014

Oops, I think I clicked "answer" twice!

bledubd · Sep 5, 2015

I goto to number two and it also solved my problem with a Samsung NX3000 camera. I was getting a Device Not recognised error. I tried the original cable with my phone and it didn't work there so maybe a cable with high resistance or just faulty. This worked on a Windows 10 running under Mac Boot camp.

Thanks for your help.

Shubham Verlekar :

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

bfairman · Sep 27, 2015

Wow, Im very happy i found this explanation..

it seemed as though it was the cable ans i have been trying 3 different cables... I kept getting code 43 on both my laptops and initially on my desktop.
Woke this morning and tried a different cable on my desktop and whola, it came up on my system.
I was using droid XT912 utility and i realized my device kept disconnecting and reconnecting as unknown...

SO what i began to do was unplug, wait a few seconds and plug in a different port until the utility ran and did what it was supposed to do and now Im back up and running

THIS DEF HELPED....

Shubham Verlekar :

Hello Brain,
Causes
The possible problem descriptions that can be returned for a USB device that failed enumeration in Windows 8 are:
A request for the USB device descriptor failed.
The USB set address request failed.
A USB port reset request failed.
A previous instance of the USB device was not removed.
The USB device returned an invalid USB configuration descriptor.
The USB device returned an invalid USB device descriptor.
Unable to access the registry.
A request for the USB configuration descriptor failed.
A request for the USB device's port status failed.
The USB device returned an invalid serial number string.
The USB set SEL request failed.
A request for the USB BOS descriptor failed.
A request for the USB device qualifier descriptor failed.
A request for the USB serial number string descriptor failed.
A request for the USB language ID string descriptor failed.
A request for the USB product description string descriptor failed.
A request for the Microsoft OS extended configuration descriptor failed.
A request for the Microsoft OS container ID descriptor failed.
The USB device returned an invalid USB BOS descriptor.
The USB device returned an invalid USB device qualifier descriptor.
The USB device returned an invalid USB language ID string descriptor.
The USB device returned an invalid Microsoft OS container ID descriptor.
The USB device returned an invalid Microsoft OS extended configuration descriptor.
The USB device returned an invalid product description string descriptor.
The SuperSpeed link to the USB device keeps going to an error state SSInactive.
The SuperSpeed link to the USB device keeps going to an error state Compliance. If the device is removable, remove the device and then disable/enable from device manager to recover.
The USB device is not compatible with Windows.
The possible problem descriptions for a USB hub failure in Windows 8 are:

The USB hub returned an invalid port status.
The USB hub failed a control transfer request.
The USB hub failed an interrupt transfer request.
The USB hub failed to reset.

Solutions
1) The USB device is "hung".

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

2) Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

3) No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

4) There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

5) The upstream hub has failed or is "hung".

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

6) The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Solution 2
Reinstall Drivers
also uninstall all the roothubs in the device manager

Regards and Enjoy

Search

Unknown USB Device

Brian Adshead

Honorable

Shubham Verlekar

Honorable

Brian Adshead

Honorable

Shubham Verlekar

Honorable

goshiga-svani

Honorable

daniel707

Honorable

Diman82

Honorable

Guest

Guest

Guest

Guest

bledubd

Reputable

bfairman

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page