Recent BIOS and Safe Mode Access Issues Linked to October Update
Users attempting to access their BIOS or Safe Mode have recently encountered a frustrating barrier: an unresponsive screen that leaves them unable to interact with their devices. This widespread issue, which has been reported across various online platforms, appears to stem from the latest October update, specifically update KB5066835, part of Microsoft’s October 2025 Patch.
The complaints indicate that this update has disrupted the Advanced Startup environment, rendering essential input devices like keyboards and mice non-functional precisely when users need them the most. Developers have also reported that this same update has compromised IIS and localhost functionality, compounding the challenges faced by many.
Frustrated users have taken to forums to share their experiences. One Reddit user lamented, “Whenever I do an advanced startup to access my BIOS my mouse and keyboard stop working.” Another user on the Eleven Forum, after attempting multiple fresh installs, noted that even a “Fresh MCT install + 6899 update = same” problem persisted.
The Advanced Startup screen appears to load, and the troubleshooting menu is displayed, yet there is no response from any input device. Users have tried various solutions, including swapping USB ports, testing different peripherals, disabling fast startup in BIOS, and even recreating the Windows Recovery Environment partition, all to no avail. As one user aptly put it, “It’s like the screen is frozen or my keyboard & mouse stopped working.”
Investigations suggest that the issue may be linked to the Windows Recovery Environment (WinRE) image file included with KB5066835. A user on r/pchelp reported success by replacing the problematic file with an older version (build 26200.6725), which restored USB functionality. Another user even provided a LimeWire link to download the older version, although it is worth noting that the link has a limited lifespan of one week.
In a separate thread, user u/Organic-Schedule1989 shared a workaround to regain access to Safe Mode. The steps are as follows:
- Create a Windows 11 installation USB.
- You can use the Media Creation Tool from Microsoft’s website.
- Boot from the USB.
- When the setup loads, click Next, then select Repair your computer.
- Open Command Prompt.
- Navigate to Troubleshoot → Advanced options → Command Prompt.
- Enter this command: bcdedit /set {current} safeboot minimal This will force Windows to boot into Safe Mode.
- Restart your PC and it should load into Safe Mode successfully.
- To return to normal Windows:
- Press Win + S and type msconfig, then open System Configuration.
- Go to the Boot tab and uncheck “Safe Boot.”
- Tick “Make all boot settings permanent” and click Apply → OK → Restart.
It is crucial to remember to uncheck the Safe Boot option once troubleshooting is complete, or users may find themselves repeatedly booting into Safe Mode.
The issue seems to disproportionately affect systems equipped with USB 3.0-only ports, although users with mixed port configurations have also reported problems. Interestingly, some laptop users have found that built-in keyboards remain functional, suggesting that the issue may specifically target USB drivers within the recovery environment. This would explain why peripherals operate seamlessly in normal Windows but become inoperative during troubleshooting.
As of now, Microsoft has not officially acknowledged the issue, but given the volume of reports, a resolution is anticipated in the near future. This latest complication adds to a growing list of challenges facing Windows 11, which has already been grappling with bugs in the File Explorer preview pane and broken taskbar search functionality.
