(Windows) Accounts that log in via a passkey are stuck on a white screen

[Tellinq]

Original reporter/ticket ID

No response

Project

Core

Describe the bug

Microsoft accounts have the option to sign in with a Passkey, when available.

With new accounts that have been created as of May 2025, passkeys are the default method of logging in, without having the option for a password. Accounts made before that timeframe have the option to add this after the fact.

If you attempt to log in via a passkey, unless you are prompted before entering your email to use a Windows Hello device bound passkey, you will be met with this screen.

Fortunately, users who use a Windows Hello device bound passkey can work around this if they are prompted to use a passkey saved directly on the device

Steps to reproduce

This can be reproduced in many ways, but the easiest way without needing to enroll can be done via the following:

1. Open the login window
2. Select Sign-in options
3. Select the option Face, fingerprint, PIN, or security key

This can also be reproduced for an account that either uses passkey authentication by default, or only has the option to use a passkey

1. Open the login window
2. Enter an email that fits one of the criteria's above

You do not necessarily need to have this account bound to a Minecraft/Xbox account. You can create a temporary account that uses passkey only authentication to test this if you wish to not modify your current account(s) login settings

Expected behavior

I should be immediately be prompted with a Passkey authentication screen such as this after either entering my email, or using the Sign in with Face, fingerprint, PIN, or security key option:

(Using Modrinth App as an example of correct behavior)

Operating System information

Windows 11 Pro 23H2 22631.5840

Additional context

A workaround to be able to log in is sign in via another application and set the default authentication as something else. However, this might not be suitable for users who specifically require a passkey-only approach, and do not allow the use of Windows Hello device bound passkeys.