This error crops up in Device Manager every single week in our support queue. A user plugs in a USB device, external hard drive, flash stick, printer, you name it, and instead of Windows recognizing it normally, they get hit with "Unknown USB Device (Device Descriptor Request Failed)". The device sits there in Device Manager with a yellow warning icon, completely unusable. And here's the frustrating part: nine times out of ten, it's something fixable without sending the device back.

TL;DR

USB device descriptor request failed means Windows can't read your device's ID data during startup. Start by trying a different USB port and cable (fixes 30% of cases). If that doesn't work, uninstall the device in Device Manager and reconnect it, disable Fast Startup and USB selective suspend, then update your chipset drivers from the PC manufacturer. If it fails on multiple computers, the device hardware is likely dead.

⏱️ 14 min read✅ 75% success rate📅 Updated June 2026

Key Takeaways

The error means Windows failed to read the device's identification (descriptor) during enumeration
Most fixes take 5-30 minutes and don't require special tools or advanced knowledge
Always test the device on another computer to rule out device-side hardware failure
Updated chipset drivers from the motherboard manufacturer fix this more often than generic Windows drivers
If the problem started after a Windows update, rolling back that update can work as a temporary fix

At a Glance

Difficulty: Easy to Medium
Time Required: 15, 45 mins depending on solution
Success Rate: 75% of users resolve this with software fixes

What Causes USB Device Descriptor Request Failed?

When you plug a USB device into your computer, Windows runs through a process called enumeration. It sends a request to the device asking "Hey, who are you? What are your specs?" The device responds with a descriptor, a data structure that contains the device's vendor ID, product ID, supported protocols, power requirements, and other identification details. Windows reads this descriptor and uses it to match the correct driver and set up the device properly.

When that descriptor request fails, it means Windows never got a readable response. Could be the device didn't send one. Could be the response got corrupted in transit. Could be Windows's USB driver stack didn't understand it. Could be the device ran out of power mid-enumeration. Any of these scenarios results in the same error: Unknown USB Device (Device Descriptor Request Failed).

The root causes fall into five buckets. First, something's wrong with the physical connection: a faulty port on your PC, a damaged cable, a cheap unpowered hub between you and the device, or a wonky connector. Second, your PC's USB or chipset drivers are outdated, corrupted, or missing entirely. Third, Windows power-management features like Fast Startup or USB selective suspend are interfering with the initialization sequence. Fourth, the device isn't getting enough power, especially common with bus-powered external drives that try to run on USB power alone. Fifth, the device itself has internal hardware damage and can't send a valid descriptor no matter what.

Info: If the device worked fine yesterday and broke today, it's likely a driver issue, power-management conflict, or physical damage to the cable. If the device never worked on your PC but works on another computer, your port or driver is the culprit. If it fails on every computer you try, the device is probably dead.

Quick Fix for USB Device Descriptor Request Failed Errors

Try a Different Port and Cable Easy

Unplug the USB device completely
Wait 5 seconds, then plug it firmly into a different USB port on your PC. Don't use a USB hub for this test, connect directly to the computer.
Watch Device Manager for changes
Open Device Manager (press Windows Key + X, select Device Manager). If the device now appears with a proper name instead of "Unknown USB Device", you've found a faulty port.
Try a different cable if applicable
If the device uses a removable cable (external hard drive, printer, etc.), swap it for a different cable. Cables wear out and develop intermittent connection issues that cause enumeration failures.
Avoid unpowered hubs during testing
Cheap USB hubs can't supply stable power. Use direct ports on your computer, or if you must use a hub, use a powered hub with its own power adapter.
Reboot if the error persists
Unplug the device, restart your PC fully, then plug it back in after Windows finishes booting.

If the device now shows up normally in Device Manager with its actual name, the problem was a faulty port or cable. If the error persists, move to the next solution.

Intermediate Fixes: Software and Power-Management Issues

If swapping ports didn't work, the problem is likely on the software side. Windows power settings or stale driver configurations can block proper USB enumeration. Here's where you dig into control panels and Device Manager.

Uninstall and Reinstall the Unknown Device Easy

Open Device Manager
Press Windows Key + X, select Device Manager, or search for "Device Manager" in the Start menu.
Locate the Unknown USB Device entry
Expand the section called "Other devices" or look under "Universal Serial Bus controllers". You should see a device with a yellow warning icon labeled "Unknown USB Device" or "USB Device (Device Descriptor Request Failed)".
Right-click and select Uninstall device
A dialog appears asking to confirm. Check the box "Attempt to remove the driver software for this device" and click Uninstall.
Reconnect the device or reboot
Either plug the device back in immediately, or restart Windows. On restart, Windows will run enumeration again from scratch and attempt to install a fresh driver.
Check Device Manager again
If the device now appears with its proper name and no warning icon, the reinstall worked. If it still shows as Unknown, move to power-management fixes.

