I've been having this issue for weeks now.

I have a Logitech mouse on an Asus x571GT laptop, and one day the Bluetooth connection to my mouse suddenly disappeared.

I checked and the Bluetooth on my laptop disappeared. I checked DEVICE MANAGER and the Bluetooth was gone (unless I selected to show hidden devices) but under the Universal Serial Bus, one of the drivers is called "unknown usb device descriptor request failed" appeared.

If my Bluetooth is working, that error isn't there. The second my Bluetooth disappears, "unknown usb device descriptor request failed" appears under Universal Serial Buses dropdown menu.

I've searched online and...

3) I've uninstalled "unknown usb device descriptor request failed" and restarted the computer. Sometimes the Bluetooth returns and everything is fine for a couple of minutes/hours/days before it suddenly disappears again, and "unknown usb device descriptor request failed" driver reappears

Usb Device Descriptor Failure Windows 8 64 Bit Download

Download 🔥 https://shurll.com/2yGARq 🔥

Before, I did not.

But I did find one solution where I had to add the 'unknown usb device descriptor request failed" into the registry, unplug the USB device, power off, and while it was powered off, I disconnected the Power adapter from the laptop. Waited a minute or two, and plugged back in the power adapter, powered it back up, and once I relogged into Windows, then plugged the USB back in.

So far, it's working.....

So far....

uninstalling the intel bluetooth software from "Programs and Features" where you would uninstall software, as opposed to uninstalling device drivers from "device manager" is what solved this problem for me. i uninstalled the software that way and installed the drivers for the bluetooth from my motherboard manufactures website fixed it.

Believe me, I tried EVERRRRRRRRRYTHING. 

The latest solution I just tried was selecting the 'unknown usb device descriptor request failed" and adding it to the registry and restarting the computer.

I just did it 30min ago, and so far it's working.

But with this 'unknown usb device descriptor request failed" sometimes it works for a few minutes, hours, days before it crashes. 

Hopefully this solution works

If your operating system, BIOS, and drivers are up to date and the issue persists even after performing a full power cycle and uninstalling the intel Bluetooth software from "Programs and Features", the last steps would be to check this issue with Asus since they may need to run some tests on their laptop.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

I am running in bus powered mode, VBUS detect disabled, and I have hardwired an external D+ pullup, because I have not been able to get the internal pullup to activate. I know the hardwired pullup is not recommended, but I don't think that is what is causing my problems. My IOC file is attached.

After this sequence has completed, I have checked the contents of hpcd_USB_OTG_HS->Setup, and the bytes match up with a USB device descriptor request. To me this all seems to mean that the USG_OTG_HS core is active, and is correctly receiving data on the USB lines.

From what I can tell, the critical step that is missing is the "setup stage done" packet, which should trigger another RXFLVL interrupt with packet status == STS_STUP_COMP. When this packet is read out of the FIFO, a setup done interrupt (STUP) should be triggered, which triggers the OEPINT interrupt. In the handler for OEPINT, the setup packet is parsed and the reply to the device descriptor request should be sent.

According to the RM0385 reference manual: "When the setup stage changes to a data IN/OUT stage, the core writes an entry (setup stage done word) to the receive FIFO, indicating the completion of the setup stage."

So to my understanding, the internal pull-up is activated when VBUS is above a certain threshold, as long as the USB_OTG core is active and the soft disconnect bit (SDIS) is not set. I confirmed that GCCFG.PWRDWN, GUSBCFG.FDMOD, and GCCFG.VBUSBSEN, were all set, and that SDIS was reset, by calling HAL_PCD_DevConnect().

I don't have VBUS detect wired on my PCB, but I was able to use jumper wires to connect the pin to 5V. Upon doing so, I confirmed that the a USB connect interrupt was called, and the B session valid bit GOTGCTL.BSVLD changed from 0 to 1. Grounding out VBUS detect caused a USB disconnect interrupt, and GOTGCTL.BSVLD was reset back to 0. At no point did windows detect a device. If memory serves, I scoped the data lines as well and didn't see any sort of pull-up effect. I didn't do too much more debugging since I don't have VBUS detect wired in the current design.

