Windows 11 24H2 Update Conceals Password Icon on Lock Screen
Microsoft has acknowledged a peculiar user interface glitch in Windows 11 version 24H2 that causes the password sign-in icon to disappear from the lock screen’s Sign-in options. This issue emerged following the August 2025 non-security preview update (KB5064081) and has persisted in subsequent cumulative updates.
Understanding the Issue
The problem specifically affects users who have configured multiple authentication methods, such as a PIN, fingerprint, or security key, in addition to a traditional password. Under normal circumstances, Windows 11 displays icons for each available sign-in method beneath the Sign-in options link on the lock screen. However, after installing KB5064081 or later updates, the password icon fails to render, leaving an empty space in the list.
Despite the icon’s absence, its functionality remains intact. Users can still click on the invisible area where the password icon would typically appear to access the password entry field. This has led to confusion, as users are left to interact with an unseen element to sign in using their password.
Technical Details
– Affected Operating Systems: Windows 11 versions 24H2 and 25H2
– Problematic Update: KB5064081 (August 2025 Preview) and subsequent updates
– Symptom: Password icon missing from Sign-in options on the lock screen
– Condition: Occurs when multiple sign-in methods are enabled
Microsoft’s Response and Workaround
Microsoft has confirmed the issue and is actively working on a resolution. In the interim, the company advises users to hover their mouse cursor over the empty space where the password icon should be. When the cursor changes to a hand icon or highlights the area, clicking will reveal the password entry field, allowing users to sign in as usual.
While this workaround restores functionality, it has been criticized for its lack of intuitiveness, with some users describing the process as akin to clicking randomly until the field appears.
Looking Ahead
Microsoft is developing a permanent fix for this issue, which is expected to be included in an upcoming service release. Users are encouraged to stay updated through official Microsoft channels for announcements regarding the release of the fix.
