Troubleshooting · 5 min read
Keyboard and mouse not working in a remote session
Written for: Support operators whose remote session displays correctly but does not accept input.
Written by the 247connect Marketing Team · Last reviewed 27 August 2026
In short
When the screen updates but your keyboard and mouse do nothing, input is being blocked rather than lost. The usual causes are a session in view-only mode, an elevation prompt on the secure desktop that the agent cannot drive, the remote window not having focus, or a mismatched keyboard layout making keys arrive as the wrong characters. Each is quick to identify once you know the screen is fine.
Key takeaways
- A live screen with dead input means input is blocked, not disconnected.
- View-only mode is the most common answer and the easiest to overlook.
- Elevation prompts on the secure desktop reject input from an agent without the right privileges.
- Layout mismatches produce wrong characters rather than no characters — a different symptom with a different fix.
- A stuck modifier key makes every keystroke behave strangely; tapping each modifier clears it.
Check the session mode first
Most tools offer a view-only or observe mode, and it is frequently the default for shadowing and training sessions. It looks identical to a full session except nothing you do has any effect. Check the session toolbar for the control state before investigating anything else.
Related: some tools require the remote user to grant control explicitly in an attended session, separately from accepting the connection. A user who clicked accept but not allow control produces exactly this symptom.
Elevation and the secure desktop
If input stops at the moment a UAC prompt or the lock screen appears, the agent lacks the privileges to interact with the secure desktop. Windows isolates it deliberately so that ordinary software cannot click through an elevation prompt.
The fix is to run the agent as a system service with the rights to capture and drive the secure desktop, which is standard in tools designed for unattended administration.
Focus and window state
Input goes to whichever window has focus locally. If the remote viewer has lost focus — a notification stole it, or the window is behind another — keystrokes go to your own machine instead. Clicking into the session restores it.
This one has a hazard attached: keystrokes intended for the remote machine landing on your own can do real damage. If input appears to have stopped, stop typing before you diagnose.
Layouts and stuck modifiers
When keys produce the wrong characters rather than nothing at all, the local and remote keyboard layouts differ — a UK operator on a US-configured machine will find the @ and " symbols swapped and the pound sign missing. Match the layouts at both ends rather than working around it.
A modifier key that the remote machine believes is still held down will make every keystroke behave oddly: shortcuts firing unbidden, letters arriving capitalised. Tapping each of Shift, Ctrl, Alt and the Windows key on both sides clears the state.
Frequently asked questions
- Why can I see the screen but not control it?
- Input is being blocked rather than lost. Check view-only mode first, then whether the remote user has granted control, then whether an elevation prompt is holding the secure desktop.
- Why do my keys produce the wrong characters?
- Mismatched keyboard layouts between your machine and the remote one. Set both to the same layout rather than compensating manually.
- Why does everything behave as if Ctrl is held down?
- A modifier key is stuck in the remote machine's view, usually after alt-tabbing away mid-session. Tap each modifier on both sides to clear it.
- Why does input stop only when a UAC prompt appears?
- The secure desktop is isolated from ordinary input injection. The agent needs to run as a service with elevated rights to interact with it.
How this works in 247connect
247connect supports both view-only and full-control sessions with the mode shown in the session toolbar, and its managed agent can drive elevation prompts, which removes the two most common causes above.
More troubleshooting guides
No audio in a remote session
Why remote sessions have no sound, covering audio redirection settings, missing playback devices on headless machines, default device selection, muted mixers and bandwidth-driven audio suppression.
Cannot connect to a remote computer
A structured way to diagnose a remote connection that will not establish: proving the device is online, checking the agent, ruling out network and DNS, and separating an authentication failure from a reachability failure.
Session keeps disconnecting
How to diagnose remote sessions that drop repeatedly: distinguishing network instability from idle timeouts, power management and Wi-Fi roaming, and what to change to keep long sessions alive.
Related across the hub
How-to
Reboot and reconnect remotely
Restarting a machine from a remote session without losing access: safe mode considerations, what has to be true for the device to come back, and how to avoid stranding a computer you cannot reach.
Reference
Content updates
What has recently been added or revised across the hub.
Best practice
Securing remote access
A vendor-neutral guide to securing remote access software, drawing on NIST and CISA guidance: why remote access is a legitimate operational capability, how it is abused, and the controls that keep it safe.
Guides
Security
What secure remote access means in practice: zero-trust access, AES-256 encryption, two-factor authentication, audit logging, and the questions to ask any remote support vendor.
Best practice
Benefits of remote desktop
A vendor-neutral guide to what remote desktop access is good for: faster troubleshooting, centralised patching, fewer site visits, business continuity and keeping sensitive data off local devices.
How-to
Support multi-monitor setups
Handling multi-monitor remote sessions without squinting: switching between displays, spanning versus single-screen view, scaling, and what to do when the remote layout does not match yours.