The Windows Recovery Screen Is Up but the Keyboard and Mouse Do Nothing — Here's What Still Works

This is one of the most stuck a person can be with a computer that is otherwise fine. Windows will not start. After a few failed attempts it finally gives you the blue recovery screen — the one with Advanced options on it, and Troubleshoot behind that — the screen every repair guide on the internet, including ours, tells you to work from. And then nothing happens. The mouse pointer does not move, or there is no pointer at all. The keyboard does nothing: no arrow keys, no Tab, no Enter. You can see the fix and you cannot reach it.

People assume one of two things at that point, and both are usually wrong. The first is that the keyboard or mouse has broken at the worst possible moment. The second is that the computer is now so badly damaged that it cannot even run its own repair tools. What is actually happening is much more mundane, and once you know it the whole problem becomes navigable: that screen is not Windows. It is a separate, stripped-down operating system, and it loads its own drivers for your hardware. Your keyboard working in Windows tells you nothing whatsoever about whether it will work in there.

This guide is about getting input back so you can use the recovery tools. If your computer shows nothing at all — no logo, no lights, no fans — that is a different problem and our laptop triage guide is the place to start. And if you are reading this on a phone while a working computer sits in the next room, skip to the last section, because there is a ten-minute job you can do today that makes this entire situation solvable.

The recovery screen is not Windows, and that is the whole explanation

The screen you are looking at is the Windows Recovery Environment, which Microsoft abbreviates to WinRE. Its own technical documentation describes what it is built on: "WinRE is based on Windows Preinstallation Environment (Windows PE), and can be customized with additional drivers, languages, Windows PE Optional Components, and other troubleshooting and diagnostic tools."

Read that sentence slowly, because the important word is "drivers." The recovery environment is not your Windows installation running in a limited mode. It is a small, separate system image with its own set of drivers, and those drivers are not the ones your Windows installation uses. Microsoft's guidance to PC manufacturers is to put that image on a partition of its own: "Add the baseline WinRE tools image (winre.wim) to a separate partition from the Windows and data partitions." That is the stray little partition you may have noticed in Disk Management. It exists so that recovery still works when the Windows partition is broken or encrypted — which is exactly the day you need it.

So a keyboard has to be recognised twice on your computer: once by Windows, and once, separately, by the recovery environment. Almost always both work and nobody ever learns that they are two different things. When only one of them works, you get today.

Microsoft has documented this exact failure — and the dates matter

This is not a folk theory. Microsoft publishes a release health page for each version of Windows listing known issues, and one entry is titled, in Microsoft's own words, "USB mouse and keyboard not working in the Windows Recovery Environment (WinRE)." The description is precise about the symptom: after installing the security update released on October 14, 2025, "USB devices, such as keyboards and mice, do not function in the Windows Recovery Environment (WinRE). This issue prevents navigation of any of the recovery options within WinRE. Note that the USB devices continue to work normally within the Windows operating system."

That last sentence is the one to keep. The vendor itself is telling you that your keyboard can be perfectly functional in Windows and completely dead on the recovery screen, and that this is a property of the recovery environment rather than a fault in your hardware. The page lists the affected platforms as Windows 11 version 25H2 and Windows 11 version 24H2, and records that the issue was resolved by an out-of-band update released on October 20, 2025 — six days later.

So if your PC has been kept up to date, that particular bug is almost certainly not what you are looking at. It is still worth knowing about for three reasons. First, because there is a nasty circularity in it: the fix arrives through Windows Update, and Microsoft's own workaround section is explicitly aimed at a device that "is unable to boot to Windows to install the latest Windows update." A machine that has sat in a cupboard since 2025, or that was restored from older recovery media, can still be carrying it. Second, because it proves the failure mode is real, which matters when you are sitting in front of a dead screen wondering whether you are doing something stupid. And third, because the three workarounds Microsoft published for it are the same three things that help whatever the cause turns out to be.

Why input drivers in particular go missing in there

There is a second piece of Microsoft documentation that makes the shape of this clear, and it is about how the recovery environment gets updated. Unlike the rest of Windows, the recovery image is not patched in place. In Microsoft's words: "Unlike the normal OS update process, updates for Windows RE don't directly service the on-disk Windows RE image (winre.wim). Instead, a newer version of the Windows RE image replaces the existing one" — and then a short list of things gets put into that fresh image. The first item on the list is: "Boot critical and input device drivers from the full OS environment are added to the new Windows RE image."

