In message , Mayayana
writes:
[]
If it happens in all software then that indicates it's
systemwide, again pointing to some kind of keyboard hook.
And since it starts unpredictably and clears at startup,
that's another clue indicating it might be some kind of
faulty code that screws things up once it runs. To use
the example above, your tool watches for 48 + Shift but
then the programmer forgot to pass the message along
once it's been dealt with in that tool. In other words, a
bug in a keyboard hook could "eat" keyboard messages
in an unpredictable manner. It could even return the ability.

The two softwares: AllChars looks for a press and release of the Ctrl
key. But turning it off doesn't clear the fault once it has started.
Noisy Keyboard looks for _all_ keys - and continues to work when the
fault has started. (And, once again, doesn't cause the fault to stop if
I terminate it.)

When you talked about this last time I looked up hooks
but didn't find anything that seemed to be a way to
list active hooks. Windows apparently doesn't keep a
publicly accessible listing. So you just have to narrow it
down by looking at running processes that could be
hooking the keyboard.

I'll live with them for now: even if it does turn out to be those
softwares, I find their usefulness outweighs the inconvenience.

--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Dook, that was great but I think the line needs
awe. Can you do it again, giving it just a little awe?"

"Sure, George," said Wayne and looking up at the cross said:
"Aw, truly this man is the son of God."
(recounted in Radio Times, 30 March-5 April 2013.)