Ledger Genuine Check works best when it is placed in the right sequence. First open Ledger Wallet from a fixed source, then connect the device, then read the app state and the Ledger device screen together. The result should be recorded as part of the authenticity workflow, not treated as a separate shortcut.
Begin with the Ledger Wallet source
The check should start from Ledger Wallet opened through a known path. If the task begins from a browser page or a download step, return to a fixed app source before connecting the device. This keeps the app state, device model, and screen prompt in the same workflow.
For installation and app-entry order, use the Ledger Wallet download guide. That article separates platform choice, app source, and first connection before the device check begins.
Genuine Check depends on the device response
Genuine Check is not just a label on a page. It relies on communication between Ledger Wallet and the connected device. For the user, the practical habit is to confirm that the device you connected is the device being checked and that the screen state matches the task you started.
The technical background is easier to understand through the Secure Element overview. The Secure Element gives context for why an app-side check and a device-side response belong together.
Read app state and device screen together
When the app reports a device state, also read the device screen. If the app, cable, platform, or device state changes during the check, record that condition instead of repeatedly retrying without notes. A clean check has a fixed source, a known device, a visible app state, and a device screen that matches the step.
Keep the result inside the authenticity record
The Genuine Check result should be recorded with source path, device model, app state, device-screen state, and next step. For the wider sequence, connect it with Ledger authenticity checking. Do not include recovery words, PIN details, or private backup photos in the record.
