Device descriptor request failed error is a problem on the universal bus controller section. Which are unique for Windows to determine what device is connected and what drivers are needed. Step 8: Click on Apply this fix. ขั้นตอน 9: Reconnect the USB device. Wait for it to automatically install the drivers. The Device would now be listed in device manager without any errors. If the above steps fail to resolve the problem, then you have to:-ขั้นตอน 10: Uninstall every device under the Universal Serial Bus controllers in Device Manager.

Summary

The Unknown USB device (device descriptor request failed) in Windows Device Manager on HP and Lenovo would stop your USB devices like an Android mobile, flash drive or pen drive from being properly detected for use in Windows 10, 8 or 7, but we finally resolved the USB not recognized problem for you. In case any USB malfunction could endanger data, let EaseUS Data Recovery Wizard recover data from the inaccessible USB drive.

Unknown USB Device (Device Descriptor Request Failed) is a Windows Device Manager error under the 'Universal Serial Bus controllers' section. The current device status is demonstrated as 'Windows has stopped this device because it has reported problems. (Code 43). A request for the USB device descriptor failed.'

What Is a Device Descriptor?

The device descriptor (USB_DEVICE_DESCRIPTOR) is the root of the descriptor tree and contains basic device information. idVendor and idProduct of which are the unique members for the Windows operating system to identify the connected device and determine which device driver must be loaded.

Anyway, we don't care about the tech-savvy's jargon, but only get to know - how do I fix the device descriptor when the request failed?

How Do I Fix Device Descriptor Request Failed?

Driver issues take the most responsibility for an unknown USB device on HP, Lenovo, Dell, and many computers. As you've concerned, the device descriptor request failed error is a generic unknown USB problem, so it's reasonable to suspect a driver issue at present. The USB device here mentioned can be a flash drive, pen drive, Android, digital camera, and any digital gadget that is supposed to use on a Windows machine.

In the next part, we mainly show you the common troubleshooting methods for the device descriptor request failed error in Windows 10. As a matter of fact, Windows 7 and Windows XP users are also having the same problem. Never mind applying the solutions to your own Windows operating system. They're all-OS-versions compatible.

3 Quick Fixes to Unknown USB Device (Device Descriptor Request Failed) in Windows 10

In case that unknown USB device (device descriptor request failed) error happens because the USB port is not working or USB device is damaged, the following three fixes are significant to try before going to further troubleshooting.

1. 1. Try plugging in a working USB drive to check whether the USB port is working or damaged.
2. 2. Plug your USB into a different PC to check whether the USB drive is working or damaged.
3. 3. Check if the USB device shows up in Disk Management. As long as the data matters, download EaseUS free data recovery software to recover data from the inaccessible USB device in advance.

Step 1. Run USB data recovery software.

Connect the USB flash drive to your computer and launch EaseUS USB data recovery software on your PC. Select your USB drive which marks as a removable disk, and click 'Scan' to start finding your lost files.

Step 2. Scan all lost files from USB.

EaseUS Data Recovery Wizard will thoroughly scan your USB flash drive and find all your lost data on it. After the scanning process, use the Filter feature to filter a specific file type. You can check and preview found USB files in this program.

Step 3. Restore all lost files from USB.

A double-click will allow you to preview the file results. Choose the target files and click 'Recover' to save them to a secure location on your PC or other external storage devices.

5 Advanced Fixes to Unknown USB Device (Device Descriptor Request Failed) in Windows 10

Due to the uncertainty of the exact factor that causes your USB drive malfunctioning in this way, the demonstrated solutions are not all supposed to take effect. Hence, take some patience to implement each solution until the problem solved.

1. Use Hardware and Devices troubleshooter

• Press Win+R, type Control Panel and hit Enter.
• Inside Control Panel in the search box type troubleshooter and select Troubleshooting.
• After that select Configure a device under Hardware and Sound and follow the on-screen instruction.
• Click on Apply this fix if any problem is found.

If the unknown USB device error is triggered by hardware issues, it will no longer appear after you try the above steps. If not, you need to move on to the next method to find a fix.

2. Try to Uninstall USB Drivers

• Open Device Manager (Right Click on Windows Logo and Click Device Manager).
• Now find and expand Universal Serial Bus controllers. Now right-click on USB drivers and click Uninstall. Do for all USB drivers one by one.
• Restart your PC then Windows will reinstall the device automatically.

