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
Tuesday, November 3, 2015 8:14 PM | 7 votes
Hello all,
I am having this problem from multiple computers at multiple locations. Both the host and the remote client are running Windows 10.
As soon as I connect to a computer with Remote Desktop, on the host, the computer I am connecting to, the keyboard stops working.
Meaning I can not log back into computer once I return to it, because I can not input anything with the keyboard.
All I can do is restart the computer and possibly loose unsaved work.
Does anyone have a solution for this?
I have already tried creating the shortcut to the command prompt in administrator mode with this command:
%windir%\System32\tscon.exe 1 /dest:console
This does log me out of the RDP session and brings back the unlocked desktop, but does not give me back the keyboard input.
I really hope someone finds an answer to this, I can not be the only one having this issue.
Thanks!
All replies (41)
Friday, November 6, 2015 3:04 AM ✅Answered | 1 vote
Hi,
First, I would like to confirm whether the computer you remote into is a Virtual machine.
This issue is very confused, and the only thing I can consider should be driver redirection or driver in virtual machine.
If there is any driver redirection, please disable it to check the issue. Then make sure to update the USB hub driver to see if we can fix this issue.
Please test if the issue still persists in clean boot mode:
How to perform a clean boot
http://support.microsoft.com/kb/929135
If the issue doesn’t appear, you can determine which one can be the cause by using dichotomy in MSconfig. Checking on half of Non-Microsoft service and restart, determining which half of the services cause the issue and repeating to check half of the problematic half services.
If the issue still persists, please check the Event Viewer tree on the left side under "Applications and Services Logs -> Windows -> TerminalServices-*" where * is all of the logs there. I think you are most interested in the TerminalService-LocalSessionManager Operational log.
There is also a "RemoteDesktopServices-RemoteDesktopSessionManager" node in the event viewer tree on the left side under "Applications and Services Logs -> Windows".
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Monday, December 14, 2015 1:48 PM | 1 vote
This is happening to me as well. Windows 10 Dell desktop machine. Microsoft wireless natural multimedia keyboard and mouse (the kind with the remote "puck" hooked directly to the machine). After I RDP in, I lose the keyboard on the host, but the mouse on the machine is still active. I can type and use the mouse from the remote session. But getting it to work again requires a reboot of the machine.
Tuesday, January 19, 2016 6:43 PM | 2 votes
This is happening to me as well. Windows 10 Dell desktop machine. Microsoft wireless natural multimedia keyboard and mouse (the kind with the remote "puck" hooked directly to the machine). After I RDP in, I lose the keyboard on the host, but the mouse on the machine is still active. I can type and use the mouse from the remote session. But getting it to work again requires a reboot of the machine.
I am having the same issue - lost keyboard after RDP, even logout-login will not fix it, and have to reboot the machine.
Wednesday, January 20, 2016 7:06 PM | 4 votes
Also having the same problem on multiple domain joined PC's. On my desktop an easy fix I found is to plug the USB keyboard into another port and it starts working. On my laptop, so far a reboot is the only way I have found.
Monday, February 29, 2016 11:35 AM | 1 vote
I'm experiencing the same issue and can't see anything useful in the event viewer logs.
When will this issue be fixed?
Friday, March 18, 2016 5:38 AM | 1 vote
Have the same problem. Any solution?
Friday, April 1, 2016 8:15 PM | 1 vote
This is happening to me as well. Windows 10 Dell desktop machine. Microsoft wireless natural multimedia keyboard and mouse (the kind with the remote "puck" hooked directly to the machine). After I RDP in, I lose the keyboard on the host, but the mouse on the machine is still active. I can type and use the mouse from the remote session. But getting it to work again requires a reboot of the machine.
I am having the same issue - lost keyboard after RDP, even logout-login will not fix it, and have to reboot the machine.
This is my experience as well. I initially thought it was the Mac OS X Microsoft Remote Desktop app which caused it, but I tried again from another Windows 10 machine and the issue persists.
Friday, April 1, 2016 8:15 PM | 1 vote
I tried this as well. The keyboard works briefly but then stops accepting input again after a matter of seconds.
Tuesday, April 12, 2016 12:18 PM | 1 vote
I am having the exact same issue - no keyboard after RDP
Even logout and login does not fix it, and have to reboot the machine.
Usually deal with the On-screen keyboard to unlock the machine and reboot. Mouse works OK, which is on the same USB port (using wireless keyboard and mouse with the same receiver).
I also tried with wired keyboard - still the same issue. Its been like this for months.
Monday, May 9, 2016 8:49 AM | 1 vote
The quickest fix - unplug the keyboard from the USB port and attach it again.
Still looking for real solution of this nasty bug.
Friday, May 20, 2016 7:06 PM
I have the same problem.
Keyboard not working after RDP sessions at the host system. Unplug USB Keyboard and plug in again does help.
But is there any better solution?
Saturday, May 21, 2016 2:52 AM
But is there any better solution?
See if Mouse Without Borders can be your backup plan. In any case if you have a mouse you can always use the OSK with it, so there should not be any lost session just perhaps a bit of inconvenience while you use the workarounds. FWIW I'm using MWB to share my wireless keyboard and mouse between my Surface RT, Surface Pro and its Hyper-V guests. It's a bit quirky but better than not having a real keyboard or mouse at all with those other systems.
Heh. I just realized that I could probably use the RT's Remote Desktop app instead but it has always seemed more bother than I wanted to try. Also, while doing a Start Menu search for "remote" Team Viewer popped up in the results. <eg>
Robert Aldwinckle
Wednesday, May 25, 2016 12:22 AM
Dear All ,
I have the same problem in windows 7 pro 64-bit ,
Host is unable to type or use the mouse , after the remote session , this happens in both windows 7 pro and windows 8.1 pro
Please find a solution because the user is always irritated by this problem of non-working keyboard mouse and needs to remove and re insert the USB cables , or restart the Pc and then worrying about the opened application packages ruining on the background
If anyone has any suggestions please I would be glad to hear them ,
Thank you in advance ,for your time
FEAR
Wednesday, May 25, 2016 11:20 AM
Same problem as well - connecting to two computers running Windows 10 Pro x64, Microsoft Natural Ergonomic Keyboard 4000 v1.0 connected via USB (on both of them). Sometimes the keyboard works afterward, most of the time I have to reconnect the keyboard (I have USB hub on one PC and Toshiba docking station on the other).
Wednesday, June 1, 2016 8:48 PM
Same problem here. Windows 10.
Saturday, June 4, 2016 11:44 AM
same issue here...after RDP session, host keyboard is dead! with the same hw setup windows 7 was fine thought...
Thursday, September 8, 2016 4:05 PM
Assuming this is a laptop, then this would be the longest fix known to mankind, not the quickest. I'm having the issue with my Windows 10 laptop.
Friday, October 14, 2016 8:07 PM
The only solution I found was to use VNC instead of rdp. Frankly it's a lot better than rdp anyway.
Tuesday, February 21, 2017 4:50 PM | 1 vote
I'm having this problem as well, and rather frequently. Windows 10 build 14393.693 here. Unplugging the keyboard & plugging back in does not correct it for me. Requires a reboot. :(
Wednesday, June 14, 2017 1:14 PM
Same problem for me. Not find any solution. My keyboard became crazy after RDP and i have to reboot.
Friday, June 30, 2017 5:24 PM
There is this Hotfix for exactly that problem, but it only works on Window 7 and I have this issue on Windows 10.
Quote:
"The issue occurs because the remote desktop ActiveX object does not deactivate the focus of the remote desktop session when the focus is lost. Because the focus is still activated, the remote desktop ActiveX object cannot set the focus of the remote desktop session again when you change the focus back to the session."
Link:
Friday, June 30, 2017 6:33 PM
<quote>
Workaround
To work around this issue, switch to another tab in Internet Explorer and then switch back to the original one.
</quote>
That doesn't sound OS dependent. <eg>
Robert Aldwinckle
Monday, July 9, 2018 2:43 PM
Well not by now - since I'm facing this same cursed problems.July 2018
All I see are links to Win 7 operating systems with how-to-s that offer nothing for me.
Mine on the surface is vanilla. I'm running Win 10 on a notebook. I RDP to two PCs in my office. They are configured on 2 seperate ports. I can connect. The mouse moves but I cannot activate the right or left buttons. The keyboard is similar - little function - in. I can open links in bottom bar - so for example look at the computer settings / logs. Folders will not open.
Fuck.
Monday, July 9, 2018 2:44 PM
There is not solution.
No life raft.
No life jacket.
Screwed.
Monday, July 9, 2018 2:47 PM
Got to love a bit of OSK. Sounds quite painful ;)
FWIW sounds like Covefe to me.
MWB is even better.
Did you orgasm with excitment when you wrote this post? There is enough babble to make some geeks cream themselves.
Monday, July 9, 2018 2:48 PM
Screwed. Windows 10 please
Monday, July 9, 2018 2:48 PM
Well I've got a wire and it still doesn't work.
Monday, July 9, 2018 2:48 PM
Me fucking too.
Monday, July 9, 2018 2:49 PM
Well I never used it in Win 7
Now we are both using Win 10 so who cares?
Monday, July 9, 2018 2:49 PM
Yeh seems like the longest I'm typing this 2 years later.
Monday, July 9, 2018 2:50 PM
Well lovely for YOU. If you are going to post a rub-your-nose-in-it great.
Why not tell us how you made your VNC solution work?
Monday, July 9, 2018 2:51 PM
Every time you move the mouse?
Monday, July 9, 2018 2:52 PM
Exactly so what the fuck good is it? I keep seeing this shitty damn link. Like it is some solution.
It says applies to X, y and Z and NOT other systems.
Monday, July 9, 2018 2:54 PM
Mr Orgasm I don't have Internet Explorer open. I have not interest in opening it either. I want to open a folder (click) and then open and listen to a video (click 2).
No focus problem here. I can see the mouse activates the mimize / expand / close links in teh folder window but won't actually respond to te "clcik" to do it.
Can you supply an organsmic solution in plain English that might work?
Monday, July 9, 2018 2:56 PM
Mr Orgasm
For reference:
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
-
- Windows 7
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
Monday, July 9, 2018 2:56 PM
Gee - I've earned 5 points for my venting here.
But no solution.
Monday, July 9, 2018 2:58 PM
Yes - the office machines are Win 10 too.
The home network is a different subnet to the office. So please don't send me there.
Friday, April 5, 2019 12:43 PM
Have you noticed this trend they have on this forum? Person with oriental name posts a generic, useless answer, then proposes their own answer as the answer to get the points, then has no further input into the conversation. In the meantime, they nip to their buddy's desk and say "Hey, can you mark my answer as the answer on this question and I'll do the same for you next time? Thanks friend". Then, another oriental named person comes in and marks that as the answer.
At which point, the people who are paying for the product, are then left to be the support service for that product.
I would advise anyone who has this done to their question, to unmark the useless answer as the answer, as you are the only ones with the control to do that. If these support staff want to post, run and hide, then they need to have their points removed as a penalty. We're not here to provide their support for them... we've paid for the right to get that support *from* them. There's too much of this "abuse of power" by these lazy MSFT employees... keep on your toes people, you're the paying customer, not the unpaid employee.
Thursday, May 23, 2019 8:51 PM
These black caucasians microsoft use dont give a fuck about rdp , i am on remote desktop app now and the only solution is to exit all machine windows and then exit and start the app then they would log on again and network activity resumes because their graphical management is breaking network functionality in rdp. And to them fuck all the customers asking , because they blowjob the boss where they are from. Help , this motherfucking fuckup persists in remote desktop, remote desktop manager and remote desktop app all versions.
Thursday, June 6, 2019 9:54 PM
Wow, this is the longest "non-answer" I've seen. Complete waste of space on the forum thread. It's almost as bad as when moderators blindly suggest typing "SFC /Scannow" from the command prompt as a suggestion.
Friday, June 7, 2019 12:23 AM
I have an actual working solution for this. I spent a lot of time figuring this out so other people don't have to.
You need to download devcon.exe. Use the below link to download the correct version of Devcon
Learn how to restart your device using Devcon in the link below. This part is a little time-consuming. You have to find the right ID for your USB device to be able to restart it. You'll have to do trial and error to see which device ID responds to your restart command.
Restart USB device using devcon.exe
Ultimately, you'll have a command that looks similar to below, except with YOUR keyboard's hardware ID. Below, is the exact command I run for my USB keyboard:
devcon.exe restart "@USB\VID_04D9&PID_010B\000000000003"
Please mark this as the solution