This issue I first noticed yesterday, could not type an upper case character or symbol to save me!
Today I switched keyboards thinking it was a stuck key, but same thing. Then I discovered it's only the right-hand shift key not working in the remote session; the left works fine for both caps and symbols.
Remote devices: affecting both W10 and W11 Pro
GoToRemote version 1.11.0.2369
My system is
Edition Windows 11 Pro
Version 22H2
Installed on 2/7/2023
OS build 22621.2283
Experience Windows Feature Experience Pack 1000.22662.1000.0
Hi DustyD,
When you press either of the Shift keys did you see this displayed at the bottom of the screen? If you open Notepad or Word in session and just type is the right Shift key still being ignored?
I'm running some tests, Windows 11 to Windows 10 Unattended first in the browser and then using the Desktop Console. So far both Shift, Ctrl and Alt keys are registering correctly when I type in a Word doc.
Sry for late reply, was travelling today. No, I only see the highlighted Ctrl Shift, etc boxes when using the left Shift key. The right one gets no response. Same behaviour in Notepad.
Was there a solution to this? Why is there an onscreen keyboard? Why does it override the keystrokes, and why the hell would it be on by default.
Do threads usually end in no solution? Not a good start to this new contract. Maybe we should look into a different vendor.
I'm not 100% sure if there was a published solution.
My issue went away after remapping the Right Shift key to function as the Left.
Still annoying me to no end is the apparent reversal of the CAPS and NumLock keys between the tech and client devices.
I have the same issue on both the desktop console and the web. Any resolution for this issue?
Currently experiencing this issue. Shift won't work for ! or @ when remoted into certain systems on random sessions. Not sure why. I did fix it though, instead of just typing shift + 1 for an exclamation mark try typing ctrl + shift + 1. It works for me and allows me to log in to my machines!
