NVDA and Office 365 Specifically Microsoft Word Editing Problem


Richard Wells
 

I am not sure when this started, but I believe it was upon the first
release of NVDA 2022.2. I wanted to see if anyone else reported it, but
no one has as far as I know. When I arrow around in Microsoft Word, NVDA
doesn't seem to track properly. It is even worse when attempting to
select text with SHIFT+ARROWS. I have done all the trouble-shooting I
know to do including Run COM Registration Fixing tool and restarting
with no change to the condition. NVDA use to be so good while editing
documents. Is there anything else I can try to get things working again
short of using JAWS with MS-Word? In case it helps, Word revision is
showing Microsoft Office version 16.0.15601.20148. the problem is the
same on Windows 10 and 11. In NVDA/settings/advanced, Use UI Automation
to access Microsoft Word document controls Always is set. Would changing
this setting help? If so, what setting should I choose?


 

Have you restarted NVDA with Add-Ons disabled then checking if the misbehavior persists?  If you haven't, you need to try that in an attempt to determine whether it may be an add-on, as opposed to NVDA core, that's triggering the issue.

Because no one else has reported this issue, I'm suspecting an add-on will end up being the root cause.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt


Richard Wells
 

Brian: I had not thought of disabling add-ons. I tried it and the
problem persists. Until someone else reports it or thinks of something
else to try, I will resort to JAWS. Thanks for the suggestion.


 

Richard,

Also, have you restarted the computer?  And I mean using Restart, as if Fast Startup is enabled a shut down is not really a shut down, but Restart forces Windows to reload from disk when it powers up again.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt


Richard Wells
 

Hi Brian: I always turn off fast startup and I have restarted computers. I am reproducing it on Windows 10 and 11. All ideas are welcome. Keep them coming.

On 9/20/2022 1:21 PM, Brian Vogel wrote:
Richard,

Also, have you restarted the computer?  And I mean using Restart, as if Fast Startup is enabled a shut down is not really a shut down, but Restart forces Windows to reload from disk when it powers up again.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt


Brian's Mail list account
 

Just a few random thoughts. Mouse, is there one? Whether it be real or a pad. Unlikely, but all sorts of oddities can occur. The fact that its on two machines makes me wonder if there might be some other piece of software only you are running that might be causing it.
Lastly, and I'm not sure how well this might work, if you run a clean download of nvda as a portable version from another folder, does the problem persist.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Richard Wells" <richwels@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, September 20, 2022 7:34 PM
Subject: Re: [nvda] NVDA and Office 365 Specifically Microsoft Word Editing Problem


Hi Brian: I always turn off fast startup and I have restarted computers.
I am reproducing it on Windows 10 and 11. All ideas are welcome. Keep
them coming.

On 9/20/2022 1:21 PM, Brian Vogel wrote:
Richard,

Also, have you restarted the computer? And I mean using Restart, as
if Fast Startup is enabled a shut down is not really a shut down, but
Restart forces Windows to reload from disk when it powers up again.
--

Brian -Windows 10, 64-Bit, Version 21H2, Build 19044

It is well to open one's mind but only as a preliminary to closing it
. . . for the supreme act of judgment and selection.

~ Irving Babbitt


 

Other things worth trying (on both systems):

1. Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8, 10 & 11

2. Completely uninstalling NVDA and reinstalling it (this should not cause loss of add-ons or settings, unless you were to deliberately nuke these yourself).

3. A repair install on Microsoft 365.

You could flip-flop steps 1 and 2, but number three should remain the last thing if one or both of the first two don't result in a change.

It would also be interesting to know whether the update to Windows 11 22H2 fixed anything there even without trying the above noted steps.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt


Richard Wells
 

Thanks for your persistence on this. I will try more of this and report back.

On 9/21/2022 10:13 AM, Brian Vogel wrote:
Other things worth trying (on both systems):

1. Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8, 10 & 11

2. Completely uninstalling NVDA and reinstalling it (this should not cause loss of add-ons or settings, unless you were to deliberately nuke these yourself).

3. A repair install on Microsoft 365.

You could flip-flop steps 1 and 2, but number three should remain the last thing if one or both of the first two don't result in a change.

It would also be interesting to know whether the update to Windows 11 22H2 fixed anything there even without trying the above noted steps.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt


Quentin Christensen
 

Hi Richard,

I don't have anything to add other than all the suggestions from Brian, but I haven't seen any other reports of this, so I'll be curious to find out what it is too.

Could you get me a copy of your NVDA log to have a look at please, ideally at debug level?
Please send it attached to an email to info@....  Include a description of what you have done and what isn't working as it should (so I know what it's about in case I don't get to investigate today).

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.log (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.


On Thu, Sep 22, 2022 at 1:57 AM Richard Wells <richwels@...> wrote:

Thanks for your persistence on this. I will try more of this and report back.

On 9/21/2022 10:13 AM, Brian Vogel wrote:
Other things worth trying (on both systems):

1. Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8, 10 & 11

2. Completely uninstalling NVDA and reinstalling it (this should not cause loss of add-ons or settings, unless you were to deliberately nuke these yourself).

3. A repair install on Microsoft 365.

You could flip-flop steps 1 and 2, but number three should remain the last thing if one or both of the first two don't result in a change.

It would also be interesting to know whether the update to Windows 11 22H2 fixed anything there even without trying the above noted steps.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

It is well to open one's mind but only as a preliminary to closing it . . . for the supreme act of judgment and selection.

       ~ Irving Babbitt



--
Quentin Christensen
Training and Support Manager