Forum Discussion

jholmquist's avatar
jholmquist
Copper Contributor
Feb 28, 2022
Solved

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.  
  • JamesPike's avatar
    JamesPike
    Mar 07, 2022
    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.
JackWR's avatar
JackWR
Copper Contributor
Mar 15, 2022

Microsoft no longer has the link to download version 1.2.28xxx.
Has anyone got a fix for this yet, newest version 1.2925 still seems to have the same issue?

JonatanB's avatar
JonatanB
Copper Contributor
Mar 15, 2022
Hi Jack, i found the link for 1.2.28xx, using archive.org (https://web.archive.org/web/20220225041639/https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windowsdesktop-whatsnew)
and went back a month to find the direct download link: https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWVhzA
  • JackWR's avatar
    JackWR
    Copper Contributor
    Mar 15, 2022

    JonatanB Thank you very much, that's a nice little trick, I'll add it to my toolbox.

    • Dennis_Schierenbeck's avatar
      Dennis_Schierenbeck
      Copper Contributor
      Mar 16, 2022
      In the newest version 1.2.2927 the following information can be found in the ChangeLog "Fixed an issue where the number pad didn't work on initial focus."
      Seems to be fixed in this version
      • sberens's avatar
        sberens
        Copper Contributor
        Mar 21, 2022

        I found this page as a number of our users have started reporting issues now that they're on 1.2.2927.0, one user reported an issue a few days before 2927 was released so it could have existed in 2925 but took users a while to start reporting the behavior.  

         

        User experience is that they'll be using their number pad without issue then it'll just stop for a user.  Number lock shows ON on the users keyboard, number pad works fine in apps running locally, but apps on AVD Session Hosts will not.  User toggles number lock a few times and it starts working again, but definitely seems something recently happened that's causing sporadic number pad issues, and isn't 100% fixed in 2927.

         

        Going to recommend our users go back to 1.2.2925.0, but wanted to validate that others are still seeing odd number pad behavior on these new AVD client versions.  

Resources