Re: Can't always blame NVDA

Brian's Mail list account <bglists@...>

And that is exactly the issue, ie some sail through unscathed while others do not.

Several people I know have rolled back to the last update due to one of the recent ones making their machine slow eat battery and overheat.
These issues have to be driver related at the lowest hardware level.
Sent via blueyonder.
Please address personal E-mail to:-, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Alexander Masic" <>
To: <>
Sent: Sunday, November 18, 2018 6:50 AM
Subject: Re: [nvda] Can't always blame NVDA

I am running the latest build 1809, and I am not facing any proglem with
it. I have one Varioultra running on bluetooth placed on the left
conected with bluetooth, and it run fine. and also i have not loused any

Den 2018-11-18 kl. 06:41, skrev Gene:
Kim Komando, because of all the problems with the latest full update,
advises people not to install the update earlier than it is offered to
you and even then, to defer it if you can until it is clear that it is
advisable to install it. You can't put it off indefinitely, but there
are ways to delay it.
Microsoft originally released this update obviously when it wasn't
ready, and the same with the last full update. I hope that, instead
of people chomping at the bit to try the new full updates, that they
wait to see if Microsoft has released a good update in future. Of
course, if someone wants to see what the latest is like and be a
guinea pig, a beta tester after beta testing should no longer be
necessary, that's fine, but for those who aren't in that category and
who want dependability and reliability, I would always wait. Even in
the past, before Windows 10, people were advised to wait after a new
version of Windows came out before adopting it. Even with proper
care, there are always going to be problems with a complex piece of
software like this. But the last two full updates have more and more
serious problems than properly tested software should.
----- Original Message -----
*From:* John J. Boyer <>
*Sent:* Saturday, November 17, 2018 10:26 PM
*To:* <>
*Subject:* Re: [nvda] Can't always blame NVDA

Microsoft has caused a lot of trouble with their updates. One of the
latest turned off Bluetooth on my laptop computer,
so i couldn't get Braille output. My computer maintenance organization
had to remote in and turn it bck on. My desktop
machine was also behaving strangely after a recent update. I couldn't
get any Braille output until I turned it off with
the power button and then back on. Three boos for Microsoft.


On Sat, Nov 17, 2018 at 12:05:59PM -0700, Jackie wrote:
This week my computer became really unresponsive to key presses. It
was right after a Windows 10 update, so I was blaming some sort of
incompatibility between W10 & NVDA. I was going to roll it back, but
for some reason I decided to do another test first & plugged a USB
keyboard into my laptop. Guess what? All the unresponsiveness
disappeared! Just goes to show sometimes that events surrounding
things like unresponsiveness, ie, such as an update, may be purely
coincidental & merely serve to throw a smoke screen. Troubleshooting
can be a real b-word, & I guess it's just best to keep all the
possibilities in mind. This was addressed to no one in particular.
Just sharing an experience on a Saturday in hopes it might help
someone on their troubleshooting journey.

Subscribe to a WordPress for Newbies Mailing List by sending a
message to:
<> with 'subscribe' in the
Subject field OR by
visiting the list page at
& check out my sites at
<> &

John J. Boyer
Email: <>
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM
that are available at no cost

Join to automatically receive all group messages.