Caps Lock problem on GtA v5

Hi DougT I have not been able to recreate the issue reliably without keyboard mashing, a developer on another team mentioned he has seen happen was the use of Windows keyboard combos repeatedly in irregular intervals can trigger this.

When this happens tapping the Ctrl key on your keyboard a few times should switch off the Function mode. Can you try that and let us know if it helps? Thanks. 

I also have this issue at the login screen.  Just started and was random but now is more prevalent.  It occurs from v5GTA app and Console.  Restart remote device and console device does not fix issue.

I have to bring up the virtual keyboard to log in. 

Once I log in, I can type upper case characters in notepad just fine.  

chrisg750 I have not been able to recreate this issue so it is hard to identify a cause. In GTARS v5 when you press Shift once on your keyboard the word Shift is displayed in the upper right and it goes away as soon as you type the first letter or click anywhere on your desktop. If you press Shift twice close together it is displayed again but with a white background, and now it is functioning as a Caps Lock until you press Shift again.

I suspect it is either sensing a double press or the Shift button or it could be 'sticky keys' in Windows is being enabled (although Windows typically shows a message about that).

BUMP- I have this problem consistently. Trying to reset someone's password with this issue is the worst possible thing. I have to confirm in notepad whether caps lock/shift is working or not. Has there been any solution one year later?

Nqua  Please confirm the GoToAssist endpoint version where you are experiencing this problem.  It should be fully resolved by now, so be sure to check for updates on all existing machines. 

I continue to have the Caps Lock problem on v5 as recently as Aug 6, 2021.  I'm using Windows 10.

NQuateman  cbmorehouse   The fixed version has been released to all accounts.  Please let us know if you see any other issues.  

Thanks. 

OK, we've identified the problem and expect a full resolution within 2 weeks.  

Thanks for your patience.