The Windows Recovery Environment (RE) serves as a vital toolkit within Windows, designed to assist users in troubleshooting their computers. This includes functionalities such as accessing the BIOS and booting in safe mode. However, a recent update has unfortunately rendered this essential software ineffective for many users. The October build of Windows 11, identified as KB5066835, has introduced a bug that disables USB keyboards and mice within the recovery interface, leaving users unable to interact with the recovery UI.
Microsoft’s Response
Microsoft has acknowledged the issue and confirmed that a fix is forthcoming. While peripherals function normally within the operating system, they become unresponsive when users attempt to enter the Windows RE. This is particularly concerning, as the recovery environment is the default setting for PCs that fail to start, designed to help diagnose and resolve boot issues.
Interestingly, users who still rely on older PS/2-connected keyboards and mice appear to be unaffected by this glitch, offering a temporary workaround for those who are less tech-savvy and may not know how to navigate the situation. Microsoft has reassured users that they are “working to release a solution to resolve this issue in the coming days,” although the lack of urgency in their communication raises concerns about the timeliness of the resolution.
Impact on IT Professionals
This bug is not an isolated incident; it adds to a growing list of recurring issues that have plagued Windows with each update. The same KB5066835 update necessitated an emergency fix for localhost connections, which prevented developers from accessing their own computers—an essential function for many in the tech industry. IT professionals will find themselves particularly affected by the Windows RE bug, as numerous critical system repairs rely on this toolkit, effectively putting their work on hold.
Currently, this issue is present across various versions of Windows 11, including 25H2, 24H2, and even Windows Server, highlighting the widespread nature of the problem. As users await a resolution, the hope is that this matter will be addressed promptly, avoiding a repeat of past experiences where significant issues, such as the SSD fiasco, were left unresolved for too long.
