Update: Defender no longer mistakenly flagging NVDA
|
Quentin Christensen
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: https://www.nvaccess.org/post/nvda-2019-3rc3-now-available-for-testing/ 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. Quentin Christensen Training and Support Manager NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/ Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess
|
|
|
|
Well thats good to know. I do really wish that if there is something a security detects as a potential issue that it finds and says its a possible issue because it may be unknown or it could be bad, or it looks like %trogen name but its unsure. What I have had happen on the net is that software x is a trogen and its name is given. The developer is contacted, he looks at it and says its not. People then flame the dev and say its a virus, then start saying all his stuff is a virus and he is bad. One of 2 things happen. 1. the developer fixes it, is aware and handles it. or. 2: and sadly what mostly happens in some forums. The developer goes, deletes his stuff and storms off. People trust their security and think its the word of god and once there is a name well they throw it about like a piece of well chooed gum. They don't care where it goes, they start making drama and so it goes on. I don't even think the companies realise what dammage they are doing. False positives are just things things find because it looks like something else. Thats not a problem but when they start naming and shaming its a problem. When avg used to find stuff like this it was like avg found unknown trogen name. ext which is in file and folder name and extention, is not in our database. I didn't really care but it was clear that it had found something it wasn't sure and didn't have. Sadly a friend that uses various software packages but has from time to time had to test some things for his job has encountered this to. He knows what it is but it can get frustrating at times. One day he decided to take his work home with him and well norton did a number on the family computer killing many files, screwing up drives and the like. He lost a backup drive, his os drive and a data drive. He now uses a restricted account for home and work and his admin but things do from time to time appear so you are not alone with this stuff.
On 10/02/2020 3:45 pm, Quentin
Christensen wrote:
|
|
|
|
Robert Doc Wright godfearer
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 To: nvda@nvda.groups.io 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: https://www.nvaccess.org/post/nvda-2019-3rc3-now-available-for-testing/
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.
-- Quentin Christensen
NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
Web: www.nvaccess.org Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess
|
|
|
|
Rui Fontes
Normally that message is from Eloquence from CodeFactory...
Rui Fontes
Às 17:16 de 10/02/2020, Robert Doc
Wright godfearer escreveu:
|
|
|
|
Gene
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.
Gene ----- 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:
|
|
|
|
You probably have to register your synths again, however you may have lost an activation. Its why all my payed stuff is sapi.
On 11/02/2020 6:16 am, Robert Doc
Wright godfearer wrote:
|
|
|
|
Quentin Christensen
If you press NVDA+control+r three times quickly it should reset NVDA to factory defaults, which should revert to Windows OneCore voices. The other alternative, if everything is still working, just the synth not reading, is you could press NVDA+Control+s to open the synth settings dialog. From here you could press HOME to jump to the first option (eSpeak) or W for Windows OneCore and press ENTER - that way you won't lose any other settings.
On Tue, Feb 11, 2020 at 6:29 AM Shaun Everiss <sm.everiss@...> wrote:
--
Quentin Christensen Training and Support Manager NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/ Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess
|
|
|