It's funny that I've been using this program for over a year, and only now am I having weirdness. :)

In the past couple of days, my RDP sessions through RDtabs suddenly start either not sending a key (like the letter "M" or "U") or acting as if the Windows Key is permanently depressed. I've tried killing RDtabs and restarting it (and re-connecting), but it appears to have become part of the RDP session. Finding key combinations to send an ESC (which seems to stop such behavior on the local computer) is akin to finding the Holy Grail in a Dan Brown novel...

On ALL sessions or just ONE session?

If just one, you tried logging off (not disconnecting) and logging back on?

Sometimes I've noticed that ALT, CTRL, SHIFT, or WIN can get stuck and you have to hit the key again so that the KEYUP message goes through the message pump to release it. I don't experience it often and in fact I don't think I've ever experienced it in a remote desktop session (for me, usually a local session when something crashes).

If ALL sessions, do you have System Key Shortcuts enabled (disabled by default)? That will trap a particular key (left or right CTRL or ALT) as an "escape" sequence to get to RD Tabs keyboard shortcuts while within a remote desktop session. I haven't experience it, but there could be a bug in the code somewhere.

I am also experiencing this problem as well. It happens on ALL sessions that I open. It is getting really annoying. I tried pressing the left and right window key just in case it is stuck but still experience the same problem once I open RD Tabs. I upgraded to 2.0.14 hoping it would fix the problem but has done nothing. I tried logging off and logging back on. My System Key Shortcuts is disabled. Any other suggestions that can fix this problem?

Thanks

Try upgrading to the 2.1.9 release candidate (it's very stable) and see if that helps. If not, try disabling the global keyboard hook (in the options) which is a feature new to 2.1.x. If that still doesn't fix it, then I may need some more information about your system to make a debug build of RD Tabs that might shed some light onto what is happening.

It seems like it has fixed the problem. I will keep an eye on it if it does happen again. Thanks