How To Fix Win11 “USB Device Descriptor Request Failed (Code 43)” Error

USB Device Descriptor Request Failed (Code 43)

You’re running into the classic USB Device Descriptor Request Failed (Code 43) problem, and you’ve already tried the usual suspects like uninstall/reinstall, different USB ports, registry tweaks, etc.

The “device descriptor” is essentially the device’s ID card, and when Windows can’t read it, it throws this error.

The Problem: 0x2B code in Device Manager usually points to the device not responding correctly to Windows’ initial handshake.

The Error

Device USB\VID_0000&PID_0002\5&1d94a37c&0&1 had a problem starting.

Windows Device Manager

USB Device Descriptor Request Failed (Code 43)

Let’s go a bit deeper with some advanced troubleshooting steps, because this can be:

  • Driver-level (Windows USB stack),
  • Firmware-level (the drive itself), or
  • Hardware-level (port or cable issue).

Here’s what I recommend in order:

1. Test on Another PC or OS

  • Why: This instantly tells you if the issue is with Windows or the drive.
  • Do this first: Plug the ASUS drive into a Windows 10 or even a Linux live USB system.
  • If it works elsewhere → Windows 11 is the culprit.
  • If it fails everywhere → The drive or cable may be dead.

2. Try a Powered USB Hub or Different Cable

  • External CD/DVD drives sometimes pull more power than standard USB ports give, especially on laptops.
  • If you’re using a USB-C adapter, try a direct USB-A 3.0 port.
  • Swap the cable if possible—many external drives use standard Micro-B or USB-A cables.

3. Reset Windows USB Controllers

  • Open Device Manager → Universal Serial Bus Controllers.
  • Right-click every entry under there → Uninstall device (don’t uninstall keyboard/mouse if they’re USB).
  • Restart Windows. It will reinstall fresh USB stack drivers.

4. Registry Fix for DVD Recognition

  • Open Registry Editor ( win + R, type regedit ).
  • Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi
  • Right-click atapi -> New > Key -> Name it Controller0
  • Inside Controller0 , right-click -> New -> DWORD (32-bit) Value -> Name it
    EnumDevice1
  • Set its value to 1 .
  • Restart your PC.

5. Check for Hidden/Corrupted Devices

  • Open Device Manager → View → Show hidden devices.
  • Under “Universal Serial Bus controllers,” delete any grayed-out or “Unknown” devices.
  • Reboot.

6. BIOS & Chipset Driver Updates

  • If Windows 11 was a clean install, the chipset drivers or USB controller firmware might be outdated.
  • Visit your motherboard/laptop vendor site → Install the latest BIOS and chipset drivers.
  • Reboot after each update.

7. Registry Fix for USB Ports (Deep Reset)

If nothing works, you can reset the entire USB controller configuration:

  1. Run regedit.
  2. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\USB
  1. If there’s a key named DisableSelectiveSuspend, set it to 1 (DWORD). If it doesn’t exist, create it.
  2. Reboot.

8. Try ASUS’s Own Drivers or Firmware (if available)

Sometimes the drive firmware itself needs an update.

  • Search for your ASUS drive model + “firmware update” or “Windows 11 driver” on ASUS’s support site.

9. Last Resort: Clean Boot or Live USB Test

  • Boot into Safe Mode with Networking or a Windows 11 PE USB.
  • If the drive works there → a third-party driver/service in normal Windows is messing things up.

10. The Final Fix that Worked

After test#1, the ASUS external slim drive worked on a laptop, also sporting Windows 11, without issues.

I loaded my old CD burning software (CDBurnerXP: a light-weight burning program that I have been using for decades now.

Within a couple of minutes, the error was back.

I uninstalled the CD burner program, cleaned the registry, restarted Windows and the external drive is working again.

Uninstalled the CD burning software from the desktop, cleaned the registry, restarted, and the external drive has been working ever since.

Turns out the culprit was CDBurnerXP. At least for my external drive.

Fix #10:

Uninstall CD Burner XP, clean the registry and restart.

Similar Posts