I have had windows do things with wireless keyboard.

If its doing that a lot, then its probably your keyboard.

It could be dirty but most like you have a dieing battery.

Make sure you keep a spare wired keyboard and lots of power cells about.

I have had users that have run out of batteries, have noticed things getting unstable, but never bothered about them, or added it to a todo list and forgot.

So they need to get another computer and go out to the store to get a battery.

Its like printer ink, actually buy your drums and ink before you run oout of them.



On 6/02/2019 7:18 AM, Brian's Mail list account via Groups.Io wrote:

It thinks you have pressed a combination of keys. I've definitely seen this in Windows 7. It seems quite random and I suspect its a windows issue myself. It is very rare but can for example appear if something is taking longer than normal to boot up I found.
If anyone has any idea let us know Often looking at the nvda log shos that several keys are pressed when only one or two are really pressed.
 I'm almost sure this goes back a very long way and had a ticket but nobody could get it to happen to order. I found often in my case it was windows and control.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Roger Stewart" <paganus2@...>
To: "NVDA List" <nvda@groups.io>
Sent: Tuesday, February 05, 2019 3:46 PM
Subject: [nvda] A weird one!

When I started my computer this morning I went to read my email and every key I pressed nvda kept saying "not in a table cell". I have no idea what that was about. I tried nvda key plus q to quit or restart nvda and it kept saying the same silly thing about table cells. Fortunately I have the Spydec P-View utility and I was able to find nvda.exe in the list of running apps and I was able to kill it from there. After I restarted nvda, everything was normal again! This is the first time I've ever had this happen in several years of using nvda. It was probably a one in a million glitch of some kind, but I'll watch and see if it ever happens again but I doubt it will. Any ideas on what might have happened? Just curious as I don't think this is a bug.

Roger