Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 3, 2016 6:12 PM | 1 vote
I use the Remote Desktop Connection application to connect to my work desktop. I'm running Windows 10 under Parallels under MacOS El Capitan. My Windows machine was updated to the Windows 10 Anniversary edition several days ago and since that time I have been unable to access my work computer through Remote Desktop Connection. The message I would receive was always that my username or password was incorrect.
Today I did some searching and I found some posts that said that there were other users of Remote Desktop Connection who were having problems with the Shift/Alt/Control keys not being recognized in RDP after the latest Windows 10 update. Sure enough, when I tried to connect to my work desktop using a different user id, I noticed that I was unable to get any capital letters, or any shifted characters from the number keys at the top of the keyboard.
Someone mentioned that if you held down *both* shift keys you could get things to work. This was sort of true. If I hold down both shift keys, I can get the shifted characters for the top row of keys (` through =) but the 'QWERTY' line of characters would not generate anything. Using the double shift approach, I was able to log on to my work computer, but even logged on I could not generate any shifted characters.
So, it seems that there is something wrong with Remote Desktop Connection and the way it interacts with the keyboard after the latest Windows 10 update. I don't know if there is anything that I can do to get around this problem, but I just wanted to report the error and hopefully get someone at Microsoft to look into a fix.
Thanks.
Jim
All replies (19)
Friday, October 28, 2016 9:07 AM âś…Answered
Hi jhoweaa,
It is not available for me to reproduce the issue on my side(Windows 10.14393.351). As a work around, we could use the "On-screen" keyboard.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Monday, October 3, 2016 6:25 PM
Hello
This kind of issue usually be caused by third party software, try to perform a Clean Boot to narrow down the cause:
http://support.microsoft.com/kb/929135
Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG.
In case it disappears in Clean Boot, please follow the method in the article to find the root cause.
Hope that helps
Regards, Regin Ravi
Wednesday, October 5, 2016 5:41 PM
I tried the clean boot. No change. RDP still does not recognize the shift key unless I am holding down *both* shift keys (and this only works for a subset of keys).
As I mentioned in my original post, everything was working properly prior to the Windows 10 Anniversary update, and this computer (a virtual machine running under Parallels) is almost exclusively used just to connect to my office computer through our VPN so there isn't a lot of other software running on the machine. I've seen other users reporting similar issues after the Windows 10 Anniversary upgrade, so I don't think this is unique to my environment.
Thanks!
Jim
Thursday, October 6, 2016 7:57 AM
Hi jhoweaa,
Are you using 32 bit machine?
We have got several reports that the remote desktop feature on a Windows 10 32 bit machine won`t work well.
I have made a test on my Windows 10.1607 version(64 bit). It is available for me to use the "shift" key. Please try to use the on-screen keyboard and check the symptom again.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, October 6, 2016 9:02 PM
I'm running the 64 bit version of Windows 10 10.1607 build 14393.222 64 bit.
If I bring up the on-screen keyboard, when I type my username/password in the entry fields on Remote Desktop Connection (this is the 'log on as other user' option) When I press the shift key on my keyboard and type a letter, the on screen keyboard lights up the shift key and the letter I'm pressing, but the letter that appears is lower case. If I use the on screen keyboard, clicking the shift key and then my letter, I do see an upper case letter.
Note that I do not have any problems with the keyboard anywhere else in the system (that I know of). For example, if I bring up Notepad ++, I can type upper and lower case characters just fine. If I enter information in a browser for searching, upper/lower case works just fine. The only time it doesn't work (again, that I know of) is when Remote Desktop Connection is launched. Also note that RDC is being launched from the VPN software that our company uses to provide access to their system (Array Networks). I first log on to the VPN through the browser (IE is required for this, unfortunately). After that a web page opens which lists the desktops to which I can connect. I enter my work machine address and RDC is launched for me (I believe this is done via a Java application running in the browser)
Again, never had any problems with this until Windows 10.1607 was installed on my machine (along with who knows what else)
Thanks!
Jim
Tuesday, October 11, 2016 7:34 AM | 5 votes
Hi jhoweaa,
Since the on-screen keyboard will work, the issue could be related to the "Keyboard" configuration. Please check the following keyboard configuration.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Monday, October 24, 2016 2:22 PM
The keyboard settings have no effect on this problem. The shift key still does not work unless both shift keys are held.
Wednesday, November 9, 2016 5:29 PM | 1 vote
Ive been using the onscreen keyboard, (which is a huge pain) but I discovered that pressing both shift keys works as well. So its a slightly lesser pain. Working on a macbook pro-> parallels 2015 VM running windows 10 -> remoting into a windows server 2008
Wednesday, February 22, 2017 8:42 PM | 5 votes
If I set this to "On this computer" my shift key works again.
Thanks for the suggestion.
Saturday, March 11, 2017 1:29 PM
It does work again with "On this computer", but then windows key combinations are sent to the local rather than the remote machine -- so it is a workaround.
I have the exact same issue. If the "Apply windows key combinations" setting is "Only when using the full screen", the shift keys will work properly when the remote desktop window is not in full screen. But when in full screen I need to press both keys simultaneously.
Thanks
Tuesday, March 21, 2017 2:15 AM | 5 votes
Hi,
I saw the similar issue on my Mac using parallels.
I saw a forum reply from parallels discussions.
http://kb.parallels.com/en/123130
Please try this and let me know if it works for you.
Thanks.
Wednesday, April 5, 2017 4:55 PM
This solves the issue.
Many thanks, I was going bonkers!
Wednesday, September 27, 2017 6:21 PM
"on this computer" solves this problem for me but it is completely counterintuitive. "on the remote computer" would seem to be the choice but it does not work.
Now both the shift and crtl keys work correctly in RDC
Friday, October 20, 2017 7:59 PM | 2 votes
The issue is related to the full screen mode, RDC thinks is not in full screen so it behave differently, try to go in windows mode and your shift key will start working.
Now we just need to find a way to make it back to normal.
-Richard
Friday, March 2, 2018 6:49 PM
Select On this Computer. That implies the comp you are RDPing to
Local Resources" src="https://social.technet.microsoft.com/Forums/getfile/1234799" />
Monday, February 11, 2019 1:24 PM | 1 vote
I just want to point out how you not being able to reproduce the issue is meaningless.
The solution is in here. You should endevour to move the solution up. Do better. Help people. I bought multiple keyboards to try and solve this problem.
CHANGE THE SETTINGS IN THE REMOTE DESKTOP TO "ON THIS COMPUTER"!!!!!
Wednesday, March 20, 2019 12:08 PM
Not an acceptable long term solution.
Wednesday, March 20, 2019 12:11 PM
Fully agree. Why comment if you can't help.
Wednesday, June 19, 2019 2:20 PM
Thank you. I was going bananas over here. I don't know what changed, it used to work normally. I never changed any settings and one day it just stopped working. But this fixed it!