USB device not recognized


  1. Posts : 5
    Win10, Linux Mint 17.2
       #1

    USB device not recognized


    I have a Lenovo Android phone which after it self-upgraded it's software (customized Android UI) does not get recognized when it's plugged into my Lenovo G50 notebook. When plugged in, Windows gives "USB device not recognized" and the phone cannot be accessed. I've tried different USB ports, cables, uninstall/reinstall the driver, nothing works. I also tried the Win10 hardware troubleshooter feature multiple times to no avail. I'm at a loss how I might resolve this problem - and Lenovo Support forum is of no help. Any help is greatly appreciated. Below is the details in the Windows event log...

    Log Name: Microsoft-Windows-Kernel-PnP/Configuration
    Source: Microsoft-Windows-Kernel-PnP
    Date: 7/31/2016 2:04:57 PM
    Event ID: 400
    Task Category: None
    Level: Information
    Keywords:
    User: SYSTEM
    Computer: DESKTOP-TOT92RJ
    Description:
    Device USB\VID_0000&PID_0002\5&2b47b14&0&3 was configured.


    Driver Name: usb.inf
    Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
    Driver Date: 06/21/2006
    Driver Version: 10.0.10586.0
    Driver Provider: Microsoft
    Driver Section: BADDEVICE.Dev.NT
    Driver Rank: 0xFF0000
    Matching Device Id: USB\DEVICE_DESCRIPTOR_FAILURE
    Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000
    Device Updated: false
    Parent Device: USB\ROOT_HUB30\4&34c3c5a1&0&0
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>400</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-31T17:04:57.083340500Z" />
    <EventRecordID>473</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="4276" />
    <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
    <Computer>DESKTOP-TOT92RJ</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="DeviceInstanceId">USB\VID_0000&amp;PID_0002\5&amp;2b47b14&amp;0&amp;3</Data>
    <Data Name="DriverName">usb.inf</Data>
    <Data Name="ClassGuid">{36FC9E60-C465-11CF-8056-444553540000}</Data>
    <Data Name="DriverDate">06/21/2006</Data>
    <Data Name="DriverVersion">10.0.10586.0</Data>
    <Data Name="DriverProvider">Microsoft</Data>
    <Data Name="DriverInbox">true</Data>
    <Data Name="DriverSection">BADDEVICE.Dev.NT</Data>
    <Data Name="DriverRank">0xff0000</Data>
    <Data Name="MatchingDeviceId">USB\DEVICE_DESCRIPTOR_FAILURE</Data>
    <Data Name="OutrankedDrivers">usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000</Data>
    <Data Name="DeviceUpdated">false</Data>
    <Data Name="Status">0x0</Data>
    <Data Name="ParentDeviceInstanceId">USB\ROOT_HUB30\4&amp;34c3c5a1&amp;0&amp;0</Data>
    </EventData>
    </Event>
      My Computer

  2. aardvark's Avatar
    Posts : 164
    Pro x64 Desktop v1607 14393.51, Home x64 Laptop v1607 14393.51
       #2

    Leave your device unplugged, access device manager, select "show hidden devices" and see if you can find the old inactive device (greyed-out). Once found, delete it, reboot, plug your updated device back in and see if it is now properly recognized:

    USB device not recognized-screenshot-13-.png
      My Computer


  3. Posts : 5
    Win10, Linux Mint 17.2
    Thread Starter
       #3

    aardvark said:
    Leave your device unplugged, access device manager, select "show hidden devices" and see if you can find the old inactive device (greyed-out). Once found, delete it, reboot, plug your updated device back in and see if it is now properly recognized:
    Nope, that does not work. I've done that numerous times. No change. Same problem. The device manager shows the error as...
    "Windows has stopped this device because it has reported problems. (Code 43)
    A request for the USB device descriptor failed."


    Any other ideas?
      My Computer


  4. Posts : 5
    Win1032
       #4

    Hi bbaker6212,

    I know that I'm replying to an old thread .... but I'm struggling with exactly the same problem with one specific model of Verbatim USB-stick, which is first recognized (drive letter available) and after a couple of seconds the "descriptor failed".
    I tried already everything I could think of and that I could find on the internet.

    Have you been able to solve that ?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:20.
Find Us




Windows 10 Forums