Windows 11 passkey bug cries failure after successful sign-in
Optional update fixes misleading Android error for versions 25H2 and 26H2
A Windows 11 passkey bug can leave Android phones announcing that authentication failed even when it succeeded. Microsoft has now released a fix for versions 25H2 and 26H2.
The problem occurs when users sign in on a Windows 11 PC using a passkey stored on an Android phone. Scan the QR code, and the Android device might display the message: "Something went wrong. Restart the process on your other device and try again."
Except it might not have gone wrong at all. Microsoft's guidance explains: "In cases where authentication completes successfully on the Windows device, the error message on the Android device is not supposed to appear and can be safely ignored."
REG AD
Cross-device authentication lets users sign in on one device using a passkey held on another, without typing a password or copying a verification code. Microsoft says the issue affects operations using Microsoft Authenticator and Google Password Manager, and can occur in Edge or Chrome – not just when signing in through Microsoft Entra ID.
REG AD
Cross-device passkey operations with an iPhone aren't affected.
An authentication system that cries failure after a successful sign-in isn't doing much for user confidence. Nor will it endear itself to support teams fielding the resulting tickets.
Microsoft has included a fix in KB5132057, the optional non-security preview update released on November 19 for Windows 11 25H2 and 26H2. Until affected devices are patched, users can ignore the Android error if authentication has completed successfully on the PC. ®
KioskNews shows a cleaned-up reading view extracted from the publisher’s page — the original always lives on their site, not ours.