Computer technician providing live USB troubleshooting help

Joe B.

Reviewed for technical accuracy

Specialities: Windows 11/10, USB devices, Drivers & Chipsets, macOS, Networking

Fix Unknown USB Device (Device Descriptor Request Failed / Port Reset Failed) — Windows 10/Windows 11

Technician avatar Technician
Hey! Let’s fix the Unknown USB Device error. I’ll help you roll back or repair the driver and clean the DriverStore so Windows stops re‑installing the broken package. Tell me: which device fails (printer, USB flash, camera, headset, hub), what the exact message shows in Device Manager (e.g., Device Descriptor Request Failed, Port Reset Failed, USB\\DEVICE_DESCRIPTOR_FAILURE), and if this started after a driver rollback or Windows Update.
Customer
Windows 11. After rolling back a USB printer driver, it now shows Unknown USB Device (Device Descriptor Request Failed). Rebooting and changing ports didn’t help.
Technician avatar Technician
Got it. After a rollback, Windows may keep a corrupted or incompatible INF in the DriverStore and auto‑bind it on every plug‑in. That causes the Unknown USB device entry under Universal Serial Bus controllers with Code 43 or Code 10. Other triggers: stale USB Root Hub/Generic USB Hub drivers, out‑of‑date Intel/AMD USB 3.x controller or chipset package, USB selective suspend power policies, Fast Startup, or a damaged cable/hub. We’ll purge the bad oem*.inf files with pnputil, refresh hubs/controllers, and install the correct vendor driver.
Customer
Okay. How do we fully clean DriverStore without breaking other USB devices?
Technician avatar Technician
Safe DriverStore cleanup (Windows 10/11):
1) Unplug the faulty USB device and any non‑essential USB hubs.
2) Open an elevated PowerShell or CMD.
3) List third‑party drivers: pnputil /enum-drivers | findstr /i "usb print usbxhci usbhub oem inf". Note suspect oemXX.inf tied to the device vendor (HP/Epson/Canon/Brother) or the wrong class.
4) Remove them cleanly: pnputil /delete-driver oemXX.inf /uninstall /force (repeat for each bad INF). This clears the DriverStore so Windows can’t reattach the broken package.
5) In Device Manager → Universal Serial Bus controllers: right‑click Unknown USB Device → Uninstall device → check Delete the driver software for this device.
6) Still in Device Manager, uninstall and Delete driver software for USB Root Hub (USB 3.0), Generic USB Hub, and the USB xHCI Host Controller (they will reload on reboot).
7) Reboot (full cold boot). Then install the latest chipset/USB controller from your motherboard or laptop vendor (Intel/AMD) before plugging the device.
Customer
I don’t see which oemXX.inf maps to the printer. Any hints?
Technician avatar Technician
Find the right INF:
• In Device Manager → the device’s Details tab → Hardware Ids; look for USB\\VID_####&PID_####. Use pnputil /enum-drivers and match the Published Name and Original Name to the vendor (e.g., hpv***.inf, prnhp***.inf, oem*.inf).
• Open %windir%\inf\setupapi.dev.log and search the VID/PID to see which INF bound last.
• If unsure, remove only the vendor’s printer USB INF(s) and leave Microsoft inbox drivers (e.g., usbhub3.inf, usbxhci.inf) intact.
Customer
What about power settings like USB selective suspend or Fast Startup?
Technician avatar Technician
Stabilize USB power:
• Control Panel → Power Options → Change plan → USB settings → USB selective suspend = Disabled (for testing).
• In Device Manager, USB Root Hub/Generic USB Hub → Power Management tab → uncheck Allow the computer to turn off this device to save power.
• Disable Fast Startup (Control Panel → Power → Choose what the power buttons do). Fast Startup can keep a bad USB state cached.
Customer
Do I need SFC/DISM in case system USB drivers are corrupted?
Technician avatar Technician
Repair Windows USB stack:
1) Open an elevated CMD and run: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
2) Reboot and confirm usbxhci.sys and usbhub.sys load without errors in Event Viewer → Windows Logs → System (look for Kernel-PnP 411/442).
3) If the issue persists across ports, try a short, known‑good cable or a powered USB 2.0 hub to rule out brown‑outs on USB 3.x.
Customer
After the cleanup, Windows keeps reinstalling a generic class driver. How do I stop that?
Technician avatar Technician
Prevent re‑attachment to the bad package:
• Immediately install the vendor’s latest USB/Printer driver or chipset package before plugging the device.
• Optional: Control Panel → System → Advanced system settings → Device Installation Settings → No (don’t auto‑download manufacturer apps). In managed setups, use Group Policy → Prevent installation of devices using drivers that match these device setup classes to block the bad class temporarily.
Customer
Could a BIOS or firmware update help? It’s a USB 3.2 laptop.
Technician avatar Technician
Yes — if the USB controller firmware is buggy, some devices fail enumeration with Port Reset Failed. Update BIOS/UEFI and install the latest Intel/AMD chipset & USB controller package from your OEM. For docking stations and printers, also check device firmware/EEPROM updates.
Customer
Any quick test to confirm it’s not the port or cable?
Technician avatar Technician
Try these quick checks:
• Test on a different PC — if it enumerates there, your Windows stack/DriverStore was the issue.
• Use a short certified cable; avoid front‑panel headers. Try a powered hub (stabilizes 5V).
• In Device Manager, enable View → Show hidden devices and remove greyed‑out entries for the same VID/PID (ghost devices) before reinstalling.
Customer
Great — the printer is now recognized and installs correctly. Thanks!
Technician avatar Technician
Summary: If you see Unknown USB Device (Device Descriptor Request Failed/Port Reset Failed) after a driver rollback, purge the bad INFs from DriverStore with pnputil, remove the device and USB hubs/controllers in Device Manager, install the latest chipset/USB controller and vendor device drivers, and stabilize power (disable selective suspend/Fast Startup). Need hands‑on help? Open the chat.

