Forum Discussion
jholmquist
Feb 28, 2022Copper Contributor
Over the past week users have had issues with the number lock becoming out of sync.
Randomly while connected to azure virtual desktop the num lock gets turned off. If they toggle it off/on again it works again.
- Mar 07, 2022I can confirm. We rolled back several clients from this most recent version (1.2.2924) back to 1.2.2860 and have seen the issues disappear. We believe that a new feature in this update broke the syncing of both the Caps Lock and Num Lock to the RDP session.
Jeff_Heathman
Mar 02, 2022Copper Contributor
Also seeing similar issues seems to coincide with our recent update to the latest version for the Window Desktop App - 1.2.2924
JamesPike
Mar 07, 2022Copper Contributor
I can confirm. We rolled back several clients from this most recent version (1.2.2924) back to 1.2.2860 and have seen the issues disappear. We believe that a new feature in this update broke the syncing of both the Caps Lock and Num Lock to the RDP session.
- jholmquistMar 07, 2022Copper ContributorThanks for this James! I somehow didn't even register looking at the client update history. I am rolling a few users back to 2860 to see if that is indeed the issue.
- JamesPikeMar 08, 2022Copper ContributorDid you find any difference in the old version? I see the new version 1.2.2925 that Dennis mentioned, but I am also of the same mind that the fix was not notated in the changelog. I am going to get a few users on this new version regardless and see if it does fix the issue.
- jholmquistMar 09, 2022Copper ContributorWe just pushed 2860 to users last night. Unfortunately at least one person on that version says they are still having the issue. Microsoft said I would be informed when the problem is patched in an update but since the ticket is closed I find that unlikely to happen.
- Dennis_SchierenbeckMar 08, 2022Copper ContributorHallo zusammen,
scheinbar wurde die Version 1.2.2925 des Clients veröffentlicht, leider habe ich hierzu noch keinen ChangeLog gefunden. Vielleicht wurde der Fehler hier ja behoben.