NVDA doesn't read context menu


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Hi,

After uninstall MS office, my NVDA doesn't read context menu.
Why and how to fix this?


Luke Davis
 

On Sun, 11 Apr 2021, 高生旺 wrote:

After uninstall MS office, my NVDA doesn't read context menu.
I should just have this tattooed on my head: run the COM Registration Fixing Tool. This is a textbook case of what it's for.
Press NVDA+n, t, r, enter. That's with an English keyboard setup, on English language NVDA.
Press Okay when prompted, and authenticate the Windows permission dialog which appears.
Press OK again when the completion Window comes up.

Luke

"In this life there are obstacles, and forces who overcome obstacles. You can be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Have done but no effect.

On Sun, 11 Apr 2021, Luke Davis wrote:

Date: Sun, 11 Apr 2021 01:32:08 -0400 (EDT)
From: Luke Davis <luke@newanswertech.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
On Sun, 11 Apr 2021, 高生旺 wrote:

After uninstall MS office, my NVDA doesn't read context menu.
I should just have this tattooed on my head: run the COM Registration Fixing Tool. This is a textbook case of what it's for.
Press NVDA+n, t, r, enter. That's with an English keyboard setup, on English language NVDA.
Press Okay when prompted, and authenticate the Windows permission dialog which appears.
Press OK again when the completion Window comes up.

Luke

"In this life there are obstacles, and forces who overcome obstacles. You can be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd





Chris
 

Did you restart after running the com registration tool?

 

If not, then do so!

 

 

From: 高生旺
Sent: 11 April 2021 07:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu

 

Have done but no effect.

 

On Sun, 11 Apr 2021, Luke Davis wrote:

 

> Date: Sun, 11 Apr 2021 01:32:08 -0400 (EDT)

> From: Luke Davis <luke@...>

> Reply-To: nvda@nvda.groups.io

> To: nvda@nvda.groups.io

> Subject: Re: [nvda] NVDA doesn't read context menu

>

> On Sun, 11 Apr 2021, 高生旺 wrote:

>> After uninstall MS office, my NVDA doesn't read context menu.

> I should just have this tattooed on my head: run the COM Registration Fixing

> Tool. This is a textbook case of what it's for.

> Press NVDA+n, t, r, enter. That's with an English keyboard setup, on English

> language NVDA.

> Press Okay when prompted, and authenticate the Windows permission dialog

> which appears.

> Press OK again when the completion Window comes up.

> Luke

> "In this life there are obstacles, and forces who overcome obstacles. You can

> be either one or the other.

> If you refuse to even try to clear an obstacle, you become the obstacle."

> - Joel Shepherd

>

 

 

 

 

 


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Still no effect. I must to re-install office or reset windows to fix it.

On Sun, 11 Apr 2021, Chris via groups.io wrote:

Date: Sun, 11 Apr 2021 08:41:27 +0100
From: Chris via groups.io <chrismedley=btinternet.com@groups.io>
Reply-To: nvda@nvda.groups.io
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA doesn't read context menu
Did you restart after running the com registration tool?
 
If not, then do so!
 
 
From: 高生旺
Sent: 11 April 2021 07:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
 
Have done but no effect.
 
On Sun, 11 Apr 2021, Luke Davis wrote:
 

Date: Sun, 11 Apr 2021 01:32:08 -0400 (EDT)
From: Luke Davis <luke@newanswertech.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
On Sun, 11 Apr 2021, 高生旺 wrote:
 
After uninstall MS office, my NVDA doesn't read context menu.
 
I should just have this tattooed on my head: run the COM Registration Fixing
Tool. This is a textbook case of what it's for.
Press NVDA+n, t, r, enter. That's with an English keyboard setup, on English
language NVDA.
Press Okay when prompted, and authenticate the Windows permission dialog
which appears.
Press OK again when the completion Window comes up.
 
Luke
 
"In this life there are obstacles, and forces who overcome obstacles. You can
be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd
 
 
 
 
 
 
 
 
 


Luke Davis
 

On Sun, 11 Apr 2021, 高生旺 wrote:

Have done but no effect.
Have you restarted the machine (actual windows restart, not turning off and on again)?

What version of NVDA and Windows?

Have you tried running NVDA with add-ons disabled?

Also, I know it seems silly, but try the COM Registration Fix tool again. I know of at least one case where a user reported that it didn't fix a problem it should have during the first run, but did after being run again. In theory that shouldn't be true, but that's what he reported.

--
Luke

"In this life there are obstacles, and forces who overcome obstacles. You can be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd


 

Others have already covered the items in #1 on this list, but I'm putting it here for completeness.  There is a pretty standard succession of things to try when any issue comes up, in order, depending on whether NVDA is involved or not.  If it's not, then skipping item #1 is fine.