Some people would find that uninstalling and reinstalling the driver only works once. The next time they plug in the drive, and the device descriptor request failed appears again. According to an experienced user who has been suffering the problem for long but finally found the cause of why this method does not work and how to make it work.

3. Disable Fast Startup

• Press Win+R, type Control Panel and hit Enter.
• Click on Power Options and select Choose what the power buttons do in the left pane.
• Click on Change settings that are currently unavailable.
• Under Shutdown settings, uncheck the box next to Turn on fast startup (recommended). Then click on the Save changes button.

4. Turn on Plug and Play in Windows Services

• Press Win+R, type services.msc and hit Enter.
• In Windows Services, find the name Plug and Play. Double-click on it to open the Properties window.
• If the Startup type is currently Manual and the Service status is Running, try to turn it to Disabled and Stopped, save the changes; later change the Disabled and Stopped to Manual and Running again. Click OK and Apply.
• If the Startup type is currently Disabled and the Service status is Stopped, switch to Manual and Running. Click OK and Apply.

Restart your PC and see if the unknown USB device problem has been resolved in Windows 10. if it doesn't work, try to perform a system restore to get rid of this issue.

Hindi Songs Download New Bollywood Mp3 dj latest albums music Top 20 Movie Remix film Ghazals Pop Qawwali Bhakti Sangeet indian free djjohal. Hindi songs free download mp3 hit songs. Free Download Latest Bollywood MP3 Songs, Instrumental Songs, DJ Remix, Hindi Pop, Punjabi, Evergreen Gaana, and Indian Pop MP3 Music at SongMP3.CoM.

5. Restore Your PC To Previous Recovery Points

• Press Win+R, type Control Panel and hit enter.
• Now find and open the Recovery option.
• Select System Restore, follow the on-screen guide and wait until all the recovery points are shown.
• Restore your PC from the right recovery point.

This topic summarizes the new features and improvements for Universal Serial Bus (USB) client drivers in Windows 8.

For information about new features in USB in general, see New for USB Drivers.

New Driver Stack for USB 3.0 Devices

Windows 8 provides a new USB driver stack to support USB 3.0 devices. The new stack includes drivers that are loaded by Windows when a USB 3.0 device is attached to an xHCI host controller. The new drivers are based on Kernel Mode Driver Framework (KMDF) and implement features defined in the USB 3.0 specification. The new drivers are as follows:

• Usbxhci.sys
• Ucx01000.sys
• Usbhub3.sys

The new driver stack maintains compatibility with the existing client drivers that were built and tested on earlier versions of the Windows operating system.

To see an architectural block diagram of the USB driver stack and a brief description of the new drivers, see USB 3.0 Driver Stack Architecture.

Features Supported by the New Stack

The USB driver stack for USB 3.0 devices supports many new features. Some of features are configurable by the client driver. Those features are as follows:

• Static streams for bulk endpoints.

  Streams provide the client driver with the ability to perform multiple data transfers to a single bulk endpoint. The Windows Driver Kit (WDK) for Windows 8 provides new device driver interfaces (DDIs) that allow a client driver to can open up to 255 streams in a bulk endpoint. After streams have been opened, the client driver can perform data transfers to and from specific streams. For more information, see How to Open and Close Static Streams in a USB Bulk Endpoint.

• Chained MDLs

  A client driver can specify the payload in a chain of MDLs instead of a contiguous buffer. This allows the transfer buffer to be segmented in physical memory hence removing restrictions on the number, size, and alignment of buffers. Using chained MDLs can boost performance during data transfers because it avoids double buffering. For more information, see How to Send Chained MDL.

• Function suspend and remote wake-up for composite devices.

  The feature enables a function of a composite device to enter and exit a low-power state, independently of other functions. The function driver can also request a device-initiated remote wake-up. Such a request must be handled by the parent driver of the composite device. The Microsoft-provided parent driver (Usbccgp.sys) supports function suspend and remote wake-up features. The WDK for Windows 8 provides DDIs that allow replacement parent drivers to implement those features. For more information, see How to Implement Function Suspend in a Composite Driver.

Client contract version for USB client drivers

