Windows Detection and Wallet Access Are Different Stages
When Windows detects your Ledger but Ledger Live cannot connect, keep the successful detection result and investigate the next layer. A Device Manager entry shows that Windows has identified a USB interface; it does not prove the client can complete its requested exchange. The current application name is Ledger Wallet.
First record the exact client action: opening My Ledger, adding an account, checking an address or signing a transaction. Those tasks can request different hardware states. A generic connection failure description loses the distinction that can point to the actual cause.
Confirm That Windows Detection Is Healthy
Inspect the relevant entry’s status rather than relying only on the USB connection sound. If Windows reports an unknown device or error code, handle that detection problem first. Microsoft’s USB troubleshooting guidance covers relevant host connection conditions.
If the entry appears normally and stays present, avoid repeatedly reinstalling every USB driver. Keep the known-good cable and port while investigating the client stage, so new physical changes do not obscure the original observation.
Read the Device Screen Alongside the Client
Locked Hardware
Unlock the Ledger through its physical controls. A visible device entry in Windows does not mean the wallet is unlocked. Never type the hardware PIN into a web form or unofficial Windows prompt to unlock USB access.
Management Access Needed
If the client requests permission for My Ledger, look for the corresponding confirmation on the device. Confirm the expected action there. An Allow accessories prompt on a host operating system and an Allow My Ledger prompt are different kinds of access.
Wrong App or Dashboard State
Follow the current task’s on-screen instruction about the device dashboard or relevant coin app. Opening a coin app too early for management, or leaving the wrong app open for an account action, can produce a different failure from missing USB detection.
Close Competing Device Sessions
When no critical operation is underway, close other wallet apps or browser sessions that may be communicating with the device. Ledger’s third-party connection guidance illustrates that companion applications can conflict during device access.
Return to one intended client session and retry the connection action once. Keep a progressing device OS update running under its documented procedure; do not terminate the host or unplug the Ledger as a routine competing-process test during that operation.
Separate Local Access from Online Service Failure
If the device is detected and unlocked but management fails with a network or WebSocket message, record that exact error. The physical USB path and an online management connection are different dependencies. Check the relevant component on Ledger’s status page when the message concerns a service.
A company network, VPN or certificate issue deserves its own investigation. Do not disable all security controls or install an unknown certificate to make a management request succeed. Use an approved network comparison and current official guidance.
Example: My Ledger Works, One Account Does Not
If management opens and displays the device but one asset-specific operation fails, the evidence points toward that narrower workflow. Check the selected network, requested coin app and exact error instead of describing the whole Ledger as undetected.
Conversely, if every operation stops at unlocking, verify the actual device state and whether another client owns the connection. The same Windows detection result can coexist with several different app-level failures.
Detected-but-Not-Connected FAQ
Should I reset application data first?
Start with the operation, hardware screen and competing-session checks. A broad data reset can remove local account entries without explaining access to a detected USB device.
Can Bluetooth fix the standalone Windows connection?
Use the transport supported by the chosen desktop edition. Mobile wireless support does not establish that a Bluetooth route is available in the standalone Windows client.
What should my support report include?
State that Windows identifies the device, then provide its status, the client version, hardware model and failing action. Include the exact error while removing recovery words, account-sensitive screenshots and other unnecessary private details.