1. Messages
  2. tracking down NVDA triggers

Re: tracking down NVDA triggers

John Isige
 

I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows. That's like, option number one? I also notice
there's no explanation whatsoever as to how we're supposedly concluding
this is a Windows issue worthy of some sort of reinstallation. I'm
sorry, this just seems irresponsible, even with things like the Windows
10 reset where you can reinstall but preserve files and data.


I don't know the answer, about how to chase it down from the logs, but
it seems to me a much more readily apparent answer is that another
program is running in the background and stealing focus, or making NVDA
think focus has changed. I don't see how it automatically means that
Windows itself has been corrupted in any way whatsoever.


Suppose for instance, there's a download manager running in the
background, and it flashes its window or such to get your attention. It
seems entirely possible to me that such a benign event could be
temporarily stealing NVDA's focus. I've had this occur before, often it
will repeatedly read the first item on the desktop, both with NVDA and
under NVDA remote. So far as I know, both of my machines are good in
terms of Windows, I'm not noticing any other issues whatsoever. It
happens so infrequently that I've never worried about it.

On 10/1/2019 9:17, Brian Vogel wrote:
Giles,

            There is likely some corruption in your Windows 10
installation itself that needs to be remedied.  The probability of
this being an NVDA-based issue is very small indeed, particularly if
you've already tried uninstalling NVDA and reinstalling it.


My standard advice, in virtually all cases, (and presuming any
potential infection has already been addressed, first) is trying the
following, in the order specified.  If the issue is fixed by option
one then there's no need to go further.  Stop whenever your issue is
fixed:

1. */Using SFC (System File Checker) and DISM (Deployment Imaging
Servicing and Management) to Repair Windows 8 & 10/*
<https://drive.google.com/uc?export=download&id=0B98uELZbPFnOc2l4M0Y1V3pkcGM>


2. */Doing a Windows 10 Repair Install or Feature Update Using the
Windows 10 ISO file/*
<https://drive.google.com/uc?export=download&id=1RZiHlLVtXewYBgoSvJNm9_08hj1tALPK>


3. Doing a completely clean reinstall (options *a* & *b* are
downloadable PDF files):

           a) */Completely Clean Win10 (Re)install Using MCT to
Download Win10 ISO File/*
<https://drive.google.com/uc?export=download&id=1hHoEnSz2YWHyztOO3ZjXtV2y4gQASoMR>

           b) */Completely Clean Win10 (Re)install Using MCT to Create
a Bootable USB Drive/*
<https://drive.google.com/uc?export=download&id=1cvsT64KAwz5ZJmiPfBQlUDBOoskb9dDO>

           c) */How to do a CLEAN Installation of Windows 10/*
<https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/>(/Tom’s
Hardware Forums/, with screen shots)

I */_never_/* choose the “/thermonuclear option/,” the completely
clean reinstall, until it's clear that this is the only viable option.
I hate having to go through all the work of reconfiguring a machine
from scratch if that can reasonably and safely be avoided.

__


--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

           ~ André Gide
Join {nvda@nvda.groups.io to automatically receive all group messages.