Community
Ctrl, Shift, Alt, AltGr and Enter stop working in Full Control
Links used in this discussion
João Pinto,
User (Posts: 1)
Nov 18, 2026 12:16:24 pm EST
Support level: Free or trial
Hello,
Several times a day (6+ on a busy day), the modifier keys stop being sent from the Viewer to the remote PC during a Full Control session. When it happens:
- Ctrl, Shift, Alt, AltGr and Enter are no longer sent. Only plain lowercase letters and numbers still get through.
- As a result, characters that need AltGr (e.g. "@" on a Portuguese keyboard) can't be typed at all, and no shortcut works.
- There are no stuck keys: I checked with the Windows On-Screen Keyboard on both PCs.
- Closing and reopening the Full Control window does NOT fix it.
- Only fully closing the Viewer (ending the process) and starting it again fixes it, until the next time.
- At the same moment, an [censored] session from the same local PC to the same remote PC works normally, so the remote PC and the keyboard itself are fine.
I have confirmed the keys are lost between the Viewer and the Host: typing directly into a local window on the remote PC (Notepad) shows the modifiers are not arriving.
Setup:
- Viewer: 7.9.0.0 on Windows 10
- Host: 7.9.0.0 on Windows 11 (laptop on the same home network)
- Both updated on 18-Nov-2026 (today); the problem happened with the previous versions too
- Keyboard layout: Portuguese (both PCs)
- I use "Full Control" mode; local hotkeys (e.g. Alt+5 for a media player) correctly stay on the local PC
Because the problem survives reopening the session but goes away when the Viewer process is restarted, it looks like something in the Viewer process stops handling modifier keys, possibly its keyboard hook being removed by Windows after a timeout.
Is this a known issue (couldn't find any on this version), and is there a setting, log or debug build I can use to help you find the cause?
Thank you.
Several times a day (6+ on a busy day), the modifier keys stop being sent from the Viewer to the remote PC during a Full Control session. When it happens:
- Ctrl, Shift, Alt, AltGr and Enter are no longer sent. Only plain lowercase letters and numbers still get through.
- As a result, characters that need AltGr (e.g. "@" on a Portuguese keyboard) can't be typed at all, and no shortcut works.
- There are no stuck keys: I checked with the Windows On-Screen Keyboard on both PCs.
- Closing and reopening the Full Control window does NOT fix it.
- Only fully closing the Viewer (ending the process) and starting it again fixes it, until the next time.
- At the same moment, an [censored] session from the same local PC to the same remote PC works normally, so the remote PC and the keyboard itself are fine.
I have confirmed the keys are lost between the Viewer and the Host: typing directly into a local window on the remote PC (Notepad) shows the modifiers are not arriving.
Setup:
- Viewer: 7.9.0.0 on Windows 10
- Host: 7.9.0.0 on Windows 11 (laptop on the same home network)
- Both updated on 18-Nov-2026 (today); the problem happened with the previous versions too
- Keyboard layout: Portuguese (both PCs)
- I use "Full Control" mode; local hotkeys (e.g. Alt+5 for a media player) correctly stay on the local PC
Because the problem survives reopening the session but goes away when the Viewer process is restarted, it looks like something in the Viewer process stops handling modifier keys, possibly its keyboard hook being removed by Windows after a timeout.
Is this a known issue (couldn't find any on this version), and is there a setting, log or debug build I can use to help you find the cause?
Thank you.
Conrad Sallian,
Support (Posts: 3324)
Nov 19, 2026 7:20:58 am EST
Hello João,
Thank you for the detailed report.
It isn't a known issue in 7.9.0.0. The closest reports we've had were typing that went wrong part-way through a session, where only a Viewer restart helped. What settled those was the connection's keyboard input method, so please try that first:
Your idea about the keyboard hook makes sense to us. Windows silently removes a low-level keyboard hook that doesn't respond within its time limit, and that would survive reopening the Full Control window but not a restart of the Viewer process. It would also fit with it happening more often on busy days. Two things make that more likely: other software on your PC that hooks the keyboard too (hotkey tools, text expanders, layout switchers, a media player's global hotkeys), and antivirus scanning the Viewer. Adding the Viewer's installation folder to your antivirus exceptions is worth a try.
If it still happens with Unicode input, turn on the Viewer log, note the time the keys stop next time, and send the log to support@remoteutilities.com. We'll take a look.
Let us know how it goes.
Thank you for the detailed report.
It isn't a known issue in 7.9.0.0. The closest reports we've had were typing that went wrong part-way through a session, where only a Viewer restart helped. What settled those was the connection's keyboard input method, so please try that first:
- Right-click the connection in the address book, choose Properties and open the Keyboard tab (see this page).
- Change Scan code input to Unicode input and click OK.
- Close the session and connect again, so the change takes effect.
Your idea about the keyboard hook makes sense to us. Windows silently removes a low-level keyboard hook that doesn't respond within its time limit, and that would survive reopening the Full Control window but not a restart of the Viewer process. It would also fit with it happening more often on busy days. Two things make that more likely: other software on your PC that hooks the keyboard too (hotkey tools, text expanders, layout switchers, a media player's global hotkeys), and antivirus scanning the Viewer. Adding the Viewer's installation folder to your antivirus exceptions is worth a try.
If it still happens with Unicode input, turn on the Viewer log, note the time the keys stop next time, and send the log to support@remoteutilities.com. We'll take a look.
Let us know how it goes.
* Website time zone: America/New_York (UTC -5)
