Christopher-Mark Gilland <clgilland07@...>
toggle quoted messageShow quoted text
Definitely no keylogger. I ran all security checks
etc, and all looks blimmish free. No Keyloggers, no adware, no malware, no
viruses, no trogens, nothing.
Co-founder of Genuine Safe Haven
----- Original Message -----
Sent: Friday, June 09, 2017 6:37 AM
Subject: Re: [nvda] Incredibly odd
problem with the NVDA modifier key
Please, check if no KeyLogger or KeyTrapper is present on the
It is the first time I hear such an error so easily reproduced
by you and
not affecting the generality of users...
Original Message -----
From: "Christopher-Mark Gilland" <clgilland07@...>
Friday, June 09, 2017 12:11 AM
Subject: [nvda] Incredibly odd problem with
the NVDA modifier key
OK, this makes no sense, and I'm highly
surprised that no one has seen it,
given the fact I've reproduced it on
about 6 different computers here, and
have also had about 5 of my other
friends reproduce it as well.
Ever since updating to NVDA 2017.2, my
numpad insert key has completely
stopped working as the NVDA
I looked in the keyboard preferences and both caps lock and
are checked. I've unchecked and re, checked both checkboxes
well as at the same time. I've restarted NVDA, I've
rebooted, I've unloaded
all plugins and simply reinstalled from a fresh
copy with not a single addon
running, and all default stock
I've tried with both a portable copy, as well as a full
I've converted a portable to a full install, as well as
downloaded the setup
file and installed directly with no success.
even used Revo to remove NVDA so that no traces of any app data
behind. Then reinstalled. No good.
I've tried this on Windows 7
Home, Windows 7 Pro, Windows 7 Ultimate, all 3
of those, I've tried both
with X86 as well as X64.
I've tried with Windows 10 Home, Windows 10
Pro, and even had a friend who's
a college student try with Windows 10
Education. All of those were tested as
well on both X86 and X64. This was
reproduced on every single one of those
Before anyone asks the obvious, yes, num lock was
disabled. I'm not that far
I looked through the diag logs and
saw nothing that indicated what the
I checked for an
NVDA update and found nothing.
I installed the snapshot next branch and
had the same problem.
I tested with JAWS to be sure it wasn't something
screwy in general going on
with my insert key, but in JFW, it works
flawlessly, plus the fact it's
happenning on more than one
I even was so desperet, I tried with XP Pro, and that even