I would be inclined to agree, but only if the two things I suggested earlier, which are less aggressive, don't fix the issue: 1. Using SFC (System File Checker) and DISM (Deployment Imaging Servicing

Hi list I have continued to fiddle with the NVDA reenabling the winamp extention then removing it and reinstalling it but still it is as if NVDA can’t see. The functionality is still there but

I don’t know if its getting worse. I pressed windows x and nothing was announced. But it was there because I then pressed u then r and it restarted even though NVDA said not a word.

I’ll try it again. I ran it before with no noticeable results. ****** character is found in how you treat people who cannot do anything for you!

If the COM Registration Fixing tool doesn't work, then you've hit an issue that I reported a while ago but nobody fixed yet. Anyone who wants to walk him through fixing it search for mathplayer in

Run the COM Registration Fixing tool in the tools submenu of the NVDA menu. That may solve all your problems. It registers some dll files that may become unregistered for one reason or another and

I would be tempted to do a Windows Re-install with all these difficulties with the core functioning of my main screenreader. However assuming that you want to stick with your setup and do not want

I use the tree view to get to places quickly. Aside from drive C I have E, F, H, K, and N as well as needing to get to Dropbox quickly. Can you imagine all the backspacing I would have to do?

The problem still exists. I noticed that when I press windows +t to bring up the task bar it says unknown there too. I have done the following: Run restore Uninstalled NVDA Deleted the NVDA folder

Hi, Try the following in the order shown: Restart NVDA while focused on these apps. Restart the computer. Run “COM registration fixing tool” – NVDA menu/Tools/Run COM registration fixing tool

Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything. ****** character is found in how you treat

It isn’t a question of right or wrong. Your synthesizer may respond, or respond as you wish at fifthy percent. But Eloquence users would find fifthy percent to be very piercing and extremely

Its interesting. You have established that the tree view is workihng properlhy but that NVDA isn’t recognizing it. Are you pursuing this because you particularly want to use the tree view instead

Hi Maybe I've been doing it wrong all these years then. I use 50% to make it obvious because I find 30% can be indistinct in some cases. At least when Colin experiences the output for whatever

I checked the advance option in settings and the box was unchecked. I did look at what it offered but all it did was to cause me to scratch my head. So I turned it back off. ****** character is

Here is an update. I discovered that when I shift tab to where the tree view is suppose to be and I know the first two letters of where I am trying to get to I find I am in the correct place. Even

That is not correct. Fifty percent is extrremely too high pitched for some synthesizers. It may be alright for others. the default is 30 percent and I wouldn't assume that that is remotely correct

Hi Use NVDA+Control+k to open the Keyboard settings dialog and ensure the check box entitled "Beep if typing lowercase when caps lock is on" is checked. This will cause a beep to sound if you type a

Hi Have a look under the following 2 sections in nvda. Press the nvda key + letter N then go to preferences then right to settings then press the enter key. The

I suspect you are using the illegal add-on which isn’t supported on the list. the list can’t, for legal reasons, support oor assist in using such software. If you want Eloquence that functions