Know What You Will Change Before Starting

A Ledger Live desktop update changes the client installed on the computer. Ledger calls that client Ledger Wallet now. Ledger OS and the blockchain apps on your signer are separate maintenance targets, so a useful plan names the component rather than calling every notification a wallet update.

Make a short record of the current client version and how you launched it. Also note any unresolved provider order or transaction already approved. Those references remain useful if the application restarts before displaying the final status of an earlier action.

Choose a Session That Can Finish Normally

Do not begin host replacement while the computer is supporting a progressing Ledger OS installation. Finish that hardware task through its proper flow first. For ordinary app maintenance, arrange stable power, adequate storage, and time to complete installation and a verification launch.

Consult Ledger’s application-update explanation for why supported clients matter. Keep the release comparison tied to your edition and platform; a mobile store number is not a desktop version requirement.

Select the Update Route by the Client’s Condition

If the built-in updater works, read its download and installation prompts and complete one attempt. Watch for a hidden operating system consent dialog or another running copy. Multiple repeated clicks create ambiguity about what is actually installing.

If that route fails, use the supported platform package from Ledger’s own download page. Manual client replacement can be appropriate without deleting the local account profile. Treat a full reset as a separate decision with different data consequences.

Make the Destination Explicit

A Fixed Installed Location

Confirm the installer replaced the destination you intend to use. On macOS, the copy inside a downloaded image can differ from Applications. On Windows, a shortcut can reference another location or user context.

An AppImage Target

For Linux, identify the actual verified AppImage your launcher starts. A new file saved beside an old one does not necessarily change that launcher. Resolve the intended filename and target deliberately after the supported replacement.

Another User Profile

Different operating system users can have distinct local settings. Check whether the updated binary and the profile you expected are the ones opening, instead of treating a changed account view as proof that keys changed.

Prove the Result and Resume the Original Task

Launch one intended copy and inspect its version. Check that necessary account entries are present or can be rediscovered using the initialized device. Let a public-history refresh complete, then compare an actual asset quantity rather than only a price chart.

If another message requests Ledger OS or a coin-app update, follow that component’s supported instructions. A successful desktop replacement does not establish that all dependencies required by a particular asset are current.

Update FAQ

Must I reconnect from the recovery phrase afterward?

Not when the device is already initialized and working. Ordinary host updates do not require entering its backup into software or generating a new wallet.

What if the app reopens with the same notification?

Compare the installed version, launch target, and exact updater result. These observations distinguish an old copy from a replacement that never completed or a specific release issue.

Can I repeat an earlier payment after the restart?

Inspect its blockchain or provider reference first. The desktop app restarting does not cancel an operation another system already received, and a second payment can be a separate transaction.