Quick answer: the accepted fix

Accepted fix when Unknown USB Device appears on Windows 10/11 after a driver rollback: clean the DriverStore (remove bad oem*.inf with pnputil), uninstall the Unknown USB Device and USB Root Hub/Generic USB Hub/xHCI Controller entries, reboot, then install the latest chipset/USB controller and the correct vendor driver. Finally, adjust USB selective suspend and Fast Startup to prevent reoccurrence.


“Device Descriptor Request Failed” after Windows Update or driver rollback

Windows can preserve an incompatible package in the DriverStore and bind it repeatedly. Use pnputil /enum-drivers to identify vendor INFs and remove them with /delete-driver oemXX.inf /uninstall /force, then reinstall the proper USB class/Printer driver. Check setupapi.dev.log and Event Viewer → Kernel‑PnP for binding errors and Port Reset Failed messages.

How to verify the USB device enumerates correctly

Plug the device after installing chipset drivers. In Device Manager, it should appear under the correct category without warning icons. The device’s properties should show a matching VID/PID, valid Driver Provider, and a recent Driver Date. If it still becomes Unknown, try a different port, cable, or a powered hub to rule out power issues.

USB enumeration — troubleshooting tips

Most “Unknown USB device” errors come from a bad INF in the DriverStore or outdated chipset drivers.

Quick path: identify VID/PID → clean DriverStore with pnputil → refresh hubs/controllers → install latest Intel/AMD chipset & USB → stabilize power (disable USB selective suspend/Fast Startup) → test with a known‑good cable. If the error persists across PCs, consider device firmware or hardware failure.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive consults. Membership can save you significant time and money each month.

FAQ

What triggers “Unknown USB Device (Device Descriptor Request Failed)”?

Usually a corrupted or incompatible driver left in the DriverStore after a rollback or Windows Update. Other causes: outdated USB Root Hub/xHCI drivers, aggressive power savings (USB selective suspend, Fast Startup), bad cables/ports, or missing chipset drivers.

How do I clean the DriverStore safely?

Unplug the device → run pnputil /enum-drivers to find vendor INFs → remove them with /delete-driver oemXX.inf /uninstall /force → uninstall Unknown USB Device and hubs/controllers in Device Manager → reboot → install latest chipset/USB and vendor drivers.

Can I stop Windows from reinstalling the wrong class driver?

Yes. Install the correct vendor/chipset package immediately after cleanup. Optionally set Device Installation Settings to not auto‑download, or apply Group Policy to block that device class temporarily.

Does this apply to printers, scanners, and docks?

Yes. The same Unknown USB device pattern affects USB printers, scanners, audio interfaces, webcams, and docking stations. Cleaning the DriverStore and updating chipset/USB controller drivers fixes most cases.

What if errors persist on every PC?

Suspect device firmware or hardware failure. Update printer/dock firmware, try a different cable/power supply, and test through a powered USB 2.0 hub. If it still fails, the device may need service.

Common Unknown USB Device problems and quick fixes
SymptomLikely causeQuick fix
Unknown USB Device (Device Descriptor Request Failed) Corrupt vendor INF in DriverStore Remove with pnputil; reinstall vendor & chipset drivers
Unknown USB Device (Port Reset Failed) Power instability / outdated USB controller Disable selective suspend; update chipset/USB; use powered hub
Device reconnect loops Fast Startup caching bad state Disable Fast Startup; cold boot; clean DriverStore
Works on other PC only Broken Windows USB stack DISM + SFC; refresh hubs/xHCI; reinstall vendor driver

Step‑by‑step (Windows 10/11)

  1. Unplug the faulty USB device and non‑essential hubs.
  2. Open elevated CMD/PowerShell and run pnputil /enum-drivers → find vendor oemXX.inf; remove with pnputil /delete-driver oemXX.inf /uninstall /force.
  3. Device Manager → Universal Serial Bus controllers → uninstall Unknown USB Device (check Delete the driver software).
  4. Uninstall USB Root Hub, Generic USB Hub, and USB xHCI Host Controller (they reload on reboot).
  5. Reboot (full shutdown + power on). Install latest chipset/USB controller from your OEM (Intel/AMD) and the correct device driver (printer/scanner/dock).
  6. Disable USB selective suspend and Fast Startup for stability; re‑test with a known‑good cable.

Step‑by‑step (macOS)

  1. macOS rarely shows this exact error text, but similar symptoms (device not recognized) can appear.
  2. Reset USB bus: shut down Mac, unplug all USB devices, wait 60 seconds, then boot and connect the device directly (no hubs).
  3. Install the latest vendor driver (if required) or use class‑compliant mode. Update macOS.
  4. If only Windows fails via Boot Camp/VM, follow the Windows steps above inside that environment.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant