When a first verification prompt does not match the expected state, the safest workflow is simple: pause, record what is visible, reopen the fixed app entry, and compare the states again. This article does not treat a prompt mismatch as a channel judgment or a device conclusion. It keeps the response limited to evidence, entry, device screen, and next-step clarity.
Pause before changing the condition
Do not keep clicking through a prompt that cannot be matched to the expected task. Leave the device and app state as they are long enough to record the visible information. If the broader arrival check is still unfinished, review What to Check When Unboxing and keep package, screen, and app observations separate.
Record the prompt without private material
The useful record is limited: device model, app entry, screen wording, time, and the step that led to the prompt. Do not include PIN details or recovery phrase words. For the device-screen and first-setup boundary, What Is Ledger Initialization helps separate first setup from later review actions.
Reopen the fixed app entry
Close unrelated pages and return to the known Ledger Wallet entry. Confirm the app name and the task before reconnecting the device. If the app source needs a separate check, use Ledger Wallet Download and Installation Guide rather than following a link from a message or a screenshot.
Decide the next step from matched states
If the second check matches the expected device and app state, continue with the planned setup path. If it still does not match, keep the same record and move to the fixed support or service entry with only non-private information. The record should show what was seen and when it was seen; it should not expand into guesses or broad claims.
