This usually happens because the passkey on the device is no longer valid, the sign-in session timed out during cross-device verification, or the device setup for passkeys is incomplete.
Common causes:
- Cross-device passkey sign-in depends on Bluetooth and internet on both devices. If the passkey is on the phone and sign-in is being completed from the PC, both devices must have Bluetooth enabled, be nearby, and be connected to the internet. If that check fails, Windows can fall back to asking to use the phone again.
- The passkey may no longer be valid on that device. This can happen if the passkey was deleted from the account or device, or if the phone authentication method changed, such as a new PIN or biometric setup. In that case, a new passkey must be created and old ones removed.
- Only one passkey per site/service is supported in many credential managers. Trying to add the same passkey again can cause "Something went wrong" behavior instead of improving sign-in.
- If the device screen lock is disabled, synced passkeys may not appear. Passkeys require face, fingerprint, or PIN authentication on the device.
- On Windows 11 version 24H2 and later, passkey access can be blocked per app. If passkey privacy consent was declined for the app being used, passkey registration and authentication will not work until access is re-enabled in Settings > Privacy & security > Passkey access.
What to do:
- On the phone and PC, make sure Bluetooth is on, both devices are near each other, and both have internet access.
- On the phone, confirm that screen lock is enabled with PIN, fingerprint, or face unlock.
- If Windows 11 is version 24H2 or later, open Settings > Privacy & security > Passkey access and allow passkey access for the affected app.
- If the message says the passkey can no longer be used, set up a new passkey first, then remove old passkeys that no longer apply.
- If the issue started after changing the phone PIN, biometrics, or moving to a new device, recreate the passkey.
- If using a new PC or phone, set up the passkey again on the new device, then delete the old one after the new setup works.
If the sign-in prompt is specifically showing a QR code and requiring the phone camera or photo-related flow each time, that indicates cross-device authentication is being used instead of a passkey stored locally on the Windows device. A locally saved passkey on Windows can avoid needing the phone for each sign-in.
References: