Re: Update: Defender no longer mistakenly flagging NVDA


If you need to register, the add-on should let NVDA switch to its default voice to read the message.  Evidently, it doesn't, still using Eloquence to read the announcement and offering no way to switch to a different voice.  Perhaps there is a way that should be discussed.  I think that using another screen-reader and modifying the NVDA.ini file would solve the problem.  In general, if a synthesizer the user sets as default can't be used for some reason, NvDA defaults to its default.  If this is what is going on, that the user is trapped in a register message and can't switch to another synthesizer, that is very poor design. 
To be safe, when upgrading to this version of NVDA if using any synthesizer that may not be compatible, it would be a good idea to switch to another synthesizer that will have no compatibility problems and make sure that setting is saved by using control NVDA key c after the change is made.  Then, turn off save settings on exit so you won't upgrade, try the incompatible voice, close NVDA, and have that new setting saved.  All this should be done before upgrading.
----- Original Message -----

From: Rui Fontes
Sent: Monday, February 10, 2020 11:51 AM
Subject: Re: [nvda] Update: Defender no longer mistakenly flagging NVDA

Normally that message is from Eloquence from CodeFactory...

Rui Fontes

Às 17:16 de 10/02/2020, Robert Doc Wright godfearer escreveu:

Quentin, I just downloaded 2019.3 from the site. After installing I get a message that says, “please register”. This is announced no matter what key I press. The only option I am left with is to press insert q.



If we can't look at ourselves, and ask, why?  then where does the learning start?


From: Quentin Christensen
Sent: Sunday, February 9, 2020 7:46 PM
Subject: [nvda] Update: Defender no longer mistakenly flagging NVDA


Hi everyone,


Just a quick update - I mentioned on Friday that Microsoft had fixed their Defender definitions.  At the time it hadn't filtered down to me at least, although later on Friday it did and everything was fine again.  You should no longer have trouble installing NVDA 2019.3rc3 from:


If you are still having trouble using eSpeak on a previously installed or setup copy of the RC, you might need to install again, as Defender probably deleted the eSpeak.dll file (the file it was incorrectly flagging as problematic).


Also just to reassure everyone, there never was a problem with eSpeak or NVDA - there never was a trojan or malicious software, it was simply Windows defender incorrectly marking the espeak dll as problematic, even though there was nothing wrong with the file.


Kind regards





Quentin Christensen
Training and Support Manager




Join to automatically receive all group messages.