Bug Description
On the Windows client, once RustDesk captures keyboard input for a remote session, I cannot easily return input to my local computer using only the keyboard. Normal shortcuts such as Alt+Tab are handled by the remote session while capture is active.
Clicking outside the remote window can release capture, but this is not a usable solution for people who operate their computer entirely with a keyboard, including screen-reader users. It creates a significant accessibility barrier.
My workaround has been to press Ctrl+Alt+Delete to open the local Windows security screen, then press Esc to dismiss it. Keyboard input then returns to the local side. Opening the security screen should not be necessary just to regain local keyboard control.
This report concerns the desktop native keyboard input path (input source 1). The exact keyboard mapping mode was not recorded.
How to Reproduce
- From a Windows computer, connect to a remote computer with RustDesk using native keyboard input.
- Enter the remote view so that RustDesk captures the keyboard.
- Try to return to local applications using only the keyboard, without clicking outside the remote window.
- Local switching shortcuts are directed to the remote session, and there is no dedicated shortcut to release capture. The workaround is Ctrl+Alt+Delete followed by Esc on the local computer.
Expected Behavior
Provide a direct keyboard shortcut to release remote keyboard capture and return keyboard input to the local computer, while keeping the remote view visible and the connection open. Users should also be able to reacquire remote keyboard control using the shortcut.
The current keyboard destination should be clear through the existing toolbar icon and, on Windows, an accessible notification for screen-reader users. This should not require additional visible controls or moving focus away from the remote window.
Operating system(s) on local (controlling) side and remote (controlled) side
Local: Windows 11 x64. Remote: not recorded; this report concerns capture and release on the local client.
RustDesk Version(s) on local (controlling) side and remote (controlled) side
Local: a development/source build reporting RustDesk 1.5.0. Remote: not recorded.
Screenshots
Not applicable: this is a keyboard-routing and accessibility problem, with no visible error dialog.
Additional Context
I have implemented a fix in PR #16173: #16173.
- Ctrl+Alt+Pause/Break releases keyboard capture to the local computer. On Windows and macOS, pressing it again reacquires remote capture.
- The existing keyboard toolbar icon shows the current state, with the tooltip Keyboard: local / Keyboard: remote.
- On Windows, a UIA notification reports the state change to assistive technology. No live region or additional visible UI is added.
- The remote view remains visible; the shortcut does not minimize the window or send the user to the local desktop.
The shortcut is inspired by Microsoft RDP's Ctrl+Alt+Pause/Break behavior. RDP uses that shortcut to switch between full-screen and windowed mode; this PR applies the shortcut directly to keyboard capture while preserving the view.
Related previous report: #1098 (closed), which described the same difficulty for keyboard-only and blind users. This report supplies a concrete implementation for review in the linked PR.
Bug Description
On the Windows client, once RustDesk captures keyboard input for a remote session, I cannot easily return input to my local computer using only the keyboard. Normal shortcuts such as Alt+Tab are handled by the remote session while capture is active.
Clicking outside the remote window can release capture, but this is not a usable solution for people who operate their computer entirely with a keyboard, including screen-reader users. It creates a significant accessibility barrier.
My workaround has been to press Ctrl+Alt+Delete to open the local Windows security screen, then press Esc to dismiss it. Keyboard input then returns to the local side. Opening the security screen should not be necessary just to regain local keyboard control.
This report concerns the desktop native keyboard input path (input source 1). The exact keyboard mapping mode was not recorded.
How to Reproduce
Expected Behavior
Provide a direct keyboard shortcut to release remote keyboard capture and return keyboard input to the local computer, while keeping the remote view visible and the connection open. Users should also be able to reacquire remote keyboard control using the shortcut.
The current keyboard destination should be clear through the existing toolbar icon and, on Windows, an accessible notification for screen-reader users. This should not require additional visible controls or moving focus away from the remote window.
Operating system(s) on local (controlling) side and remote (controlled) side
Local: Windows 11 x64. Remote: not recorded; this report concerns capture and release on the local client.
RustDesk Version(s) on local (controlling) side and remote (controlled) side
Local: a development/source build reporting RustDesk 1.5.0. Remote: not recorded.
Screenshots
Not applicable: this is a keyboard-routing and accessibility problem, with no visible error dialog.
Additional Context
I have implemented a fix in PR #16173: #16173.
The shortcut is inspired by Microsoft RDP's Ctrl+Alt+Pause/Break behavior. RDP uses that shortcut to switch between full-screen and windowed mode; this PR applies the shortcut directly to keyboard capture while preserving the view.
Related previous report: #1098 (closed), which described the same difficulty for keyboard-only and blind users. This report supplies a concrete implementation for review in the linked PR.