RemoteApp : Caps Lock / Num Lock become inverted in RemoteApp sessions. Server 2012r2 and 2016 RRS feed

  • General discussion

  • This issue has been a thorn in my side for the past several months. While investigating I've read every post/article I could find on the topic and wanted to share my findings, as well as include instructions how to recreate the issue which I haven't seen elsewhere. 


    In Server 2012r2 and Server 2016 RDS environments, while in published RemoteApp applications, the Caps lock/Numlock keys become inverted from the local computer. For example, the keyboard indicator shows Caps Lock is off, but capitalizes all characters in the RemoteApp application.


    The Caps Lock/Num Lock keys are inverted when the application opens a new window, a text field is selected, and the “Caps Lock” or "Num Lock" keys are the first input. It appears that when new Windows are generated from the published application they don't get keyboard sync information until text is input. For instance, if you launch a published instance of File Explorer, click the search bar, and hit the "Caps Lock" key, the issue doesn't happen. However, if you right click a folder, select "open in new window", click the search bar in the new window, then hit the caps lock key, it will. Again, only if the Caps Lock/Numlock keys are the first input.

    You can recreate the problem easily by doing the following:

    1. Publish "Notepad" in your RemoteApp environment
    2. Launch "Notepad
    3. Go to File -> Open
    4. Select the "File name:" field
    5. Press the "Caps Lock" or "Num Lock" key before pressing anything else
    6. The caps lock/num lock key will now be out of sync

    I have tested this in several applications including: Adobe, WordPad, Word, Excel, PowerPoint. This also works in clean installations on both Server 2012r2 and 2016.


    Currently none. We placed a paid ticket with Microsoft Support where we explained the issue and provided instructions on how to recreate. The ticket was escalated, and we were eventually informed that this is a known issue that hasn't been documented. We were then provided a refund and informed that they would let us know when a fix is in place.


    Clicking anywhere outside of the RemoteApp applications will correct the inversion. We typically recommend clicking the task bar. Another option is minimizing and maximizing the application manually or by pressing Win+D twice. Many of our users use the caps lock key in place of the shift key. I'm not sure how effective it has been but we are instructing users to use the shift key, especially when entering credentials. 

    Even though there isn't currently a solution I hope that this is at least informative and someone finds it helpful.

    • Edited by Jessticy Wednesday, June 5, 2019 4:49 PM Formatting
    Wednesday, June 5, 2019 4:46 PM

All replies

  • Hello Jessticy,

    We are having the same issue just in W10 client computers. Which OS client did you use to have this problem?

    Hope Microsoft releases a patch soon to fix it...


    Thursday, June 27, 2019 2:34 PM
  • Same issue here ! please let us know if you have any new information's !

    And thanks for sharing your return of experience :)


    Yohan LEFEVRE - MCTS / MCP

    Friday, September 6, 2019 9:06 AM
  • Jessticy,

    Have you received any further information from Microsoft about this issue? 

    I am in the process of deploying RemoteApps in a Windows 2016 environment with Windows 10 clients (1903 and 1809), and a few of my users are experiencing the issue and were even able to replicate using the steps above with an ERP client.


    Thursday, November 7, 2019 9:12 PM
  • Also seeing this exact issue with Server 2012R2 and Windows 10 clients.  As we were seeing this with 2008R2  before I'm not too hopeful they will fix it but here's hoping ;-)

    -- Al

    Tuesday, December 10, 2019 6:48 PM
  • We have the same issue, is there any update?
    Thursday, January 9, 2020 3:55 PM
  • Good morning, we also have the same problem. Have there been any developments from the support?
    Thursday, February 13, 2020 11:42 AM
  • Hi,

    This last UPDATE of W10 is even worse in this matter, how is possible that this issue is know for more than 1year and still nothing and now I can´t syncronise the Caps and Num lock. We are going back to the old MSTSC because this is making problems in our company.

    Tuesday, February 18, 2020 11:09 AM
  • Hi people

    Firstly, I'm commenting here because two of my customers has a similar issue (Caps Lock reversed) but it's an intermittent issue affecting users randomly.

    I've built two clean RDS test farms in my lab environment, one running Server 2012 R2 and one running Server 2016. Both fully patched. I've tried using the steps given at the top to try and reproduce the issue, but can't. After starting Notepad, File > Open, then pressing Caps Lock, the first character I type is shown in the correct case.

    My test desktop is a Windows 10 x64 device, version 1909 Build 18363.900, fully patched.

    Is there any other way of reproducing the issue?


    Ken Z

    Regards Ken Z

    • Edited by Ken Z Friday, July 3, 2020 9:56 AM bad grammar
    Friday, July 3, 2020 9:55 AM