Re: multiple instances of NVDA

Quentin Christensen


I just tried and when I press CONTROL+ALT+N, the copy of NVDA which started automatically on login exits cleanly and the new copy starts.  What version of NVDA and Windows are you using though?

I am using Windows 10 (64-bit) Version: 1903 Build 18362 
Running NVDA version: alpha-20763,1ef4dfb0 

That's probably not the most usual combination though (My Windows 10 keeps hitting an error updating and I haven't taken the time to reformat it).  So if you're using a different version of Windows and / or NVDA your mileage might vary.  If anyone else tries this, please do share your version of Windows and NVDA and whether NVDA restarts cleanly or leaves an icon in the notification area.


On Fri, Aug 21, 2020 at 9:09 PM Gene <gsasner@...> wrote:
I should have added that I am using Windows 7 and using NVDA as a portable
program, and that may or may not make a difference.

-----Original Message-----
From: Gene
Sent: Friday, August 21, 2020 5:56 AM
Subject: Re: [nvda] multiple instances of NVDA

I've never had it happen when I unload NVDA, then restart it.  I'm not
talking about using the control alt n command when NVDA hangs or crashes.
I'm talking about using NVDA key q, then restarting.

KI've only seen this happen when NV
DA crashes and I restart it.

-----Original Message-----
From: Quentin Christensen
Sent: Friday, August 21, 2020 3:11 AM
Subject: Re: [nvda] multiple instances of NVDA

Interesting, I regularly restart NVDA and I don't recall ever seeing it from
that.  Do you have any add-ons?

On Fri, Aug 21, 2020 at 4:35 PM Luke Davis <luke@...> wrote:
On Fri, 21 Aug 2020, Quentin Christensen wrote:

> This is generally caused by something closing NVDA unexpectedly, such as
> it crashing, or if you go to task manager and "End task" it.  I haven't
> seen it
> when restarting or updating add-ons.  I wonder if it is a particular
> add-on which is not letting NVDA shut down cleanly?
> If anyone replicates this, ideally with the log set to debug level, I'd be
> interested in your nvda-old.log file (the one from when NVDA didn't shut
> down
> properly).

I'll get you one, but I must say that I have rarely NOT had this happen when
doing an NVDA restart.
It is just the way of things.
Since it happens on all of my systems, I assumed it was an error with slave
helper, and couldn't be avoided.



Quentin Christensen
Training and Support Manager

User group:
Twitter: @NVAccess

Quentin Christensen
Training and Support Manager

Join to automatically receive all group messages.