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

Amazon Workspaces 5.0 Client issues?

4

Our organization has recently started deploying the 5.0 release of the Amazon Workspaces Desktop Client (specifically the Windows version, and most if not all of the Workspaces are running on PCoIP, in case it is relevant). Since doing so, we have noticed an increase in users having issues with their USB devices functioning properly in Amazon Workspaces. This primarily is manifesting as issues where their USB headsets will not be recognized after only a few minutes into their session, but we have been noticing it is causing strange issues with users' keyboards as well where the Caps Lock and Num Lock will not behave as expected inside of Amazon Workspaces despite working just fine on the host PC.

The keyboard issue has only started cropping up in any sort of noticeable numbers since the 5.0 client has begun deployment in our organization earlier this month. The headset issues are something that we are used to seeing, but have historically been able to resolve with standard troubleshooting methods such as adjusting the audio settings on the host PC, making sure that the user is not muted inside or outside of Amazon Workspaces, repairing the client and driver installations, restarting the Windows Audio Service inside and outside of Amazon Workspaces, rebooting the workspace and/or local PC, etc.

Typically, if those steps don't resolve the issue, we can point to a user's slow or unstable internet connection as a likely culprit or narrow it down to a hardware issue with the headset or PC. Since we started deploying the 5.0 Amazon Workspaces client, however, we have seen many more users having issues with their headset dropping out and not being recognized by the workspace client despite us replacing the hardware and confirming that they have exceptional internet speeds.

We are starting to roll back users who have issues to the last stable build as a short-term fix, but I haven't seen much being mentioned about this outside of my IT organization and was wondering if others have noticed the same issues? There seem to be some bugs with the USB handling in this release based on the way the problems are manifesting.

  • jwalkerwc
    2 years ago

    We are having the same keyboard issues. The Num Lock and Caps Lock will become reversed from the PC's operating system, so if the user has the Caps turned on (light illuminated on keyboard), it will be off in Workspaces. Restarting the workspace client can sometimes fix it temporarily.

  • rePost-User-2922631
    a year ago

    We are still having this issue as of 11-22-2022. Just received updates a couple of days ago and seems to have made it worse. Before we could reset the On Screen Keyboard to Number Lock and it would hold for several days. After the last update, we have to reset it every time we log on. We are an accounting firm and work with numbers all day long. This is very frustrating.

Topics
End User Computing
Tags
Amazon WorkSpaces
Language
English
rePost-User-7483970
asked 2 years ago2447 views
5 Answers
3

We are also seeing issues with the caps/num lock not being in sync. We are suggesting users roll back to a pre 5.0 version of the workspace but that is difficult since they need to uninstall and reinstall. How can we get a resolution to this?

rePost-User-8283250
answered 2 years ago
3

We are also having an issue with the caps/num lock not being in sync between the local machine and the workspace. What can we do to get to the bottom of this and get this issue resolved? I am going to submit a support ticket as well.

rePost-User-2575699
answered 2 years ago
0

(Deleted my original post because I made a comment instead of an answer. I'm a noob.)

I'm having the same issues. Num lock became permanently inverted somehow between my host computer and AWS workstation. My PC is the only one running the Windows 64-bit client. We have about 10 Mac client users with no num-lock issues. Caps lock has always worked for me.

Clean reinstall of the client didn't help. (To be fair, it did help the first two times, but not anytime after that.) Rebooting the remote workstation and host PC didn't help. Rebooting the AWS workstation while uninstalling and clean-installing the client, then rebooting the host before connecting to reset the num-lock states... didn't help. Reverting back to 4.x (even without rebooting the AWS workstation) resolved it and I haven't had an issue since. That seems to point to the issue being with the client app.

I don't have any feedback about USB audio devices, since we only use WorkSpaces to access our ERP app, and sound is hardly ever used.

I've also submitted a support ticket; we'll see where it goes. I'm happy with 4.x, but the last version was in Dec 2021.

rpsushi
answered a year ago
  • rpsushi
    a year ago

    I got this response from support:

    I have reviewed your issue and checked internally with service team. This issue has been acknowledged as a bug and is being worked on for a solution. Unfortunately I do not have an exact ETA as to when this issue will be resolved. However, I can assure you that the internal team is working hard and actively in order to find a resolution.
    ...
    Please keep eye on the clients release and review release notes. If the fix is in the release then upgrade otherwise please continue using the existing client.

0

We are also experiencing headset issues with version 5.x. USB headsets will intermittently stop working. Closing and restarting Workspaces will temporarily fix it.
We have found that switching to the 32 bit version avoids the issue.

rePost-User-4941104
answered 2 years ago
-2

Thanks for reaching out. We are not aware of any bugs in the new version of the client. I suggest you open a support case so we can gather more information and resolve your issue.

profile pictureAWS
Jeremy_S
answered 2 years ago
  • jwalkerwc
    2 years ago

    We have been having the keyboard (num & caps lock) issue for the past couple releases.

  • rePost-User-0447696
    a year ago

    We have had a ticket open with support for 132 days now. Amazon Engineers are well aware of the num lock sync issue but so far every fix we have tested for them has been unsuccessful. Case ID 10268231641

  • jwalkerwc
    a year ago

    This is STILL an issue in the most recent version (5.5.0.3276)!!

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