Establish Which USB Entry Belongs to the Ledger
If Windows Device Manager shows an unknown USB device while Ledger Live cannot connect, identify the entry before changing drivers. The client is currently called Ledger Wallet. An unknown item already present before you connected the Ledger might belong to another peripheral and should not be removed on assumption.
During an ordinary idle session, observe what appears or changes when the intended device is connected. Keep a progressing Ledger OS update’s connection intact; a failed-update state should follow its exact model guide instead of an ordinary unplug test.
Record the Status, Not Just the Yellow Symbol
Open Device Manager, inspect the relevant entry’s Properties and read Device status. Microsoft’s Device Manager error reference explains where Windows reports the code. Keep the description and numeric code together.
A descriptor request failure, Code 43 and a device that appears normally but cannot be opened by the wallet app are different observations. The label Unknown USB Device alone does not prove that the hardware is counterfeit, permanently damaged or missing a downloadable wallet-specific driver.
Compare the Physical Data Path
Use a cable known to carry data and suitable for the actual Ledger model. A lit screen establishes power, not successful USB identification. If a hub or dock is involved, compare a direct host connection when the device is idle.
Try one other appropriate port or data cable at a time. Record whether the unknown entry disappears, changes its error or becomes a normally identified device. Microsoft’s USB-C troubleshooting guidance is relevant to host-port and dock conditions where applicable.
If another supported computer identifies the same Ledger and cable normally, that narrows attention toward the first host. It does not conclusively identify one driver or prove the original computer has a hardware defect. If neither computer identifies it, preserve those observations for support.
Use Supported Driver Handling
Follow the current Windows and Ledger guidance for the exact observed state. Ledger has Windows device-detection guidance that includes a specific update-related context. Match your situation to the article instead of applying every driver procedure to every USB error.
Use Windows Update, the computer manufacturer’s official resources or publisher instructions where a driver action is indicated. Avoid generic driver packs, random INF files and tools that replace every USB interface binding. Uninstalling all USB controllers can also disrupt unrelated input devices and is not a focused first response.
Retest the Wallet App Only After Detection Changes
Once Windows identifies the device appropriately, unlock it on the hardware and follow the task shown by the client. An on-device access confirmation, competing wallet application or incorrect coin-app state can still prevent the next stage.
If My Ledger opens but an account action fails, that is a narrower application workflow than unknown USB enumeration. Keep the successful Windows result in your report so the next investigation does not start by repeating already completed cable checks.
Example: The Wrong Unknown Device Was Blamed
Suppose an unknown USB entry remains present with the Ledger disconnected, while a second entry appears normally when the Ledger is attached. The original unknown item may be unrelated. Tracking the change prevents a wallet connection problem from triggering driver changes to another peripheral.
Device Manager FAQ
Should I install a driver from a search advertisement?
Use the official operating-system, host manufacturer or Ledger instructions for the identified device and condition. A familiar brand in an advertisement does not establish the source of the offered driver.
Does a Windows error require a hardware reset?
Not as routine USB troubleshooting. Resetting wallet keys does not explain or repair the host’s inability to identify a peripheral.
What information is useful to support?
Provide the entry name, status code, Windows version, hardware model and controlled cable or port comparisons. Keep recovery words and private keys out of logs, screenshots and remote-support sessions.