Janet,

            I myself have learned, the hard way, that NVDA issues are not always, in reality, NVDA issues.  I've had plenty of thing end up being traceable to an add-on over time, and sometimes to one that's worked fine for ages as a change in something else triggers it to break.

            Hence, I suggest you take a look at:  The Most Basic Troubleshooting Steps for Suspected NVDA Issues
It will help you to figure out whether this is, in reality, an actual problem with the NVDA core code or if something else may be going on.
--

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

Any idiot can face a crisis. It's the day-to-day living that wears you out.

      ~ Anton Chekhov