Microsoft Fixes Bug Causing Password Sign-In Option to Disappear

Why It Matters

Restoring the password icon eliminates user confusion and reduces support overhead, underscoring Microsoft’s commitment to post‑release stability.

Key Takeaways

• Bug removed password icon after August 2025 updates
• Affected users with multiple sign‑in methods
• Fixed in KB5074105 cumulative update
• Update also patches boot and activation bugs
• Install via Settings > Windows Update or catalog

Pulse Analysis

The disappearing password icon on Windows 11’s lock screen sparked frustration among both consumer and enterprise users, especially those who rely on a mix of PINs, security keys, and passwords. The UI glitch originated from the August 2025 KB5064081 preview update, which unintentionally suppressed the password button when multiple sign‑in options were present. While the password field remained accessible via a hidden placeholder, the missing visual cue disrupted familiar workflows and increased help‑desk tickets, highlighting how minor interface regressions can ripple across large deployments.

Microsoft’s response arrived with the January 2026 KB5074105 cumulative update, an optional but recommended patch that restores the missing icon and bundles 32 additional fixes. Beyond the UI correction, the update resolves iSCSI boot failures, Explorer.exe hangs during first login, and activation server registration errors—issues that collectively affect system reliability and licensing compliance. Administrators can deploy the update through the standard Settings → Windows Update path or manually download it from the Microsoft Update Catalog, ensuring a streamlined rollout across heterogeneous environments.

The episode reinforces the delicate balance Microsoft must strike between rapid feature delivery and rigorous quality assurance. As Windows 11 continues to evolve through semi‑annual feature updates, maintaining UI consistency becomes critical for enterprise productivity and user trust. Proactive monitoring and swift patch cycles, as demonstrated by the KB5074105 release, are essential to mitigate the operational impact of such regressions. Organizations should incorporate optional cumulative updates into their maintenance windows to stay ahead of similar issues and preserve a seamless authentication experience.