Microsoft October 2025 Updates Disable USB Input in Windows Recovery Environment
Summary
Hide ▲
Show ▼
Microsoft's October 2025 security updates (KB5066835) initially disabled USB mice and keyboards in the Windows Recovery Environment (WinRE), affecting both client (Windows 11 24H2 and 25H2) and server (Windows Server 2025) platforms. This issue made WinRE unusable for troubleshooting or repairing the OS, prompting users to switch to Bluetooth or PS/2 input devices as a workaround. Microsoft has since released an emergency update (KB5070773) to resolve the issue, which started rolling out on October 21, 2025. This update restores USB functionality in WinRE, allowing users to navigate recovery options. Affected customers can also use touchscreen, PS/2 devices, or USB recovery drives as workarounds. OEMs and enterprises can use PXE in Configuration Manager to install the update, while IT administrators can deploy push-button reset features using Windows ADK and WinPE add-on. Additionally, Microsoft confirmed in February 2026 that the October 2025 KB5068164 update for Windows 10 also broke WinRE. A new update (KB5075039) was released to fix this issue, requiring the WinRE partition to be at least 256MB in size.
Timeline
-
04.03.2026 23:03 1 articles · 23h ago
Microsoft releases KB5075039 to fix WinRE in Windows 10
Microsoft released KB5075039 to fix the WinRE issue in Windows 10, which was broken by the October 2025 KB5068164 update. The WinRE partition must be at least 256MB to install the update.
Show sources
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
21.10.2025 12:01 2 articles · 4mo ago
Microsoft releases emergency update KB5070773 to restore WinRE functionality
Microsoft released an emergency update (KB5070773) to fix the WinRE issues caused by the October 2025 security updates (KB5066835). The update restores USB functionality in WinRE, allowing users to navigate recovery options. Affected customers can use touchscreen, PS/2 devices, or USB recovery drives as workarounds. OEMs and enterprises can use PXE in Configuration Manager to install the update, while IT administrators can deploy push-button reset features using Windows ADK and WinPE add-on.
Show sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
20.10.2025 22:06 3 articles · 4mo ago
Microsoft October 2025 Updates Disable USB Input in Windows Recovery Environment
Microsoft's October 2025 security updates (KB5066835) disabled USB mice and keyboards in the Windows Recovery Environment (WinRE), making it unusable for troubleshooting or repairing the OS. This issue affected both client (Windows 11 24H2 and 25H2) and server (Windows Server 2025) platforms. Users were advised to use Bluetooth or PS/2 input devices until a fix was released. Additionally, the October 2025 KB5068164 update for Windows 10 also broke WinRE, which was confirmed in February 2026.
Show sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
Information Snippets
-
The October 2025 security updates (KB5066835) disable USB input devices in WinRE.
First reported: 20.10.2025 22:061 source, 3 articlesShow sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
This issue affects Windows 11 24H2, Windows 11 25H2, and Windows Server 2025.
First reported: 20.10.2025 22:061 source, 3 articlesShow sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
USB input devices still function normally within the Windows operating system.
First reported: 20.10.2025 22:061 source, 2 articlesShow sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
-
Users can switch to Bluetooth or PS/2 input devices as a workaround.
First reported: 20.10.2025 22:061 source, 3 articlesShow sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
Microsoft is working on a fix, expected to be released in the coming days.
First reported: 20.10.2025 22:061 source, 2 articlesShow sources
- Microsoft: October updates break USB input in Windows Recovery — www.bleepingcomputer.com — 20.10.2025 22:06
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
Microsoft released an emergency update (KB5070773) to fix the WinRE issues.
First reported: 21.10.2025 12:011 source, 2 articlesShow sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
The emergency update started rolling out on October 21, 2025.
First reported: 21.10.2025 12:011 source, 1 articleShow sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
-
Affected customers can use touchscreen, PS/2 devices, or USB recovery drives as workarounds.
First reported: 21.10.2025 12:011 source, 1 articleShow sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
-
OEMs and enterprises can use PXE in Configuration Manager to install the update.
First reported: 21.10.2025 12:011 source, 1 articleShow sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
-
IT administrators can deploy push-button reset features using Windows ADK and WinPE add-on.
First reported: 21.10.2025 12:011 source, 1 articleShow sources
- Windows 11 KB5070773 emergency update fixes Windows Recovery issues — www.bleepingcomputer.com — 21.10.2025 12:01
-
The October 2025 KB5068164 update for Windows 10 also broke WinRE.
First reported: 04.03.2026 23:031 source, 1 articleShow sources
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
Microsoft released KB5075039 to fix the WinRE issue in Windows 10.
First reported: 04.03.2026 23:031 source, 1 articleShow sources
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
-
The WinRE partition must be at least 256MB to install the update.
First reported: 04.03.2026 23:031 source, 1 articleShow sources
- Windows 10 KB5075039 update fixes broken Recovery Environment — www.bleepingcomputer.com — 04.03.2026 23:03
Similar Happenings
Windows 10 update bug triggers incorrect end-of-support alerts
A bug in the October 2025 Windows 10 updates triggers incorrect end-of-support alerts on systems running Windows 10 Enterprise LTSC 2021, Windows 10 IoT Enterprise LTSC 2021, and Windows 10 22H2 enrolled in the Extended Security Updates program. The bug causes affected devices to display 'Your version of Windows has reached the end of support' messages, despite the systems still being under active support or security coverage. Microsoft has deployed a cloud configuration update to correct the erroneous message, but some devices may not receive it due to connectivity or configuration issues. IT administrators can use Known Issue Rollback (KIR) to remove the incorrect messages on enterprise-managed devices. Microsoft released the first Windows 10 extended security update (KB5068781) on November 11, 2025, to address the bug for all customers enrolled in the Extended Security Updates (ESU) program. However, the KB5068781 update was failing to install with 0x800f0922 errors on devices with corporate licensing. Microsoft has now released an emergency Windows 10 KB5072653 out-of-band update on November 17, 2025, to resolve these installation issues. Some corporate Windows admins have reported that WSUS and SCCM are not correctly indicating that a Windows 10 device needs the extended security update, even when it is correctly enrolled in the program. Microsoft plans to release a new Scan Cab with updated metadata to address this issue.
Windows 11 updates disrupt localhost HTTP/2 connections
Microsoft's October Windows 11 updates (KB5066835) and September's KB5065789 preview update have caused issues with localhost (127.0.0.1) HTTP/2 connections. Users are experiencing errors such as 'ERR_CONNECTION_RESET' or 'ERR_HTTP2_PROTOCOL_ERROR' when attempting to connect to localhost. This affects various applications, including Visual Studio debugging, SSMS Entra ID authentication, and the Duo Desktop app. The issue also affects Windows Server 2025 systems and is linked to a bug in the HTTP.sys Windows-based web server for ASP.NET Core. Microsoft has provided a temporary fix via Known Issue Rollback (KIR) for non-managed business devices and most home users. IT administrators can resolve the issue on managed devices by installing and configuring a specific KIR group policy. A permanent fix will be included in a future Windows update.
Microsoft October 2025 Patch Tuesday fixes 6 zero-days, 183 flaws
Microsoft's October 2025 Patch Tuesday marked the end of free security updates for Windows 10, addressing 183 vulnerabilities, including six zero-days, with the final cumulative update **KB5066791**. The update also introduced critical fixes for components like Windows SMB Server, Microsoft SQL Server, and Remote Access Connection Manager, alongside third-party vulnerabilities in AMD EPYC processors and IGEL OS. However, a newly disclosed **February 2026 Patch Tuesday** update fixed **CVE-2026-20841**, a high-severity remote code execution flaw in **Windows 11 Notepad** that allowed attackers to execute arbitrary programs via malicious Markdown links without security warnings. The flaw, affecting Notepad versions 11.2510 and earlier, exploited improper command neutralization to launch unverified protocols (e.g., `file://`, `ms-appinstaller://`). Microsoft mitigated the risk by adding execution warnings for non-HTTP(S) URIs, with updates distributed automatically via the Microsoft Store. Prior milestones included out-of-band patches for a critical **WSUS vulnerability (CVE-2025-59287)** with public exploit code, smart card authentication issues caused by cryptographic service changes, and a **RasMan zero-day** (DoS vulnerability) affecting all Windows versions. Windows 10 reached end-of-life, with Extended Security Updates (ESU) available for purchase, while Exchange Server 2016/2019 and Skype for Business 2016 also ended support. The October 2025 update remains the largest on record, with 183 CVEs pushing Microsoft’s annual vulnerability count past 1,021.
Microsoft Releases November and December 2025 Patch Tuesday Updates for Windows 11
Microsoft has fully resolved the Windows 11 'UNMOUNTABLE_BOOT_VOLUME' boot failure issue in the February 2026 Patch Tuesday security update (KB5077181), addressing a problem that left commercial systems unbootable after failed December 2025 updates. The issue, which affected Windows 11 versions 25H2 and 24H2, was initially mitigated by the optional KB5074105 preview update but is now considered fully resolved. Devices that became unbootable before the fix may still require manual recovery or enterprise support. Earlier, Microsoft linked the January 2026 boot failures to failed attempts to install the December 2025 security update, which left systems in an unstable state. The company had also released emergency out-of-band updates to fix an unrelated issue causing Microsoft Outlook to freeze when PST files were stored in cloud services. Prior updates included fixes for gaming performance issues, broken localhost HTTP connections, and Windows Recovery Environment (WinRE) problems, alongside cumulative updates for November and December 2025 introducing new features and addressing security vulnerabilities across Windows 11 versions 25H2/24H2 and 23H2.
Windows 11 KB5065789 Preview Update Released with 41 Changes and Fixes
Microsoft has released the KB5067036 preview cumulative update for Windows 11 24H2 and 25H2, resolving the 0x800F081F error that caused Windows update failures. This update includes new features such as a redesigned Start Menu, the rollout of the Administrator Protection feature, and various bug fixes. The update is optional and does not include security patches. It addresses issues with the Media Creation Tool, HTTP/2 connections, and Kerberos Key Distribution Center (KDC) service. The update is available for installation via Windows Update or the Microsoft Update Catalog. The KB5065789 preview update, released on 2025-09-30, included 41 improvements and fixes, such as new AI actions in File Explorer, bug fixes for Windows Update, and Windows Sandbox. It also introduced features like Administrator Protection Preview, passkey integration, and performance improvements for gaming.