Haha, that's always the way :) I was going to say, if you had a way of reliably reproducing it, you could try disabling add-ons, then do that and see if it happens again - but if it doesn't happen all

Several. Nothing particularly unusual though. W10 App Essentials, Add-on Updater, Speech History, Bluetooth Audio, Add-on Documentation, Remote, Classic Selection, debugHelper, Dropbox, Easy Table

Interesting, I regularly restart NVDA and I don't recall ever seeing it from that. Do you have any add-ons?-- Quentin Christensen Training and Support Manager Web: www.nvaccess.org Training:

I'll get you one, but I must say that I have rarely NOT had this happen when doing an NVDA restart. It is just the way of things. Since it happens on all of my systems, I assumed it was an error with

It may be that sending a log to those who have the technical knowledge to understand it might give an answer. I'll let those who know about the way to have the log contain the information you want

I hope you will find the solution soon, try this addon, I’m bet you can do it more better then this Sent from Mail for Windows 10

Holy cow, this worked! The language was set to NE! Of all the silly little… Hahaha, thanks very much! That said, I also want to report that I ran the SFC scan, and it actually did find and fix some

If this turns out to be the case, and it turns out that editing the nvda.ini file is necessary, I'd be very curious to know that the "language =" line read before being edited to "language =

Hi, I think I know exactly what could have happened: if a system restart nor NVDA restart didn’t fix the problem and if this only affects NVDA interface, chances are that somehow NVDA’s interface

I am running windows 10, build 19041.450

This is generally caused by something closing NVDA unexpectedly, such as it crashing, or if you go to task manager and "End task" it. I haven't seen it when restarting or updating add-ons. I wonder

In this case, even if SFC comes back clean when run initially, still follow it up with a run of DISM as well. Also, what Windows are you running, version and build? -- Brian - Windows 10 Pro, 64-Bit,

OK, thanks. I’ll give that a shot as well.

Were I you, I'd try uninstalling NVDA first. Then following these instructions: Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10 Then

Thanks for this suggestion, but sadly it did not work. I ran the tool, restarted the whole system, and still have the same issue. Bah, I say. Bah.

Hi, Try using tskill to remove NVDA out of memory to see if it works. Press Windows r to get the run dialogue box and then type, tskill NVDA and press the enter key. Thanks, Jim

We're here :) Welcome, and do please let us know if there's anything we can help with. Quentin. -- Quentin Christensen Training and Support Manager Web: www.nvaccess.org Training:

Hi. Yeah, I get this sometimes usually on system startup. nvda control n will not work, menu up but not read hit it again, menu will go away but no read. Fix, wait for a bit and it

Hi Try the following first it is found under the tools then the menu you want is called Run COM Registration Fixing tool... Then follow the directions. If

I get this behavior not infrequently. They usually clean themselves up over time, but if you try to activate any of the ones that are "ghost icons" they disappear and do nothing. There's only ever