Windows XP Remote desktop acts like the SHIFT key is stuck.

[Dan Sheehan]

When I go through the logon process on a remote machine
from my XP desktop, the SHIFT key does not appear to
be "held down".
However after I am loged in, the following symptoms are
shown:
Moving the arrow keys around in any text (word, notepad,
Outlook, etc...) highlights the text as if I am holding
down the shift key. Doing normal things like deleting
something from Outlook, causes Outlook to prompt me for
an action as if the SHIFT key was held down (in the case
of delete it asks if I want to permanently delete the
email). More instances exibit the same behavior, however
regualr typing is not capitalized until I actually do
hold down the shift key. So it isn't 100% like the SHIFT
key is held down.

I have tried reinstalling Remote Desktop, installed the
Windows 2003 version, installed the old NT 4.0 client,
cleaned the HKCU\Software\Microsoft\Terminal Server
Client registry, and even renamed the c:\windows\system32
\mstscax.dll file so Windows would use the one in
C:\progam files\Remote Desktop.

As you can imagine, this is making the use of Remote
Desktop quite frustrating. Short of a complete reinstall
of the OS, I am not sure what else to do. Can someone
please offer some suggestion on getting Remote Desktop to
stop thinking the SHIFT key is held down for some
operatons?

Thanks!
Dan.

 

[Mike]

Sorry I can't offer a solution to this problem, but I can
at least offer some consolation; I have exactly the same
problem. I have no clue what started, but perhaps
someone else has some suggestions...

 

[loid]

Sorry, no solution, but same problem. I can't logon via
RD because the password seems to be incorrect. I think
the SHIFT key is permanently pressed.

 

[Eric]

I see the same thing--and it just started recently, and
only on one of my machines. What I see is that just the
arrow keys (and insert/delete/pgdn/etc.) are affected,
and that NUM LOCK now acts as the shift key for those
keys (and that the actual SHIFT keys have no affect on
them).

The best workaround I have is to turn off NUM LOCK; I'll
keep looking for a better one.

Eric