If setup appears paused on a device confirmation screen, read the screen first instead of refreshing every app page. The pause may come from an unread device prompt, a connection condition, a Ledger Wallet page waiting for the device, or an update prompt that belongs to a separate layer.
Read the device confirmation screen first
Check whether the device is unlocked, whether a confirmation prompt is open, and whether the buttons or touchscreen are asking for review. If the device is still inside the initialization sequence, compare it with the first-time initialization flow before changing other conditions.
Separate cable or Bluetooth checks
Connection checks should be handled one at a time. For a desktop setup, review cable, port, and permission state. For a mobile setup, review Bluetooth permission and pairing state. If the app cannot open the device, use the Ledger Wallet device-opening checklist to separate permission and screen prompts.
Use the Ledger Wallet page as context
Ledger Wallet shows which step the app believes is active, but it does not replace the device prompt. If the page appears stuck, check whether it is waiting for the device to be unlocked, an app to be opened, or a confirmation to be completed. For general connection review, use the Ledger connection troubleshooting checklist.
Change one condition at a time
Change only one variable before checking again: one cable, one port, one Bluetooth setting, or one app page refresh. If a firmware or app update prompt appears during setup, keep it separate and read the app-versus-firmware update explanation. A simple step record makes the next attempt easier to understand.
This approach keeps the diagnosis tied to visible device and app states, without turning a paused screen into a broad device concern.
