Microsoft’s January preview patch has finally closed a persistent Windows 11 sign‑in annoyance and bundled a broad set of stability fixes that administrators and power users should evaluate now.
Background
Microsoft published a non‑security preview update,
KB5074105, on
January 29, 2026, delivering an optional cumulative package for Windows 11 versions
24H2 and
25H2. This update is a monthly, non‑security “preview” rollup: it’s optional, staged, and intended to let IT teams test fixes and quality improvements ahead of the next mandatory Patch Tuesday. The release advances the OS builds to
26100.7705 (24H2) and
26200.7705 (25H2) and lists a broad set of fixes and quality improvements across sign‑in, boot, activation, and File Explorer behaviors.
KB5074105 is notable because it addresses a long‑running, visible user experience bug introduced by an earlier preview: the
August 29, 2025 KB5064081 non‑security update. That August update created four documented regression symptoms, one of which made the password sign‑in icon invisible on the lock screen when multiple sign‑in options were configured. Microsoft initially mitigated some of KB5064081’s effects via later preview updates and Known Issue Rollback (KIR) policies, and KB5074105 now completes the fix for the password icon issue while also delivering a dozen+ other corrections.
What changed in KB5074105 (high level)
KB5074105 is not a security update; it’s a cumulative preview aimed at stability. The most important items for desktop and enterprise users include:
- Fix for the missing or invisible password icon on the lock screen (regression from KB5064081).
- Fix for an Explorer.exe hang that could occur on first sign‑in when certain startup apps were present, which could leave the taskbar or desktop unresponsive.
- Fixes for boot failures, including an iSCSI boot condition that could surface as an “Inaccessible Boot Device” stop error on some configurations.
- Responsiveness improvements to File Explorer when browsing network locations.
- Corrections for activation/license migration failures during upgrades in certain scenarios.
- Several additional fixes spanning Windows Sandbox, UAC elevation, desktop icon behavior, and keyboard settings.
These corrections were published in Microsoft's January preview release notes and independently verified by multiple Windows news outlets and community reports. The combination of sign‑in, boot, and Explorer fixes makes this one of the more consequential preview updates released in recent months.
The sign‑in icon bug: what happened and who it affected
What the bug looked like
After the August 29, 2025 preview update (KB5064081) and some subsequent builds, many devices that had
multiple sign‑in options enabled (for example: PIN, fingerprint, password) no longer showed the
password icon on the lock screen’s sign‑in options. The password mechanism itself remained functional — hovering over the blank area would reveal a placeholder and allow password entry — but the missing icon broke discoverability and degraded user experience.
Who was affected
Microsoft’s published guidance made an important distinction: the issue was
very unlikely to affect typical
Home and
Pro users on personal devices; the primary impact was observed in
enterprise or
managed environments where multiple authentication methods and enterprise provisioning commonly coexisted. That pattern is consistent with regressions that surface under complex, managed configurations rather than in simple consumer setups.
The interim workaround
While Microsoft prepared a permanent fix, the documented workarounds included:
- Hovering the mouse over the empty icon area and clicking the placeholder to reveal the password field.
- Using Known Issue Rollback (KIR) via Group Policy for managed deployments, which temporarily reverts the problematic change until a full fix ships.
KB5074105 carries the permanent resolution for this symptom, so organizations relying on the workaround can plan to move to the optional preview to validate the correction.
Why the optional (preview) update matters — preview vs Patch Tuesday
Microsoft splits its updates into different channels and categories. Understanding these helps match the update to your risk tolerance.
- Preview (Optional) Updates: Non‑security cumulative previews like KB5074105 are published monthly to allow testing of bug fixes, quality improvements, and non‑security features before they land in the mandatory Patch Tuesday rollups. They give IT teams an early look at fixes.
- Patch Tuesday (Cumulative Security Updates): Delivered on the second Tuesday of the month, these are mandatory security and quality rollups that most organizations apply via normal patching cycles.
- Out‑of‑Band: Rare or urgent fixes can be pushed outside the normal cadence.
Because KB5074105 is optional, it won’t be force‑installed by typical automatic update schedules. IT teams can fetch it via “Optional updates” in Settings, use Windows Update for Business controls, or deploy via catalog/WSUS packages for testing. The optional nature reduces risk for conservative environments but also means that systems still experiencing the KB5064081 symptom must actively install KB5074105 to obtain the fix.
The other headline fixes: Explorer.exe hang, iSCSI boot, activation
KB5074105’s scope goes beyond the sign‑in icon. Three fixes stand out for their operational impact:
- Explorer.exe hang at first sign‑in: Some systems configured with particular startup applications experienced a hang in Explorer.exe during the first interactive login. Because explorer.exe is the Windows shell (taskbar, Start menu, desktop, system tray), that hang can leave users without a functional UI even though Windows boots. KB5074105 explicitly lists a fix for that timing/regression and aims to stop the taskbar from failing to appear during first sign‑in.
- iSCSI boot failure (“Inaccessible Boot Device”): Systems that boot from iSCSI targets could encounter a failure to boot with an inaccessible boot device error. For organizations running block storage or remote iSCSI boot scenarios, this was a high‑severity operational problem. KB5074105 includes an address for the condition.
- Activation/Digital license migration failures: Some devices experienced failed automatic license registration during an upgrade, requiring manual intervention with the Activation troubleshooter. KB5074105 includes a change to counteract that registration problem.
These issues were surfaced by Microsoft’s release notes and corroborated by independent reporting and community feedback. The fixes indicate Microsoft’s attention to both interactive UX regressions and critical boot/activation scenarios.
The context: a rough patch in Windows update reliability
Over the last year Windows updates have included a number of high‑visibility regressions (UI oddities, DRM playback interruptions, driver interactions, and rare boot failures). The chain of events that led to KB5074105 is a useful case study in how modern OS updates — especially preview updates shipped to wide audiences — can create unintended side effects in diverse hardware/software ecosystems.
Key takeaways from the pattern:
- Complex, managed environments expose edge cases that consumer testing doesn’t always catch.
- Preview/optional updates serve a dual role: they get fixes in front of users faster but also risk delivering changes before every corner case is resolved.
- Known Issue Rollback (KIR) and the use of Group Policy to temporarily mitigate issues are now essential tools for enterprise IT teams.
It’s fair to say that the frequency of high‑profile regressions has raised concern among administrators. That said, the appearance of fixes in the next monthly preview demonstrates Microsoft’s iterative approach: identify problems, mitigate broadly where possible, and push targeted fixes in subsequent updates.
What administrators should do now — practical guidance
If you manage Windows fleets, here’s a prioritized checklist to evaluate KB5074105 and reduce risk.
- Inventory your risk profile
- Identify systems using enterprise sign‑in configurations (multiple sign‑in options), iSCSI boot setups, or complex startup application lists.
- Mark critical endpoints that cannot tolerate potential instability during business hours.
- Test KB5074105 in a staged ring
- Deploy the update first to a small pilot group (10–50 machines) representing your environment diversity: laptops, desktops, virtual machines, and machines using iSCSI or specialized drivers.
- Validate logon behavior, File Explorer responsiveness, boot success, and activation state.
- Use Windows Update for Business or WSUS to control rollout
- Keep the update in a test ring first; do not auto‑approve for all devices until you’ve validated the pilot.
- If you rely on WSUS or SCCM/Endpoint Configuration Manager, import the KB package and control deployment timing.
- Enable/prepare Known Issue Rollback (KIR) mitigations
- For managed devices that encountered the password icon regression earlier, KIR Group Policy objects were provided by Microsoft. Confirm whether KIR is required or if KB5074105 has already resolved the issue in your builds.
- Have your Group Policy rollbacks and recovery steps documented before broad deployment.
- Take recovery precautions
- Ensure you have tested repair and rollback procedures: System Restore (where available), image rollback, or the Windows Recovery Environment.
- For highly critical systems, consider full image backups or snapshotting before applying optional updates.
- Monitor vendor and community reports post‑deploy
- Observe telemetry, Event Viewer, and user help‑desk tickets for regressions (e.g., network connectivity, driver issues, application compatibility).
- Be prepared to roll back the update if you encounter new, reproducible failures.
Following a staged, measured deployment significantly reduces the chance that you’ll be surprised by a rare interaction.
Caveats and community reports after installation
While Microsoft’s release notes and reputable outlets confirm the fixes in KB5074105, community threads and some user reports indicate mixed post‑install experiences. Examples include anecdotal reports of:
- Wireless connectivity regressions on a small subset of NIC hardware after installing KB5074105.
- Initial Explorer sluggishness on first boots post‑install that later normalizes.
- Isolated issues unrelated to the fix list, which in some cases required driver updates or a rollback.
These reports are currently anecdotal and not reflected as new known issues from Microsoft at the time of publication. They do, however, underscore the value of staged testing. If you see a problem after applying KB5074105, collect logs (Event Viewer, reliability history), driver versions, and hardware identifiers before escalating to vendor support.
Be clear: a small handful of user reports does not invalidate the overall value of the fixes. It does mean the update interacts with a wide variety of third‑party drivers and configurations in unpredictable ways. Treat those reports as signals to observe, not as universal symptoms.
How Microsoft addressed this in policy and practice
Microsoft’s handling of this thread of regressions shows several elements of modern software lifecycle management:
- Public Known Issue documents: Microsoft recorded the password icon behavior as a known issue and published workarounds and KIR guidance for enterprise administrators.
- KIR and Group Policy mitigations: For managed environments, Microsoft provided Group Policy‑based KIR downloads to temporarily revert the change for affected devices.
- Preview channel fixes: The permanent fix for the password icon and other regressions were bundled into the January 29, 2026 preview update.
- Staged rollouts: Microsoft continues to stage deployment, meaning not all devices will see the update simultaneously; this reduces blast radius.
That approach — document, mitigate, fix, stage — reflects best practices for large OS vendors operating at global scale. It’s imperfect, but it’s pragmatic given the variability of hardware and software across Windows’ install base.
What this means for everyday users
If you’re an individual consumer on a Home or Pro machine, Microsoft’s guidance suggests you were very unlikely to experience the password icon regression. If you did see the issue, KB5074105 provides the fix and you can install the optional update via Settings → Windows Update → Optional updates → Download and install.
For business users and IT admins, KB5074105 is the update to validate if you experienced any of these symptoms after August 29, 2025, updates — especially the password icon disappearance, explorer.exe hang at first sign‑in, or iSCSI boot problems. But do not rush to blanket‑deploy: stage, test, monitor, and be ready to roll back if a new regression surfaces in your environment.
Final analysis — strengths and risks
Strengths
- KB5074105 bundles targeted fixes for high‑impact regressions (sign‑in UX, boot, and Explorer hang). These fixes restore basic usability and address operational failure modes.
- Microsoft’s public documentation and KIR mechanisms give enterprise admins tactical mitigations while a permanent fix is developed and validated.
- Staged, optional preview releases provide an opportunity to validate fixes before they reach the full, mandatory update channel.
Risks and open questions
- Preview updates inherently carry risk. Although optional, they change system behavior and can interact unpredictably with third‑party drivers and complex enterprise configurations.
- Community reports of isolated regressions following KB5074105 suggest that certain hardware/driver combinations may still be fragile; those require careful testing by admins.
- Broader confidence in update reliability has been strained by a series of visible regressions over the past year. Microsoft’s iterative fixes are appropriate, but organizations that cannot tolerate disruption should maintain conservative deployment rings and robust rollback plans.
Practical closure: a short checklist for today
- If you experienced the missing password icon or Explorer hang: schedule a pilot deployment of KB5074105 for test devices.
- If you operate iSCSI‑boot systems: prioritize testing KB5074105 in a maintenance window and verify boot success.
- For all admins: maintain a staged deployment, capture telemetry and logs, and prepare rollback steps before broad rollouts.
- For consumer users encountering the missing icon: hovering/clicking the empty area still allows password entry, but installing KB5074105 will restore the visible icon.
KB5074105 is a meaningful stability step: it addresses both a UX regression that frustrated sign‑in discoverability and several hard failure modes that impacted boot and shell reliability. The update’s optional status and staged rollout are appropriate for organizations that need to balance immediate remediation against the risk of introducing new, rare regressions. Test deliberately, monitor carefully, and treat KB5074105 as a targeted fix rather than an all‑clear for every update‑related risk.
Source: TechRepublic
New Microsoft Update Improves Windows Sign-In Experience