Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)
toggle quoted messageShow quoted text
If NVDA starts after logon even if disabled following Win 10 1903 update, here is a work around script :
This script needs to be copied in the scratchpad\globalPlugins directory after having active the scratchpad option (if required).
This script does not fixes the issue but unloads NVDA if it was not configured to start after logon.
Feedback welcomed although it is a “quick dirty script”.
I do not plan to release it as an addon, unless there is a demand.
De : email@example.com <firstname.lastname@example.org> De la part de Cyrille via Groups.Io
Reading the ticket, I have understood that :
Thank you for this information, that you also wrote in the ticket.
Since the fix will not be provided by MS before 2020, I intend to develop this workaround so that my wife does not have to quit NVDA (or forget to do it) each time she starts her session.
Seems that I still just need to figure if current NVDA version was run with the --ease-of-access flag. Is there an internal variable for it ? Or should I deal with NVDA process command line ?
Hi. My copy of NVDA running on Windows 10 1903 is not subject to this fault. It might be that I have Jaws running as the default startup screen reader, but as of now, NVDA will not start on my desktop unless I explicitly tell it to do so with the usual alt+ctrl+n. Cheers!
On 8/19/2019 11:22 PM, Joseph Lee wrote: