Unknown USB Device (Device Descriptor Request Failed): how to fix it

Updated Sep 17, 2026

Device Manager shows Unknown USB Device (Device Descriptor Request Failed) under Universal Serial Bus controllers, with the status “Windows has stopped this device because it has reported problems. (Code 43)”. The hardware ID of such a device is typically USB\VID_0000&PID_0002.

This ID is a placeholder: Windows asked the plugged-in device to describe itself (its device descriptor) and got no valid answer, so it does not know what the device is. That means there is no driver to download for VID_0000&PID_0002 — the fix is to make the device communicate correctly, which in most cases is about the cable, the port, power or the USB controller driver.

1. Unplug, wait, plug into another port

Disconnect the device, wait 10 seconds and connect it to a different port. On a desktop use a port on the back panel — those are soldered to the motherboard, while front ports go through an internal cable that is a common source of this error. Avoid unpowered USB hubs and extension cables while troubleshooting.

2. Try a different cable

Many USB cables sold with chargers and power banks are charge-only — they lack the data wires, so the device gets power but cannot talk to the computer. Damaged or very long cables cause the same symptom. Use a short cable that you know transfers data.

3. Fully power off the computer

USB controllers can get stuck in a bad state that a normal restart does not clear.

1. Shut down the computer (hold Shift while clicking Shut down to do a full shutdown).
2. Unplug the power cable. On a laptop also disconnect the charger.
3. Hold the power button for 15–30 seconds, then reconnect power and start the PC.

4. Uninstall the device and scan for hardware changes

1. In Device Manager right-click Unknown USB Device (Device Descriptor Request Failed) → Uninstall device.
2. Unplug the device.
3. Click Action → Scan for hardware changes, then plug the device back in.

5. Disable USB selective suspend

Selective suspend lets Windows cut power to idle USB ports; some devices do not wake up correctly afterwards.

1. Open Control Panel → Power Options (or run powercfg.cpl).
2. Click Change plan settings next to the active plan → Change advanced power settings.
3. Expand USB settings → USB selective suspend setting and set it to Disabled (for both “On battery” and “Plugged in” on laptops).

If “USB settings” is not listed, your power plan hides it — skip this step and continue with the next one.

6. Stop Windows from turning off USB hubs

1. In Device Manager expand Universal Serial Bus controllers.
2. For each USB Root Hub and Generic USB Hub: right-click → Properties → Power Management → clear Allow the computer to turn off this device to save power → OK.

7. Update chipset and USB controller drivers

The USB ports are run by the chipset’s USB host controller (xHCI). An outdated or wrong chipset driver can make every USB device on a port misbehave. Install the chipset driver for your platform — from the laptop or motherboard maker’s support page, or one of these:

Intel platforms:

• Intel Chipset Device Software Driver 10.1.20003.8622 (Nov 5, 2024, Windows 10, 11)
• Intel Chipset Device Software Driver 10.1.19900.8599 (Jul 20, 2024, Windows 10, 11)
• Intel Chipset Device Software Driver 10.1.19913.8607 (Jul 9, 2024, Windows 10, 11)

AMD Ryzen platforms:

• AMD Ryzen™ Chipset Driver 7.02.13.148 (Feb 26, 2025, Windows 10, 11)
• AMD Ryzen™ Chipset Driver 7.01.08.129 (Jan 14, 2025, Windows 10, 11)
• AMD Ryzen™ Chipset Driver 6.10.22.027 (Oct 23, 2024, Windows 10, 11)

Also browse the USB drivers and chipset drivers sections if you have an add-on USB card (for example ASMedia, VIA or Renesas controllers).

8. Turn off Fast Startup

Fast Startup restores part of the previous session on boot, including the state of USB controllers.

1. Open Control Panel → Power Options → Choose what the power buttons do.
2. Click Change settings that are currently unavailable.
3. Clear Turn on fast startup (recommended) and click Save changes, then shut down and start the PC again.

9. Test the device on another computer

If the same error appears on a second computer with a known-good cable, the device itself is faulty (damaged connector, dead controller or corrupted firmware). Flash drives and external disks with this symptom often have a failing controller — if the data matters, stop retrying and contact a data recovery service.

When the device is recognised but still has no driver

Once Windows reads the descriptor, the device appears with its real hardware ID, such as USB\VID_1A86&PID_7523. At that point copy the hardware ID and search for it. Popular USB devices that need a separate driver:

Related guides

• Find your hardware ID
• Code 43: device reported problems
• Code 10: this device cannot start
• SM Bus Controller driver
• PCI Simple Communications Controller
• PCI Data Acquisition and Signal Processing Controller
• Base System Device driver
• PCI Device driver missing