Can't type characters requiring the shift key on some remote sessions

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

We have been having a similar issue for several months, though it is not consistent or every time.  We have found that it happens mostoften with the shriek (! character), but also with the £ symbol. 

With the password that comes to mind it is isn't the first character in the password and all of the preceeding characters are accepted ok (and are shown on the screen as the * character).  Clicking back on the session and then the password box changes the focus back, but it is annoying enough to cause several expletives in the office!

I have combined these posts as they seem to be the same issue. 

550c can you please provide some more details about what you are experiencing? 

• Is this happening with specific characters, if yes which ones?
• Are you entering the characters in an application window or a browser window, does it make a difference?
• When the screen changes focus, what does it change focus to? (maybe a hotkey combination is being triggered) 
    

I have the same issue

Same issue for me. I cant enter passwords because the screen will change focus when entering a special character

Hey KateG!  These are all Windows 10 or Windows 11 machines.

Hi jaggrey welcome to the GoTo Community. I'd like to try and replicate your experience. Can you let me know the OS you are using? 

I'm having the random issue where when typing in a password at an elevated prompt, characters where I need to hit the Shift key are not inputted.  I've only seen this behavior when typing in my admin password on a user's machine that does not have admin access.  I have not tested inputting the characters in general when not at a prompt.