1. The Most Basic Troubleshooting Steps for Suspected NVDA Issues
2. Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10
[Preferably before doing #3 and absolutely before doing #4, taking a full user data backup and a full system image backup is required.]
3. Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file
4. Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Fetch the Win10 ISO File
    (and since you will have already fetched the ISO file for step 3, you can begin in the instructions at the point immediately after it's been downloaded, or you can instead
     follow these instructions: Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Create Bootable Win10 Install Media on a USB Thumb Drive)
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

While checking log I got the messages:

Input: kb(desktop):applications
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (18:40:29.645) - MainThread (4772):
accRole failed: (-2147312566, 'An error occurred while loading the type library/DLL.', (None, None, None, 0, None))

On Sun, 11 Apr 2021, 高生旺 wrote:

Date: Sun, 11 Apr 2021 15:58:47 +0800 (CST)
From: 高生旺 <coscell@gmail.com>
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA doesn't read context menu
Still no effect. I must to re-install office or reset windows to fix it.

On Sun, 11 Apr 2021, Chris via groups.io wrote:

Date: Sun, 11 Apr 2021 08:41:27 +0100
From: Chris via groups.io <chrismedley=btinternet.com@groups.io>
Reply-To: nvda@nvda.groups.io
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA doesn't read context menu
Did you restart after running the com registration tool?
 
If not, then do so!
 
 
From: 高生旺
Sent: 11 April 2021 07:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
 
Have done but no effect.
 
On Sun, 11 Apr 2021, Luke Davis wrote:
 

Date: Sun, 11 Apr 2021 01:32:08 -0400 (EDT)
From: Luke Davis <luke@newanswertech.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
On Sun, 11 Apr 2021, 高生旺 wrote:
 
After uninstall MS office, my NVDA doesn't read context menu.
 
I should just have this tattooed on my head: run the COM Registration
Fixing

Tool. This is a textbook case of what it's for.
Press NVDA+n, t, r, enter. That's with an English keyboard setup, on
English

language NVDA.
Press Okay when prompted, and authenticate the Windows permission dialog
which appears.
Press OK again when the completion Window comes up.
 
Luke
 
"In this life there are obstacles, and forces who overcome obstacles. You
can

be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd
 
 
 
 
 
 
 
 
 


tim
 

Have you tried reinstalling your NVDA add-ons? There have ben a few updates in the past weeks and you may have corrupted on. I had that happen on 2003.

On 4/11/2021 8:08 AM, Luke Davis wrote:
On Sun, 11 Apr 2021, 高生旺 wrote:

Have done but no effect.
Have you restarted the machine (actual windows restart, not turning off and on again)?
What version of NVDA and Windows?
Have you tried running NVDA with add-ons disabled?
Also, I know it seems silly, but try the COM Registration Fix tool again. I know of at least one case where a user reported that it didn't fix a problem it should have during the first run, but did after being run again.  In theory that shouldn't be true, but that's what he reported.


 

On Mon, Apr 12, 2021 at 06:59 AM, =?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?= wrote:
While checking log I got the messages:
-
You know, several people now, including myself, have asked you to try several things, including starting with add-ons disabled, and reporting back.

Diagnosing issues is not a scattershot process, but a methodical one.

Have you done, IN ORDER, The Most Basic Troubleshooting Steps for Suspected NVDA Issues?

What is the result after trying each, IN ORDER?  And for restarting the computer definitely use Restart, not Shutdown, because if Fast Startup is enabled a shutdown is not really a complete shutdown.

If those don't work, then an uninstall and reinstall of NVDA would be what I'd try next.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Again, no effect with all you said.
The log message had said it is missing some dll.
Do you know which one?

On Mon, 12 Apr 2021, Brian Vogel wrote:

Date: Mon, 12 Apr 2021 08:25:19 -0700
From: Brian Vogel <britechguy@gmail.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
On Mon, Apr 12, 2021 at 06:59 AM, =?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?= wrote:
While checking log I got the messages:
-
You know, several people now, including myself, have asked you to try several things, including starting with add-ons disabled, and reporting back.
Diagnosing issues is not a scattershot process, but a methodical one.
Have you done, IN ORDER, The Most Basic Troubleshooting Steps for Suspected NVDA Issues?
What is the result after trying each, IN ORDER?  And for restarting the computer definitely use Restart, not Shutdown, because if Fast Startup is enabled a shutdown is not really a complete shutdown.
If those don't work, then an uninstall and reinstall of NVDA would be what I'd try next.
 
--
Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  
Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.
       ~ Richard M. Nixon
 


 

On Mon, Apr 12, 2021 at 09:35 PM, =?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?= wrote:
Do you know which one?
-
No.  But you show no indication of having uninstalled/reinstalled NVDA.  Have you?

You are not going to get additional help from me until and unless you start reporting on each and every step you've taken, and stopping after each to report the result. 

This grasping at straws, which is what you're doing, and zig-zagging is not helpful, to anyone, least of all you.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

I've remove nvda and re-install the newest alpha-22295,49a85788.
I still cannot read context menu.

On Mon, 12 Apr 2021, Brian Vogel wrote:

Date: Mon, 12 Apr 2021 18:47:10 -0700
From: Brian Vogel <britechguy@gmail.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
On Mon, Apr 12, 2021 at 09:35 PM, =?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?= wrote:
Do you know which one?
-
No.  But you show no indication of having uninstalled/reinstalled NVDA.  Have you?
You are not going to get additional help from me until and unless you start reporting on each and every step you've taken, and stopping after each to report the result. 
This grasping at straws, which is what you're doing, and zig-zagging is not helpful, to anyone, least of all you.
 
--
Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  
Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.
       ~ Richard M. Nixon
 


Gene
 

Did you run the registration tool again, as was suggested? If that doesn't work, do you have system restore points? Runnning a restore point from before you uninstalled Office will likely correct whatever problem the uninstallation caused. Then, regardless of wheteher Office programs work or not, leave them installed.

Gene

-----Original Message-----
From: 高生旺
Sent: Monday, April 12, 2021 9:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu

I've remove nvda and re-install the newest alpha-22295,49a85788.
I still cannot read context menu.

On Mon, 12 Apr 2021, Brian Vogel wrote:

Date: Mon, 12 Apr 2021 18:47:10 -0700
From: Brian Vogel <britechguy@gmail.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu

On Mon, Apr 12, 2021 at 09:35 PM, =?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?= wrote:
Do you know which one?

-
No. But you show no indication of having uninstalled/reinstalled NVDA. Have you?

You are not going to get additional help from me until and unless you start reporting on each and every step you've taken, and stopping after each to report the result.

This grasping at straws, which is what you're doing, and zig-zagging is not helpful, to anyone, least of all you.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win unless you hate them. And then you destroy yourself.

~ Richard M. Nixon






 

I would suggest not using the alpha.  Try installing 2020.4 and see if the issue persists.  Report back on if it does/does not.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


Luke Davis
 

I've remove nvda and re-install the newest alpha-22295,49a85788.
I still cannot read context menu.
Did you run SFC and DISM as Brian explained? Because it is sounding more and more like a Windows problem. But still run the COM Reg Fix Tool a second time.

--
Luke

"In this life there are obstacles, and forces who overcome obstacles. You can be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

I've done every thing you said.
I'm sure it's missing a dll.
I need to know which it is.

On Mon, 12 Apr 2021, Luke Davis wrote:

Date: Mon, 12 Apr 2021 23:26:27 -0400 (EDT)
From: Luke Davis <luke@newanswertech.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu

I've remove nvda and re-install the newest alpha-22295,49a85788.
I still cannot read context menu.
Did you run SFC and DISM as Brian explained? Because it is sounding more and more like a Windows problem. But still run the COM Reg Fix Tool a second time.

--
Luke

"In this life there are obstacles, and forces who overcome obstacles. You can be either one or the other.
If you refuse to even try to clear an obstacle, you become the obstacle."
- Joel Shepherd





Chris
 

It may be a good idea to install a stable version rather than using alphas, until the issue has been resolved

 

 

 

 

 

From: 高生旺
Sent: 13 April 2021 05:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu

 

I've done every thing you said.

I'm sure it's missing a dll.

I need to know which it is.

 

On Mon, 12 Apr 2021, Luke Davis wrote:

 

> Date: Mon, 12 Apr 2021 23:26:27 -0400 (EDT)

> From: Luke Davis <luke@...>

> Reply-To: nvda@nvda.groups.io

> To: nvda@nvda.groups.io

> Subject: Re: [nvda] NVDA doesn't read context menu

>

>> I've remove nvda and re-install the newest alpha-22295,49a85788.

>> I still cannot read context menu.

> Did you run SFC and DISM as Brian explained? Because it is sounding more and

> more like a Windows problem. But still run the COM Reg Fix Tool a second

> time.

> --

> Luke

> "In this life there are obstacles, and forces who overcome obstacles. You can

> be either one or the other.

> If you refuse to even try to clear an obstacle, you become the obstacle."

> - Joel Shepherd

>

 

 

 

 

 


Rowen Cary
 

In fact, this problem plagues many NVDA users, not only uninstalling Office, even if you uninstall Mathplayer, it will also cause this to happen.
I think the Com registration repair tool is not reliable. This requires improvement by NVAccess. The following may help you:
https://github.com/nvaccess/nvda/issues/2807#issuecomment-320149243


=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Hello Rowen

Thanks your help! You're right.

On Tue, 13 Apr 2021, Rowen Cary wrote:

Date: Tue, 13 Apr 2021 01:11:17 -0700
From: Rowen Cary <manchen_0528@outlook.com>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
In fact, this problem plagues many NVDA users, not only uninstalling Office, even if you uninstall Mathplayer, it will also cause this to happen.
I think the Com registration repair tool is not reliable. This requires improvement by NVAccess. The following may help you:
https://github.com/nvaccess/nvda/issues/2807#issuecomment-320149243