Input device drivers are named, on their own, as a category that has to be carried across every time that image is replaced. The same page lists what is not carried across, and the first item is "Drivers which are in the existing Windows RE image but not in the full OS environment." In other words, the set of hardware your recovery environment can talk to is rebuilt periodically, from a different source than Windows uses, by a process that runs invisibly during an ordinary monthly update.

To be straight with you: Microsoft did not publish a root cause for the October 2025 issue, so treat that as how the plumbing works rather than as a stated explanation of that specific bug. But it is also why the recovery environment can simply lack support for hardware Windows handles without complaint, and Microsoft says as much elsewhere about a different device class: "Some Wi-Fi hardware, drivers, certificate providers, or enterprise authentication configurations might require components that aren't present in WinRE." Wi-Fi is the one they chose to warn about. Input can go the same way.

What still works, in the order worth trying

Work down this list. Each step is quick, none of them risks your files, and you can stop the moment something responds. Between steps, give the machine a few seconds — the recovery environment detects devices when it starts, so a change may only take effect after a restart.

Take everything out from between the keyboard and the computer. Unplug the USB hub, the monitor with USB ports on it, the docking station, the KVM switch, the powered splitter behind the desk. Plug a plain wired USB keyboard directly into a port on the computer itself — on a desktop that means the ports on the back of the machine, not the ones on the front panel, because the back ports are on the motherboard. If all you have is a wireless keyboard, borrow a wired one before you conclude anything: it is the single cheapest test on this list and it removes several variables at once.

Then try the other ports. If the machine has a mix of USB port types, try an older, slower one — often a black port rather than a blue one — and try both a front and a back port on a desktop. On a laptop, unplug the dock entirely and use the built-in keyboard and trackpad, which are wired to the machine directly rather than through a USB controller on a cable.

If the mouse is dead but the keyboard works at all, you are not stuck: the recovery menus are fully keyboard-navigable with Tab, the arrow keys, Enter and the space bar. Some of the tools behind them are keyboard-only anyway — the Startup Settings screen that gets you into Safe Mode works by pressing a number key, so a mouse would not have helped there regardless.

Microsoft's own three workarounds — including the one nobody has ready

When Microsoft documented the October 2025 issue it published three workarounds for a machine that cannot boot into Windows to install the fix. All three are worth trying for any dead-input recovery screen, not just that bug, and they are quoted here as written.

The first: "If your PC has a touchscreen, you can use the touchscreen's touch keyboard to navigate within WinRE." If you have a two-in-one, a Surface, or any laptop with a touch display, try tapping the screen before anything else. Touch on those machines does not go through the same path as a USB keyboard, and this is Microsoft's first suggestion for a reason.

The second: "If your PC has a PS/2 port, you can use a PS/2 keyboard or mouse to navigate within WinRE." A PS/2 port is the small round purple or green socket on the back of a desktop, and a surprising number of desktop motherboards still include one, often as a single combined port. No laptop has one. If you have an old beige keyboard in a box in the garage, this is the one day of its life that it is the most useful object in the house.

The third is the one that actually solves this reliably, and it is also the one almost nobody has: "If you had previously created a USB recovery drive, you can boot your computer from the recovery drive. This will take you directly to WinRE with restored USB functionality." Note the tense — previously created. A recovery drive is built on a working computer and carries its own copy of the recovery environment, complete with the drivers that were on the machine when you made it. It is the only item on the whole list that you cannot arrange after things have gone wrong.

One caution if you do boot from a recovery drive. The menu it lands on includes an option called "Recover from a drive," which is the full factory reinstall, and Microsoft's instructions for it have you choose between "Just remove my files" and "Fully clean the drive." That is not the button you want first. Go to Troubleshoot and the advanced options — Startup Repair, System Restore, Uninstall Updates, Command Prompt — and treat the reinstall as the last resort it is.

No recovery drive either? Windows installation media does the same job

There is a fourth route, and it works from any working PC and a spare USB stick, which is a much easier thing to find in a hurry than a recovery drive you never made. Microsoft's own support page for the recovery environment lists it: use the Media Creation Tool on a working computer to build Windows installation media, boot the broken machine from it, enter your language preferences, and then — this is the step people miss, because the screen is clearly trying to sell you a fresh installation — choose "Repair my PC" rather than Install. That lands you in the recovery environment, running from the stick rather than from the partition on your failing machine.