A client contract version identifies a set of rules that the client driver when sending requests to the USB driver stack. Failure to do so might result in an unexpected behavior. For information about those rules, see Best Practices: Using URBs.

A client driver that intends to use the capabilities of the USB driver stack for 3.0 devices, must identify itself with the client contract version of USBD_CLIENT_CONTRACT_VERSION_602. Such a client driver is required to register with the USB driver stack. After registration, the client driver must query the underlying USB driver stack to determine whether the stack supports the required capability. To facilitate those operations, the following KMDF-specific methods and WDM routines have been included in the WDK for Windows 8:

New Routines for Allocating and Building URBs

Windows 8 provides new routines for allocating, formatting, and releasing URBs. The URB structure is allocated by the USB driver stack. If the underlying stack is the new USB driver stack, the URB is paired with an opaque URB context. The USB driver stack uses the URB context to improve URB tracking and processing. For more information about the routines, see Allocating and Building URBs.

The new routines are as follows:

• USBD_AssignUrbToIoStackLocation routine to associate an URB with an IRP. This routine only applies to WDM client drivers.

In addition to the routines in the preceding list, there are new KMDF-specific methods for URB allocation. For KMDF-based client drivers, we recommend that you call,

• The WdfUsbTargetDeviceCreateUrb method (instead of USBD_UrbAllocate) to allocate an URB.
• The WdfUsbTargetDeviceCreateIsochUrb method (instead of USBD_IsochUrbAllocate)to allocate an URB for an isochronous transfer. Those calls allocate a variable-sized URB that is based on the number of isochronous packets required for the transfer. For more information about isochronous transfers, see How to Transfer Data to USB Isochronous Endpoints.

New User Mode I/O Control Requests for USB 3.0 Hubs

Windows 8 provides the new IOCTLs that applications can use to retrieve information about USB 3.0 hubs and their ports. The new IOCTLs are as follows:

By sending the preceding I/O requests to the USB driver stack an application retrieve the following set of information:

• Hub descriptors
• Properties of all ports and companion ports
• Operating speed of a device that is attached to a port

New Compatible ID for WinUSB

Device manufacturers can add 'WINUSB' in the firmware (Microsoft OS feature descriptor) so that Windows recognizes the device as a WinUSB device. In Windows 8, Winusb.inf has been modified to include USBMS_COMP_WINUSB as a device identifier string. That modification enables Windows to automatically load Winusb.sys, as the function driver for the device, as soon as the device is detected. For more information, see WinUSB Device.

New Visual Studio templates for USB client drivers (*New for Beta)

Microsoft Visual Studio 2012 includes USB User-Mode Driver and USB Kernel-Mode Driver templates that generate starter code for a UMDF and KMDF USB client driver, respectively. The template code initializes the USB target device object to enable communication with the hardware. For more information, see the following topics:

For more information, see Getting started with USB client driver development. Extend your driver by performing Common tasks for USB client drivers.

For information about how to implement UMDF and KMDF drivers, see the Microsoft Press book Developing Drivers with the Windows Driver Foundation.

UASP driver

Windows 8 includes a new USB storage driver that implements the USB Attached SCSI Protocol (UASP). The new driver uses static streams for bulk endpoints, as per the official USB 3.0 specification.

Boot support

The Windows to Go feature allows Windows to boot from a flash drive or an external drive. You can boot with your copy of Windows from those drives on various machines.

Enhanced debugging and diagnostic capabilities

Windows 8 provides new USB 3.0 debugging tools to improve diagnosing USB issues faster. There are new USB 3.0 kernel debugger extensions that examine USB 3.0 host controller and device states. You can use USB WPP and event tracing to analyze USB interactions and troubleshoot USB device issues more easily. Windows 8 supports debugging over USB 3.0. For more information, see Setting Up a USB 3.0 Connection Manually.

New USB-specific failure messages in Device Manager

At times, Windows can fail to enumerate an attached USB device. Typically, enumeration failures occur when requests sent to the USB device fail or the device returns incorrect descriptors.

In Windows 8, when such failures occur, the General tab in Device Manager displays a USB-specific error message that indicates the reason for failure.

The error strings are as follows:

• 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 USB device returned an invalid serial number string descriptor.

Related topics

New for USB Drivers
Universal Serial Bus (USB) Drivers