Reinstalling the device works when the driver entry got stuck or corrupted. Fresh enumeration often bypasses whatever caused the original failure.

Disable Fast Startup Easy

Open Control Panel
Search for "Control Panel" in the Start menu and open it.
Navigate to Power Options
Click System and Security, then Power Options.
Click "Choose what the power buttons do"
This link is on the left sidebar.
Click "Change settings that are currently unavailable"
You need admin privileges to modify these settings. Windows will prompt you if needed.
Uncheck "Turn on fast startup (recommended)"
This option appears under Shutdown settings. Uncheck it.
Click Save changes and restart your PC
The change takes effect immediately when you restart.

Fast Startup skips some initialization checks to speed up boot time. Disabling it forces Windows to fully initialize USB controllers and drivers, which often fixes descriptor errors that happen after shutdown/restart cycles.

Disable USB Selective Suspend Medium

Open Control Panel
Search for "Control Panel" in the Start menu.
Go to Power Options
Click System and Security, then Power Options.
Click "Change plan settings" for your active power plan
Usually labeled "Balanced" or similar.
Click "Change advanced power settings"
A window titled "Power Options" appears with tabs and expandable categories.
Expand the USB settings category
Look for "USB settings" in the tree. If you don't see it, scroll down, it's usually near the bottom.
Expand "USB selective suspend setting"
You'll see options for battery and plugged-in modes.
Set both to "Disabled"
Change the value for both Battery and Plugged in to Disabled. This prevents Windows from power-cycling USB devices.
Click Apply, then OK, and restart
The changes take effect after a restart.

USB selective suspend is designed to save power by turning off unused USB devices. But if a device is slow to wake up, it may not respond to the initial descriptor request, triggering the error. Disabling it forces constant power delivery.

Advanced Fixes: Drivers and Power-Management Deep Dives

If intermediate fixes didn't work, you need to get into driver installation and power-management at the USB controller level. These solutions take longer but hit the root cause when it's buried in the driver stack.

Update Chipset and USB Drivers from Manufacturer Hard

Identify your motherboard or PC model
On a laptop, search for your brand and model number (e.g., "Dell XPS 15"). On a desktop, open Device Manager, find "System devices", and look for chipset entries (e.g., "Intel Z790 Chipset"). Or, on Windows 11/10, open Settings > System > About and note your System Model.
Visit the manufacturer's support page
Go to Intel, AMD, Asus, MSI, Dell, Lenovo, HP, whoever made your motherboard or PC. Search for your exact model.
Download chipset and USB drivers
Look for "Chipset Drivers" and "USB Drivers" or "USB 3.0 Host Controller Drivers". Download the latest version for your Windows version (Windows 11 or Windows 10).
Install the drivers in the correct order
Usually, install chipset first, then USB drivers. Run the installer and follow the prompts. Some installers require a restart between them.
Restart Windows fully
After all driver installations complete, do a full restart.
Test the USB device
Plug in the device and check Device Manager. Manufacturer drivers often include firmware updates and initialization fixes that generic Windows drivers miss entirely.

Warning: Generic drivers from Windows Update are often out of date. Manufacturer-provided drivers are specifically tuned for your hardware and carry critical USB enumeration fixes. Always prefer the manufacturer over Windows Update for chipset and USB controller drivers.

Reinstall USB Root Hub Controllers in Device Manager Hard

Open Device Manager
Press Windows Key + X and select Device Manager.
Expand "Universal Serial Bus controllers"
Click the arrow next to this category to see all USB controllers and hubs.
Look for "USB Root Hub" entries with warning icons or multiple entries
If you see yellow exclamation marks or multiple Unknown USB Device entries, these are problematic controllers.
Right-click each problematic entry and select "Uninstall device"
Check the box to remove driver software. Uninstall one at a time, especially if there are multiple USB Root Hubs.
Reboot Windows
Windows will detect and reinstall USB controllers automatically on startup.
Verify in Device Manager
After restart, expand Universal Serial Bus controllers again. You should see fresh USB Root Hub entries with no warning icons.

Info: USB Root Hubs are the software representations of the physical USB ports on your motherboard. Reinstalling them clears stale driver data and forces Windows to negotiate fresh power and communication settings with each port.

Disable USB Power-Management at the Root Hub Level Hard

