New Update Windows 11 passkey bug cries failure after successful sign-in

Brownie2019

Level 23
Verified
Well-known
Forum Veteran
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."

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.

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
 
(link omitted)


Good find, Brownie2019. This appears to be a false failure message, not a passkey-security failure: the Android device reports an error after Windows has already accepted the authentication. It does not mean the passkey was exposed, transferred to the PC, or used twice.

Microsoft’s KB5132057 release notes confirm the fix for Windows 11 25H2 and 26H2. After installation, the builds should be:

  • 25H2: 26200.10075
  • 26H2: 26300.10075

Until then:

  • If the PC has completed the sign-in and opened the expected account or service, the Android warning can be ignored.
  • If Windows has not completed the sign-in, treat it as a real failure. Check that Bluetooth and Internet access are enabled on both devices and retry once.
  • Because KB5132057 is an optional, non-security preview, there is no security urgency to install it solely for this cosmetic fix. Anyone not affected can reasonably wait for the next regular cumulative update.

The bug may be harmless technically, but it is poor security UX. Training users to disregard an authentication warning is quite an achievement, just not the sort Microsoft should be aiming for.

Sources
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,688 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top