[Windows 11] Lenovo IdeaPad 1 15ALC7 — STM32 CDC device alternates between “Device Descriptor Request Failed” and usbser Code 10, works fine on desktop PC

Post

The device in question is a drone flight controller, but for USB purposes it’s just a generic STM32 CDC virtual COM port device (USB\\VID\_0483&PID\_5740). It should enumerate as a plain USB Serial Device and use Microsoft’s inbox usbser.sys. Nothing exotic. It works perfectly on my desktop PC with the same cable. On this laptop it will not start. SYSTEM Lenovo IdeaPad 1 15ALC7, Windows 11 Home USB controllers: 2x AMD USB 3.10 eXtensible Host Controller (Microsoft driver), 2x USB Root Hub (USB 3.0). No dedicated USB 2.0 / EHCI controller exists on this machine Device: STM32 CDC ACM, VID\_0483&PID\_5740 SYMPTOM It alternates between two states across reconnects and reboots: 1. Unknown USB Device (Device Descriptor Request Failed) — fails to enumerate at all 2. USB Serial Device (COM3), Manufacturer: Microsoft, with “This device cannot start. (Code 10)” and “{Operation Failed} The requested operation was unsuccessful.” Same cable and same device enumerate instantly and work on a desktop PC. WHAT I’VE ALREADY DONE Driver layer: • Removed leftover STMicroelectronics VCP drivers via pnputil /delete-driver oemXX.inf /uninstall /force (five entries) • Confirmed the device now binds to Microsoft’s native usbser.sys, not a third-party VCP driver • Device Events tab shows “Driver service added (usbser)” with status: 0 — the driver installs successfully, it just won’t start • Events also repeatedly show “Device settings not migrated” • Uninstalled the device with “delete driver software” checked, rescanned, reconnected — same result Registry: • Checked HKLM\\SYSTEM\\CurrentControlSet\\Control\\Class{4D36E978-E325-11CE-BFC1-08002BE10318} — no UpperFilters or LowerFilters present • Cleared ComDB in Control\\COM Name Arbiter • Removed six “Standard Serial over Bluetooth link” COM ports that were holding low port numbers • Tried reassigning to COM20/COM21 via Advanced Port Settings — Windows creates a fresh device instance on reconnect and grabs a low number again • Attempted to delete HKLM\\SYSTEM\\CurrentControlSet\\Enum\\USB\\VID\_0483&PID\_5740 — blocked, SYSTEM-owned key USB stack / power: • Uninstalled and let Windows reinstall all host controllers and root hubs • sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth — both completed • Fast Startup disabled, full shutdown + 30s power drain with charger unplugged • USB selective suspend disabled on battery and plugged in • Power management “allow the computer to turn off this device” unchecked on all hubs OEM / firmware: • Installed AMD IO Driver from Lenovo support. This helped — before it, the device only ever showed as Device Descriptor Request Failed; after it, it at least enumerates as USB Serial Device. Code 10 persists • Lenovo does not publish a separate chipset or xHCI driver for this model, so there’s nothing to replace on the host controller side • BIOS: disabled Always On USB and Charge In Battery Mode. No USB Legacy Support or xHCI hand-off options exist in this BIOS Ruled out: • Cable — works on desktop • Device — works on desktop • Physical port — a USB mouse works in the exact same port • Power draw during enumeration — tested with the device externally powered as well, no change NOT YET TRIED • Inserting a cheap USB 2.0 hub between device and laptop (transaction translator theory) — don’t have one on hand • BIOS update from Lenovo QUESTION Given that usbser reports a successful install (status 0) but the device still can’t start, and there are no class filters and no COM conflicts left, what else can cause Code 10 at this stage? Is this a known incompatibility between AMD-only xHCI controllers and USB 2.0 full-speed CDC devices, and is the USB 2.0 hub the realistic fix? Or is there something in the enumeration path I haven’t checked? Happy to post Device Manager and Events screenshots, or run any diagnostic (USBView, xperf USB trace, etc.) if that helps. Thanks, sorry for bad format, first time writing this long and i’m a little frustrated.

This signal has not been scored yet.