Open Device Manager and expand Universal Serial Bus controllers
Press Windows Key + X, select Device Manager, then expand the USB controllers category.
Right-click "USB Root Hub" (pick one if there are multiple) and select Properties
Each physical USB port or controller has a corresponding Root Hub entry.
Go to the Power Management tab
Click the tab labeled "Power Management".
Uncheck "Allow the computer to turn off this device to save power"
This option controls whether Windows can power-cycle the hub. Leaving it checked can cause intermittent descriptor failures.
Click OK and repeat for all USB Root Hub entries
Do this for every Root Hub if your PC has multiple controllers (USB 2.0, USB 3.0, USB 3.1, etc.).
Restart Windows
Changes take effect on reboot.

USB Root Hubs often get aggressive power-management settings that cut power to unresponsive devices. Disabling this forces constant usb-c-pd" class="vae-glossary-link" data-term="usb-c-pd">power delivery during enumeration, which fixes descriptor timeouts.

Roll Back a Recent Windows Update (if the error started recently) Hard

Open Settings and go to System > About
Note the Windows build number (e.g., 26100.1234).
Go to Settings > System > Recovery
Look for "Go back" option under Recovery if you're on Windows 11.
Click "Go back" and select "Previous version of Windows"
You'll get a list of reasons why you're going back (optional to select).
Follow the prompts to roll back
Windows will revert to the previous build and restart.
Plug in your USB device and test
If the error disappears, the recent update introduced a USB driver bug. You can prevent future updates to that build or wait for a patch.

Warning: Rolling back Windows should be a last resort. It's most useful if the error started immediately after a specific Windows update and affects multiple USB devices. If only one device is affected, the issue is probably with that device, not Windows.

Not sure if your problem is on the advanced side? Test the device on another computer first. If it works fine on a second PC but fails on yours, you've confirmed the problem is software-based, and these advanced driver fixes will likely solve it.

Diagnosing Device-Side Hardware Failure

Sometimes the USB device itself is dead. It might have failed due to a power surge, water damage, physical drop, or just age. If the device fails to enumerate on every computer you try, you're dealing with a hardware problem that no amount of driver updates will fix.

Here's how to confirm: grab a second computer (a friend's laptop, a library computer, anything running Windows or Mac). Plug the same USB device into it. If you get the same descriptor error on a completely different PC with different drivers, different motherboard, different USB controller, the device is almost certainly broken internally. Some devices can be repaired by specialists, but replacement is usually the only practical option.

If the device works fine on the second PC but fails on yours, then you know your first computer has a driver issue, faulty port, or power-management conflict. In that case, the advanced software fixes above should resolve it. You might also consider having a technician scan for malware that could be interfering with USB drivers, though this is rare.

Prevention Tips for USB Device Descriptor Request Failed Errors

Once you've fixed the issue, here's how to avoid it happening again.

Start with the physical layer. Buy decent USB cables. A £2 cable from a discount bin is often where problems begin. They develop internal breaks, poor shielding, and flaky connectors that cause intermittent enumeration failures. If a cable has been yanked, bent sharply, or just used hard for years, bin it and get a new one. Same goes for USB hubs. Cheap unpowered hubs are notorious for causing descriptor errors because they can't supply stable power. If you need a hub, spend a bit more on a powered one with its own adapter.

On the software side, keeping your drivers current matters hugely. Set a calendar reminder to check your motherboard manufacturer's support page every 3, 4 months for new chipset and USB driver versions. Manufacturer updates often include critical enumeration and power-management fixes that generic Windows Update will never push. And once you've got Fast Startup and USB selective suspend dialled in, leave them alone, these settings are a common source of USB problems.

When you do shut down or restart your PC, actually restart it instead of using sleep mode when you've had USB issues. Sleep mode can leave USB devices in a weird intermediate power state where they won't enumerate cleanly on wake. A full shutdown and restart forces every device to start from a clean slate.

Finally, always use Safely Remove Hardware in the system tray before unplugging storage devices. Just yanking out an external drive can corrupt the file system and cause the device to stop responding to descriptor requests. A few seconds to safely eject saves your data and keeps the device healthy.

Info: If you work with multiple high-power USB devices (external drives, video interfaces, powered hubs), consider getting a dedicated powered hub instead of daisy-chaining everything into one PC port. Overloading a single USB controller can cause timing issues during enumeration.

USB Device Descriptor Request Failed: Summary

USB device descriptor request failed errors stop devices cold, but they're fixable in the vast majority of cases. Start simple: try a different port and cable, reinstall the device in Device Manager, and disable Fast Startup and USB selective suspend. If those don't work, update your chipset drivers from the manufacturer and reinstall USB Root Hub controllers. Only about 25% of cases are actually due to dead device hardware, most are software and power-management issues that respond to these fixes. And if you're unsure whether the problem is your computer or the device, test it on another PC. That one test saves hours of troubleshooting. Once you've got it working, keep your drivers current and treat your cables decently, and you'll stay out of this mess.