Security News

Windows 11 Passkey Bug Shows a False 'Failed' Message on Android Even When Sign-In Works

The Register · 20 Nov 2026
Key Takeaway If staff use Android phones to sign in to Windows 11 PCs with passkeys, tell them the error can be ignored when the PC sign-in succeeds, and plan to apply the optional update.

Microsoft has confirmed a Windows 11 bug that can make an Android phone report a failed sign-in when the sign-in actually worked. The problem appears when someone signs in on a Windows 11 PC using a passkey stored on their Android phone.

The user scans a QR code on the PC, and the phone may then display the message: "Something went wrong. Restart the process on your other device and try again." According to Microsoft's guidance, if authentication completes successfully on the Windows device, the error is not supposed to appear and can be safely ignored.

Cross-device authentication lets people 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. It can occur in Edge or Chrome, and not only when signing in through Microsoft Entra ID. Cross-device passkey operations with an iPhone are not affected.

Microsoft has included a fix in KB5132057, an optional non-security preview update released on November 19 for Windows 11 versions 25H2 and 26H2. Until affected devices are patched, users can ignore the Android error as long as the sign-in has completed on the PC.

The bug does not appear to be a security flaw, but a misleading failure message can still erode trust in a sign-in method and generate extra support requests.

Why it matters

Passkey rollouts depend on users trusting the new sign-in flow, and a false failure message can push staff back to weaker fallbacks or flood the help desk. Businesses running Windows 11 25H2 or 26H2 with Android-held passkeys are exposed to this confusion. It also forces a decision on whether to deploy an optional preview update or simply brief users to ignore the message.

What to do

  • Tell staff that the Android error can be ignored if sign-in completes on the Windows PC.
  • Test KB5132057 on Windows 11 25H2 and 26H2 devices before wider rollout.
  • Check whether users sign in with passkeys through Microsoft Authenticator or Google Password Manager in Edge or Chrome.

Summarised by CISO AI from The Register, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.