Microsoft has acknowledged a bug in the October Windows 11 update (KB5066835) that renders USB-connected mice and keyboards unusable within the Windows Recovery Environment (WinRE), preventing users from accessing critical repair tools.

The company confirmed the issue and stated it is working to resolve the problem swiftly.

Following the release of the October Windows 11 patch (KB5066835), numerous users reported that their USB-connected mice and keyboards ceased functioning in the Windows Recovery Environment (WinRE). Microsoft has officially admitted the existence of the problem and stated that developers are working on a fix patch.

While this may not affect general users immediately, the WinRE is a vital system necessary when a computer encounters problems, as it aggregates the tools used to rescue a user's machine. The inability to use the mouse and keyboard in this environment means users cannot access essential troubleshooting tools, such as:

Startup Repair: Fixes issues that prevent Windows from booting.

System Restore: Reverts system settings back to a previously working state.

Uninstall Updates: Removes recent updates that might be the cause of system problems.

Command Prompt: Allows for advanced commands to diagnose and fix system files.

Crucially, if a computer fails to boot three consecutive times, it automatically enters the WinRE screen. Without a functional mouse and keyboard, users will be unable to proceed with any recovery actions, leaving their computer stuck.

Switch to PS/2 Keyboards and Mice: If an older keyboard or mouse with the round PS/2 port (purple/green) is available, it can be used in the WinRE screen, as the problem only affects USB ports.

Create a Windows 11 Bootable USB: Users can create a Windows 11 installation drive via USB on another computer. Booting from this drive provides a "Repair your computer" option during the setup process, which leads to a fully functional Recovery Environment because it runs from the USB, not the damaged system.

Microsoft has confirmed the bug, stating it "is working to release a resolution in the coming days" but has not yet provided a precise timeline for the fix.