Skip to main content
Mallory

Windows Update KB5066835 Disrupts USB Input Devices in Windows Recovery Environment

patch-regressionwidely-deployed-product-advisory
Updated March 21, 2026 at 03:39 PM7 sources
Share:
Windows Update KB5066835 Disrupts USB Input Devices in Windows Recovery Environment

Get Ahead of Threats Like This

Know if you're exposed. Before adversaries strike.

Microsoft released the KB5066835 security update for Windows in October 2025, which introduced a critical issue affecting the Windows Recovery Environment (WinRE). After installing this update, users reported that USB-connected keyboards and mice stopped functioning within WinRE, rendering the recovery environment largely unusable for troubleshooting or repairing systems. The main Windows operating system remained unaffected, with USB input devices continuing to work as expected outside of recovery mode. This issue impacted both client versions, including Windows 11 24H2 and 25H2, as well as Windows Server 2025 platforms. Microsoft acknowledged the problem on its Windows release health dashboard, confirming that the bug was directly linked to the KB5066835 update. The inability to use USB input devices in WinRE prevented users from navigating recovery options, which could be particularly problematic for those needing to restore or repair their systems after critical failures. As a temporary workaround, Microsoft suggested using Bluetooth wireless input devices or legacy PS/2 connectors, which were not affected by the update. The company assured users that a fix was being developed and would be released in the coming days to address the issue. This incident followed previous problems with WinRE updates, such as the 0x80070643 installation errors that were resolved earlier in the year. The rapid response from Microsoft included an emergency patch to mitigate the disruption caused by the faulty update. Security news outlets highlighted the urgency of the situation, emphasizing the importance of WinRE for system recovery and the widespread impact of the bug. The incident underscored the risks associated with critical system updates and the need for thorough testing, especially for components essential to system recovery. Administrators and end-users were advised to monitor Microsoft's official channels for updates and to consider alternative input methods if immediate access to WinRE was required. The event demonstrated the cascading effects a single update can have on system usability, particularly in scenarios where recovery tools are vital. Microsoft's communication and swift action were crucial in managing the fallout and restoring confidence among its user base. The situation also served as a reminder for organizations to have contingency plans for recovery operations in the event of unexpected software issues.

Timeline

  1. Oct 21, 2025

    Microsoft releases emergency update KB5070773 to fix WinRE bug

    Microsoft rushed out emergency update KB5070773 to restore USB keyboard and mouse functionality in Windows Recovery after the October update issue. Multiple outlets reported the fix as an out-of-band response to the botched update.

  2. Oct 20, 2025

    October Windows updates break USB input in Windows Recovery

    Microsoft's October 2025 Windows updates, including KB5066835, introduced a bug that disabled USB keyboard and mouse input in the Windows Recovery Environment, making WinRE difficult or impossible to use on affected systems. Reports indicate the issue affected Windows 11 versions 24H2 and 25H2.

See the full picture in Mallory

Mallory subscribers get deeper analysis on every story, including:

Impact Assessment

Who’s affected and how

Technical Details

Deep-dive technical analysis

Response Recommendations

Actionable next steps for your team

Indicators of Compromise

IPs, domains, hashes, and more

AI Threads

Ask questions and take action on every story

Advanced Filters

Filter by topic, classification, timeframe

Scheduled Alerts

Get matching stories delivered automatically

Related Entities

Related Stories

Windows 10 KB5068164 WinRE Failure and Microsoft’s Delayed Fix

Windows 10 KB5068164 WinRE Failure and Microsoft’s Delayed Fix

Microsoft issued a fix for a **Windows 10 Windows Recovery Environment (WinRE)** failure introduced by the October 14, 2025 update that left some systems unable to launch WinRE, a critical last-resort recovery tool when Windows fails to boot. The remediation is associated with **KB5068164** for Windows 10 **21H2/22H2**, which was intended to update WinRE via a Safe OS Dynamic Update but instead shipped with a defect that prevented WinRE from starting; Microsoft provided limited technical detail beyond stating the issue was “addressed.” Reporting indicates Microsoft formally logged the known issue on **Feb 20, 2026** and updated support documentation with a resolution on **Mar 3, 2026**, leaving affected endpoints without functional WinRE for months. The update’s applicability is conditional (e.g., sufficient free space in the recovery partition—commonly cited as **250 MB**—and presence/state of a WinRE partition), and administrators can validate WinRE status using `reagentc /info`; a subsequent fix is referenced as **KB5075039**. Separately, a Windows 11 in-place upgrade bug has been reported to delete `C:\Windows\dot3svc\Policies` (impacting **802.1X** wired authentication and causing loss of network connectivity), but that issue is distinct from the WinRE incident.

1 months ago
Windows Update Bug Triggers BitLocker Recovery Mode on Reboot

Windows Update Bug Triggers BitLocker Recovery Mode on Reboot

A bug in recent Windows security updates has caused some systems to unexpectedly boot into BitLocker recovery mode after installation and reboot. Microsoft confirmed that the issue primarily affects Intel devices with Connected Standby (Modern Standby) support, impacting platforms such as Windows 11 24H2, 25H2, and Windows 10 22H2. Users encountering this problem are required to enter their BitLocker recovery key to regain access, after which the system resumes normal operation without further prompts. Microsoft has acknowledged the problem and advised IT administrators to use a group policy delivered via Known Issue Rollback (KIR) as a mitigation, with further support available through Microsoft Support for business customers. This incident follows similar BitLocker recovery issues triggered by Windows updates in May 2025, August 2024, and August 2022, highlighting a recurring challenge with update compatibility and BitLocker functionality on certain hardware configurations.

1 weeks ago
Microsoft January 2026 Windows Updates Trigger Remote Desktop Credential Failures and Secure Launch Shutdown Bug

Microsoft January 2026 Windows Updates Trigger Remote Desktop Credential Failures and Secure Launch Shutdown Bug

Microsoft’s January 2026 Windows security updates introduced regressions that disrupted enterprise endpoints, including **Remote Desktop authentication failures** affecting access to *Azure Virtual Desktop* and *Windows 365*. After installing `KB5074109` on specific Windows client builds (noted as Builds **26200.7623** and **26100.7623**), users reported repeated credential prompt/sign-in failures in the **Windows App**, preventing successful remote session establishment; Microsoft acknowledged the issue and issued an **out-of-band** update intended to restore normal Remote Desktop connectivity. Separately, Microsoft confirmed another January patch-related issue on Windows 11 23H2 where some systems with **Secure Launch** enabled may **fail to shut down, restart, or hibernate**, leaving devices running and potentially draining batteries. As a workaround, Microsoft advised forcing shutdown via the command: ```cmd shutdown /s /t 0 ``` Microsoft indicated a permanent fix would be delivered in a future update, but did not provide scope/impact metrics for affected devices.

1 months ago

Get Ahead of Threats Like This

Mallory continuously monitors global threat intelligence and correlates it with your attack surface. Know if you're exposed. Before adversaries strike.