This is not a security hole, and nobody is getting into accounts they shouldn't. The bug is a false failure message: the sign-in works, but the phone says it didn't. That's still annoying for anyone who has spent years teaching users to take security warnings seriously.
What's actually going wrong
The problem appears in cross-device authentication. You sign in on a Windows 11 PC using a passkey stored on your Android phone. The PC shows a QR code, you scan it with the phone, and you approve the sign-in there.
According to The Register, the Android phone may then show: "Something went wrong. Restart the process on your other device and try again." The Register quotes Microsoft's guidance as saying that when authentication completes on the Windows device, the Android message "is not supposed to appear and can be safely ignored."
The Register also reports these limits on the bug, citing Microsoft:
- It affects passkeys held in Microsoft Authenticator and Google Password Manager.
- It can happen in Microsoft Edge or Google Chrome.
- It isn't limited to sign-ins with Microsoft Entra ID.
- Cross-device sign-ins using an iPhone are not affected.
These details come from The Register's reporting. Microsoft's own release note for the fix is short. "This update fixes an issue that caused cross-device passkey authentication on Android devices to display a 'Something went wrong' error." That confirms the bug and the fix. It does not list affected providers or browsers.
Neowin quotes a slightly different version of the note, which says the update "improves cross-device passkey registration and sign-in using Android devices, helping the process complete without displaying an incorrect 'Something went wrong' message on your phone." If that wording is right, the fix may also cover passkey registration (creating a passkey on the phone for use on the PC), not just sign-in. The main support-page text available for this report mentions only authentication, so treat registration as a possible extra rather than a confirmed detail.
Summary: The phone reports a failure but the PC signs in successfully. Android only. iPhones are not affected, according to The Register.
Why a fake failure is still a real problem
Cross-device passkeys depend on users trusting what they see. Microsoft's documentation describes the process as using a passkey stored on one device to sign in on another through a QR code shown on the device you're signing in to. A proximity check makes sure the passkey is only used on a nearby device.
Microsoft's Windows passkey documentation also says that for cross-device sign-in, both the Windows PC and the phone need Bluetooth turned on and an internet connection. That lets the phone approve the sign-in without copying the passkey to the PC.
So what happens when the phone says the sign-in failed? Some users will:
- Scan the QR code again, even though they're already signed in.
- Decide passkeys are unreliable and go back to passwords.
- Contact the help desk.
- Turn off Bluetooth or try other "fixes" for a problem that doesn't exist.
None of those helps a passwordless rollout. The Register put it simply: an authentication system that reports failure after a successful sign-in won't build user confidence or win over support teams. No source puts a number on how many people hit this bug. It's clear, though, that a red error after a working sign-in teaches users the wrong lesson.
Summary: No security risk, but a real cost in user trust and help-desk time.
Which update fixes it, and which builds
The fix is in KB5132057, released November 19, 2026. Microsoft's support page lists it as a preview update for Windows 11 versions 26H2 and 25H2, all editions:
| Windows 11 version | Build after KB5132057 |
|---|---|
| 26H2 | 26300.10075 |
| 25H2 | 26200.10075 |
The same KB number appeared earlier in the Release Preview channel for Windows Insiders, with different build numbers. Those release notes cover Windows 11 Builds 26200.10066 and 26300.10066 (KB5132057) in the Release Preview channel on Windows 11, versions 25H2 (Build 26200) and 26H2 (Build 26300), all editions. The .10066 builds were the Insider preview. The .10075 builds are the optional update for regular PCs.
Microsoft lists the passkey fix in the update's "normal rollout" section, not the gradual rollout of new features. In Microsoft's wording, normal rollout means the broad release to all eligible devices at once. Gradual rollout means features reach devices in phases.
How to install it
KB5132057 is an optional, non-security update, so it won't install automatically. To get it now:
- Open Settings > Windows Update > Advanced options > Optional updates.
- Install KB5132057 if it's offered, then restart. Install KB5132057 if it is offered, then restart.
- Check your build by running winver. On 25H2, winver should show 26200.10075. On 26H2, it should show 26300.10075.
If you install it manually or through WSUS, Microsoft lists these prerequisites:
- Windows 11 25H2 must already have an update released on or after June 10, 2025, such as KB5060842.
- The latest servicing stack update must be installed. KB5132057 includes servicing stack update KB5132056.
- The Microsoft Update Catalog may also require checkpoint cumulative updates, installed in order before the target update.
Not ready for a preview update?
Many organisations don't deploy optional preview updates in production. Microsoft says the changes will be included in the next security update for Windows Update for Business. Pureinfotech expects the update to leave preview on December 8, 2026, which is Patch Tuesday. Microsoft hasn't confirmed that date in the material reviewed here, so treat it as an estimate.
Microsoft has also said there will be no non-security preview update in the second half of December 2026 because of the holidays. That makes the December security update the next likely way for the fix to reach managed PCs.
Summary: The fix is available now as an optional preview. Managed PCs will most likely get it in a later security update.
What to do until you're patched
The interim advice is simple, with one important condition:
- Check the PC, not the phone. If Windows shows you're signed in, the error on the Android phone can be ignored, according to the Microsoft guidance quoted by The Register.
- If the PC did not sign in, this advice doesn't apply. Troubleshoot it as a real failure. Check that Bluetooth and internet access are on for both devices, as Microsoft's documentation requires.
- Don't repeat a sign-in that already worked just because the phone says so.
For help desks, a short note to users ("if your PC signed in, ignore the Android error") could save a lot of tickets. Organisations that block Bluetooth should know Microsoft's passkey documentation explains how to allow passkey-only Bluetooth use with the Bluetooth and DeviceInstallation policy CSPs. That's a separate issue from this bug, but it often comes up when cross-device passkeys misbehave.
The bigger picture
Passkeys are Microsoft's main push toward passwordless sign-in, and cross-device authentication is a key part of it: your phone becomes the key for any nearby PC. KB5132057 also brings web sign-in to Microsoft Entra hybrid joined devices. At the lock screen, you can sign in without a password by using a FIDO2 security key, a passkey on your phone, or a Temporary Access Pass (TAP).
That's why a cosmetic bug like this matters. The more Microsoft relies on phone passkeys at the Windows lock screen and on the web, the more each misleading prompt erodes trust. This fix is small, but it supports a much larger rollout.
Bottom line
- What: Android phones show "Something went wrong" after cross-device passkey sign-ins on Windows 11 that actually succeeded.
- Who's affected: Windows 11 25H2 and 26H2 PCs using passkeys from Android phones. The Register reports Microsoft Authenticator and Google Password Manager, in Edge or Chrome, are affected and iPhones are not.
- The fix: KB5132057 (builds 26200.10075 and 26300.10075), an optional preview released November 19, 2026.
- Until then: If the PC confirms you're signed in, ignore the error on the phone. If the PC didn't sign in, troubleshoot it as a real failure.
Want to compare notes on passkey rollouts? WindowsForum's threads on KB5132057, Windows Hello and Entra passwordless sign-in are a good place to share what's working in your environment.
References
- Windows 11 passkey bug cries failure after successful sign-in The Register · 2026-11-20T11:09:44+00:00
- November 19, 2026—KB5132057 (OS Builds 26300.10075 and 26200.10075) Preview | Microsoft Support support.microsoft.com
- Release Preview Build 26200.10066/26300.10066 - Windows Insider Program | Microsoft Learn learn.microsoft.com