The same page notes the thing that trips this up: "If you don't see the setup screen, your PC might not be set up to boot from a drive." Getting a machine to boot from USB means telling the firmware to do it, which is a one-time boot menu on most machines — and, yes, pressing a key, which is why the wired-keyboard step above comes first.

Is it the recovery environment, or is the keyboard actually dead?

One test separates these cleanly, and it takes a minute. Restart the machine and press the key that opens your firmware setup screen — usually F2, F10, Delete or Escape, shown briefly on the maker's logo screen. That screen is the firmware on the motherboard, and it is older and simpler than anything Windows runs.

If your keyboard works in firmware setup but not on the recovery screen, the hardware, the cable and the port are all fine, and the problem is the recovery environment — which is the case this whole guide is about, and the recovery-drive and installation-media routes are your answer. If the keyboard does not work in firmware setup either, stop chasing Windows: you are looking at the keyboard, the cable, the port, or whatever you have plugged it into. Swap the keyboard, then swap the port.

A word about the lights, because they mislead people. A Num Lock or Caps Lock light coming on when you press the key tells you the port is supplying power to the keyboard. It does not tell you that the environment on screen is receiving anything from it. A lit keyboard on a screen that ignores you is completely consistent with everything described here, and it is not evidence that the keyboard is being heard.

While the computer still works: the ten-minute job that makes this a non-event

Of everything above, exactly one thing has to be done in advance, and it is the one that works. Make a recovery drive now, while the machine is healthy. Microsoft's instructions are short: find a USB drive you can erase, search the Start menu for "Recovery Drive" (or run recoverydrive.exe), make sure "Back up system files to the recovery drive" is ticked, choose the USB drive, and select Create. The warning on that page is worth repeating: "Use an empty USB drive because this process will erase any data that's already stored on the drive." It takes a while, because a lot of files get copied.

Two details from the same page that change how you should think about it. Microsoft says "It's recommended to recreate the recovery media annually to include the latest Windows updates and improvements" — so this is a yearly reminder, not a one-off, and a recovery drive made years ago carries years-old drivers. And it says plainly that "the recovery media doesn't include your personal files. Therefore, you should use a different backup method, such as Windows Backup or File History, to back up your personal data separately." A recovery drive is a way back into the machine. It is not a backup, and it will not save your photos. You still need the other thing.

While you are in there, it is worth confirming the recovery environment is actually present and switched on, because it can be turned off or left behind by a bad update. Open Command Prompt or Terminal as an administrator and run reagentc /info. Microsoft documents that option this way: "Displays the current status of Windows RE and any available recovery image on an online or offline image." You want to see it reported as enabled. Finding out that it is missing on a quiet Tuesday is free; finding out on the morning the machine will not boot is not.

And one more thing to have ready, because it is the cruel joke of this whole situation: the moment your keyboard starts working again may well be the moment the recovery tools ask you to type a 48-digit BitLocker recovery key. Microsoft's support page for the recovery environment says it directly — "If you've encrypted your device, you'll need the BitLocker recovery key to use certain tools." On most newer machines the drive is encrypted whether or not anyone chose that, and the key is saved to the Microsoft account the PC was set up with. Look it up from your phone before you start, not after. We wrote a whole guide to that trap.

What this does not fix

Getting the keyboard back gets you to the menu. It does not repair whatever stopped Windows from starting in the first place, and it is worth being clear about that so you are not disappointed twice in one evening. Once you can navigate, the order of tools to try — Startup Repair first, then Safe Mode, then System Restore, then Uninstall Updates, and a reinstall only at the very end — is a different job, and our guide to the automatic repair loop walks through it in that order.

It also does not help if the recovery environment never appears at all. A machine that shows a firmware message about no bootable device has not reached the recovery layer, and that is a different starting point. A machine that powers on to nothing at all is a hardware triage question. Both have their own guides below.

Stuck on a screen you cannot click?

If you are sitting in front of a recovery screen that will not respond, we can help — and it is often quicker than it looks, because the machine is usually not badly broken, it just cannot hear you. We service desktop and laptop computers across the Los Angeles area, Orange County, the Inland Empire, San Diego and the Coachella Valley, and this is a bench job with a known set of moves: a known-good wired keyboard on a motherboard port, our own recovery media built for the right version of Windows, and the repair tools worked through from safest to last resort with your files left alone.

If the machine is still working today and you would rather never meet this screen unprepared, ask us to set up a recovery drive and a real backup at the same time. They are two different things and most people have neither.