This happened shortly after the 204 update. Not able to identify the specific hardware causing the issue going into properties and the various details. Tried unplugging mouse, keyboard, webcam. Reinstalled chipset driver.
Any way to identify the specific hardware causing this?
I found this article at an HP forum. It is marked solved so it may be of help. Fix for Unknown USB Device (Device Descriptor Request Failed)?
Thanks Lance. I had gone through most of that without success. I do see in control panel/devices it's telling me the DESKTOP is the issue???????
Took this issue to Microsoft tech support. After a valiant 2 hour attempt to resolve it tech told me they were out of ideas. Escalated to level 2. After an hour level 2 said two options: revert to Windows 1909 or get a bios update from Asus. These guys tried hard, but disappointed the device causing the "issue" couldn't even be identified.
Anyone else with an Asus Z170 MB experiencing this problem with Windows 10 2004?
I just resolved the problem. Even though bluetooth drivers were installed "successfully", just noticed no on/off bluetooth option in settings and no bluetooth icon in action center. Bluetooth was enabled in bios. Disabled it and rebooted. Shut computer down and unplugged power. Restarted and reenabled bluetooth. Bluetooth on/off option now available in settings and in action center. No device descriptor failed message in device manager.
Ten Forums are inspirational in so many ways.
Even though it is working at the moment, I do suggest that you check your Bluetooth adapter. Pull it out and push it back in again [while the computer is turned off].
The reason I suggest this is that I had a [USB] Device Descriptor Request Failed error earlier today.
- I knew which equipment it was [well, that it was one of two identical ones] because one entry had disappeared from Device manager.
- When I poked around the back I found that its inline USB connection was ever so slightly slipping out. I pushed it back on [the movement was less than a fingernail's thickness] and the fault was fixed.
- So perhaps your Bluetooth adapter is ever so slightly slipping out.
Best of luck,
Denis
Thanks Dennis, but I don't even have a bluetooth device. Bluetooth capability is on the MB of course, but all my hardware is plugged in. Once in awhile I will pair my phone to the PC but that's about it. When I was troubleshooting the problem, I unplugged and replugged every USB device (they all worked) and tried different USB ports to no avail. For some reason the install of 2004 resulted in Windows 10 stating my PC is NOT bluetooth capable??? If I had a bluetooth keyboard/mouse maybe the issue would have been identified earlier.
I wasn't referring to any connected Bluetooth device but to your Bluetooth adapter itself [which might well be a combined WiFi-Bluetooth adapter for all I know].
Obviously, there is no hurry since you are not using it for anything but if you find a service manual for your computer / motherboard, it will identify the Bluetooth [or combined Bluetooth-WiFi] adapter as a separate piece of hardware inside the computer that is connected to your motherboard. That's what I am suggesting has worked [ever so slightly] loose.
This, just by way of example, is the one in my desktop. They all look more or less the same.
- The black bar on the right of the picture is fixed to the motherboard and is what the WiFi-Bluetooth adapter is pushed into.
- The two wires on the left are the two [internal] aerial connections to the adapter.
Denis
Oh, sorry Denis, you're talking about the wifi/bluetooth connection within the MB. That makes sense. I checked that and every other internal connection after testing usb ports. All was/is fine.
Of course, once I figured out it is an unrecognized bluetooth issue, I can find the same issue with a search. It's even happeneing to people with a brand new MB.
I saw how hard the very capable Microsoft techs worked on the issue, as they took control of the screen. Going through logs, searching for clarity on the log messages and trying just about everything to no avail. Nothing identified the issue as bluetooth related.
We get build after build of Windows 10. IMHO the OS developers need to work hard on improving the troubleshooting feature. The OS tells you "Hey user, you have a device descriptor failed issue but even the best Microsoft tech guys won't be able to identify the problem." Really???
Quote
