By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Caps Lock and Num Lock keys not working in Workspace since 5.2.1.3123 update

6

Since the Workspace Client Update to version 5.2.1.3123 my num lock and caps lock keys on the keyboard are not working correctly in the workspace. They are opposite on the workspace and local machine. For example - I log onto my workspace with the num lock off and turn it on once I am on my workspace it will work on my workspace but be off on my local machine. If I enable it while working on an application on my local machine it will not work on an application on the workspace. The same thing with the CAPS Lock This is causing users to enter incorrect passwords and not be able to access their workspaces or applications and get locked out. Anyone else experience this since the most recent Workspace client update?

We have clients running the older workspace client who do not have this issue.

  • Simon
    2 years ago

    Having the exact same issue here, after upgrading to 5.2. Just installed the latest fix version (5.3.0.3163), but the issue is still there.

  • rePost-User-8157809
    2 years ago

    Thanks for the update @simon. We had to go back to version 5.1.0.

  • rePost-User-0447696
    a year ago

    We have been going back and forth with AWS Support since June on this issue. Only temporary workarounds have been given but still no fix.

Topics
End User Computing
Tags
Amazon WorkSpaces
Language
English
rePost-User-8283250
asked 2 years ago4850 views
3 Answers
1

In Workspaces, go to Windows settings, open up On-Screen Keyboard.

One of the keys is "Options", push that and in the options turn on the numeric keypad.

Go back to On-Screen Keyboard

Find the NumLock key, press it, and close the On-Screen Keyboard.

This worked on Version 5.4 on all our workspaces.

rePost-User-2922631
answered 2 years ago
  • Brian McQuaig
    a year ago

    Thanks for the work-around...works great. My customers are going to want this to be transparent so I'm currently working out how to do this through a startup script. After testing, your solution does not persist after a restart of the WorkSpace unless the NumLock key is active, so that's where we'll need to concentrate our efforts. What I want to know is what is AWS doing to fix this issue? There has GOT to be a way that the client can determine what keyboard is in play whenever it is launched and make adjustments accordingly.

  • rePost-User-5986395
    a year ago

    Not an option for Linux Workspace users. AWS - please fix this. Find the regression since 4.0.6.

1

We are seeing 10-key characters not working. Going to try to revert to an earlier client version as waiting for a fix might be a while.

https://clients.amazonworkspaces.com/Versions.html

UPDATE: Version 5.1.0 worked for us.

rePost-User-8157809
answered 2 years ago
1

I did not find the issue resolved until I fell back to 4.0.6

rePost-User-0047732
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content