Dont do this - because this cpu/usb has internal pullup, it can switch on. So if it not doing this, you are not at "start the usb now" - so setup something wrong and need do it better. If connecting external pullup - you cannot see this anymore...not helpful.

"I have a 64GB USB flash drive that I haven't used for about a year. Now I constantly get a massage saying that the device has malfunctioned. Device Manager shows a similar massage. I formatted the USB drive twice now and still get the error. I tried unplugging and plugging the device, but nothing changes. I cannot find any further information about the USB drive in Device Manager except the hardware ID is USB\DEVICE_DESCRIPTOR_FAILURE. What should I do to be able to access the USB device properly?"

Your USB device cannot be recognized or reports device descriptor request failure error in Windows 11/10/8/7? We use USB devices all the time and it is quite frustrating when it is malfunctioned, not working or not recognized in Windows. The USB device_descriptor_failure is one of the issues we often encounter. In this article, you can find 9 reliable solutions to fix the problem and make your drive work again.

When it comes to transferring data from one device to another, USB (Universal Serial Bus) devices might be the first choice. USB devices come in various types, such as USB flash drives, memory cards, pen drives, etc. They are portable, small-sized and large in capacity, making users carry huge amount data or transfer data between devices.

What does "Unknown USB Device (Device Descriptor Request Failed)" error mean? The USB device descriptor is used to store information for USB drives and it is responsible for recognizing different USB devices. If it fails to work properly on Windows 10 or Windows 11, the USB drive cannot be recognized by operating system and you may get errors like code 43. When you insert the USB device to your computer, you may get one of the following messages depending on your PC.

If you open Device Manager, you can see the USB device which is displayed under Universal Serial Bus controllers is marked with a yellow exclamation icon and with message "Unknown USB Device (Device Descriptor Request Failed)". If you check its properties, you can see error message " Windows has stopped this device because it has reported problems. (Code 43) . A request for the USB device descriptor failed" in the Device status section of the General tab.

In addition to error messages above, you may also encounter other symptoms, for example, the USB device my repeatedly disconnect and reconnect automatically, making it difficult to use. In some cases, the USB device might become unresponsive or not respond to any commands from the computer. Sometimes, the Device Descriptor Request Failed error is not limited to USB storage devices, which means it may also occur to other USB peripherals such as keyboards, mice, printers, etc.

If you are troubled by this issue now and have no idea how to fix it. How to solve a request for the USB device descriptor failed? Just continue reading the rest part which will present a couple of methods to help you troubleshoot this issue without losing data.

If your computer has installed Windows 10 Creator Update, you can try the new troubleshooting tool to fix the problem. It is a Windows built-in universal troubleshooting tool and it can be used to check and repair various system problems.

The USB device descriptor failure issue usually has something to do with problematic USB drivers, for example, USB drivers on your computer might be outdated, corrupted, missing or broken. Therefore, you can try updating drivers for USB controllers to fix the issue.

Bad sectors are areas that cannot be read or written, if a disk contains too many bad sectors, you'll have to consider replacing it with a new one. Here we'd like to recommend free partition manager software to check and repair bad sectors for USB drives. You can download DiskGenius Free Edition and follow steps below to repair damaged USB drives. It should be noted that the bad sector scanning process is safe, and yet the bad sector repairing process damages data and you should back up or recover data first if you want to repair bad sectors on USB drives.

The fast startup feature relates to hibernate and shutdown, which is designed to make computer boot faster. However, some users report that this feature makes computer performs so quickly that Windows 10 cannot detect USB device and the USB device descriptor failure appears. If that is the case, you can follow these steps to turn off fast startup.

In some cases, operating system will put the USB port in low-power mode if the USB selective suspend setting is enabled. If so, the USB drive connecting to this port won't be able to work normally and cause USB device_descriptor_failure problem. To solve the problem we can try disabling this feature via following steps:

Windows updates are crucial for keeping your operating system secure, stable, and up to date with the latest features and improvements. If you're using Windows 11 or Windows 10, make sure your operating system is up to date. Sometimes, an outdated driver or system component can cause USB-related issues. Here are how to check and install Windows updates: 152ee80cbc

download football rocker for pc

hytera programming software download

download draw a stickman epic pro