Topics

confused


Robert Doc Wright godfearer
 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 


David Griffith
 

This is very strange as it seems NVDA specific if Jaws is reading the tree view fine.

As a workaround you could consider using Explorer ++  as a temporary alternative to File Explorer. At least that will let you navigate between your different drives.

Explorer ++ can either replace File Explorer or work alongside it.

It is free and in many ways better than File Explorer anyway.

 

David Griffith

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: 26 December 2019 12:47
To: nvda@nvda.groups.io
Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 


Gene
 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 

As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used. 
I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.
 
]Gene

----- Original Message -----
Sent: Thursday, December 26, 2019 6:46 AM
Subject: [nvda] confused

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 


Gene
 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.
 
Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?
 
Gene

----- Original Message -----
From: Gene
Sent: Thursday, December 26, 2019 8:52 AM
Subject: Re: [nvda] confused

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 

As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used. 
I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.
 
]Gene
----- Original Message -----
Sent: Thursday, December 26, 2019 6:46 AM
Subject: [nvda] confused

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 


 

It could very easily be a small corruption in the Windows 10 installation that, for whatever reason, is only interacting with NVDA and not JAWS.

Any time you see strange issues such as this one, and particularly after a Windows Update, there are a number of steps you could take.  In this case I'd try the following two, in order, and if the first one fixes the issue then stop:

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


2. 
Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Most of the change we think we see in life is due to truths being in and out of favor.

         ~ Robert Frost, The Black Cottage (1914)

 

 


Nathaniel Kile
 

Hello Robert,
I am new to the list, however I am excited to be here and hope to be able to add my two pennies every now and then in a way that helps. So, I would maybe try to first restart File Explorer to see if that makes a difference at all, this is under your Task Manager with the show more option, arrow down to, "Windows Explorer," no, they haven't changed the name to File Explore, hit your application key and arrow down to restart. 
The other thing to check is if all of your screen resolutions and display settings are set to default.
Lastly, you can go into the Explorer settings and select explorer to open up in the Tree view when activated.
Regards,
Nate Kile


Robert Doc Wright godfearer
 

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 though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.

 

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 8:38 AM
To: Gene; nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.

 

Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?

 

Gene

----- Original Message -----

From: Gene

Sent: Thursday, December 26, 2019 8:52 AM

Subject: Re: [nvda] confused

 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 


As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used.  I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.

 

]Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 6:46 AM

Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

 


Robert Doc Wright godfearer
 

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 found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 8:38 AM
To: Gene; nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.

 

Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?

 

Gene

----- Original Message -----

From: Gene

Sent: Thursday, December 26, 2019 8:52 AM

Subject: Re: [nvda] confused

 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 


As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used.  I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.

 

]Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 6:46 AM

Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to     

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

 


Gene
 

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 of the list view or just as a matter of curiosity and interest? 
 
Gene

----- Original Message -----
Sent: Thursday, December 26, 2019 5:32 PM
Subject: Re: [nvda] confused
 

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 though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.

 

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 8:38 AM
To: Gene; nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.

 

Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?

 

Gene

----- Original Message -----

From: Gene

Sent: Thursday, December 26, 2019 8:52 AM

Subject: Re: [nvda] confused

 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 


As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used.  I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.

 

]Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 6:46 AM

Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to    

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

 


Robert Doc Wright godfearer
 

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 people who cannot do anything for you!                                                                       

 


 

Hi,

Try the following in the order shown:

  1. Restart NVDA while focused on these apps.
  2. Restart the computer.
  3. Run “COM registration fixing tool” – NVDA menu/Tools/Run COM registration fixing tool and follow the prompts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: Thursday, December 26, 2019 7:14 PM
To: nvda@nvda.groups.io
Subject: [nvda] more confusion

 

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 people who cannot do anything for you!                                                                       

 


Robert Doc Wright godfearer
 

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 in app-data\roaming

Downgraded to 2019.2

There is no change.

 

Is there something else I should have deleted after uninstalling to make sure NVDA was completely removed?

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Joseph Lee
Sent: Thursday, December 26, 2019 8:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] more confusion

 

Hi,

Try the following in the order shown:

  1. Restart NVDA while focused on these apps.
  2. Restart the computer.
  3. Run “COM registration fixing tool” – NVDA menu/Tools/Run COM registration fixing tool and follow the prompts.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: Thursday, December 26, 2019 7:14 PM
To: nvda@nvda.groups.io
Subject: [nvda] more confusion

 

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 people who cannot do anything for you!                                                                       

 

 


Robert Doc Wright godfearer
 

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?

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 5:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

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 of the list view or just as a matter of curiosity and interest? 

 

Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 5:32 PM

Subject: Re: [nvda] confused

 

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 though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.

 

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 8:38 AM
To: Gene; nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.

 

Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?

 

Gene

----- Original Message -----

From: Gene

Sent: Thursday, December 26, 2019 8:52 AM

Subject: Re: [nvda] confused

 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 


As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used.  I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.

 

]Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 6:46 AM

Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to    

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

 

 


David Griffith
 

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 to switch to using Explorer ++ the way I have coped with NVDA difficulties with File Explorer  in the past was to switch to Narrator with control windows enter  until NVDA started responding again.

The situation is better now but for a long time NVDA was pretty dreadful with File Explorer for me, taking ages and ages to recognise and respond to any files in a file explorer list.  Not just sluggish but completely unresponsive. In those situations I simply switched to Narrator and used that with File Explorer. Unlike NVDA Narrator would instantly start reading the necessary filenames as you cursor down.  I continued like this until NVDA decided to wake up again. As soon as NVDA was responding again I would turn Narrator off again with control windows enter and revert to using NVDA solely.

You could try the same approach with your File Explorer Drive tree.

David Griffith

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: 27 December 2019 07:28
To: nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

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?

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 5:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

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 of the list view or just as a matter of curiosity and interest? 

 

Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 5:32 PM

Subject: Re: [nvda] confused

 

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 though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.

 

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Thursday, December 26, 2019 8:38 AM
To: Gene; nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

I just looked at the setting in the advanced category.  I don't think it applies, but if the check box is checked, uncheck it.  I doubt you ever changed the setting but I was trying to think of something that might apply.

 

Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?

 

Gene

----- Original Message -----

From: Gene

Sent: Thursday, December 26, 2019 8:52 AM

Subject: Re: [nvda] confused

 

Is the item view the same as a list view?  If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens.  Simply back space to move up one level and press enter to open something like a drive or a folder. 


As to why the tree view isn't being read, I don't know, but I wonder if it has anything to do with the UIA setting being used.  I don't know where it is in NVDA, but there is a setting for using UIA or not using UIA.  What is it set for?  others can discuss that setting in more detail, I don't have Windows 10.

 

]Gene

----- Original Message -----

Sent: Thursday, December 26, 2019 6:46 AM

Subject: [nvda] confused

 

I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what  should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area.  The only major thing that I have done in this time period is to upgrade Windows to    

Version 1909 OS build 18365.535.

I am running the same version and build on the laptop but not having this problem in file explorer there.

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

 

 


Gene
 

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 which must be registered for NVDA to perform properly.
 
Gene
---[—Original Message -----

Sent: Thursday, December 26, 2019 9:13 PM
Subject: [nvda] more confusion
 

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 people who cannot do anything for you!                                                                       

 


Tyler Spivey
 

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 the issues and have at it.
I can't come up with a list of steps right now,
but I'm 99% sure that given the symptoms, that'll fix it.
The Python Console command in the issue description will work (as long as NVDA is elevated).

On Fri, Dec 27, 2019 at 04:19:35AM -0600, Gene wrote:
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 which must be registered for NVDA to perform properly.

Gene
---[—Original Message -----
From: Robert Doc Wright godfearer
Sent: Thursday, December 26, 2019 9:13 PM
To: nvda@nvda.groups.io
Subject: [nvda] more confusion

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 people who cannot do anything for you!






Robert Doc Wright godfearer
 

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!                                                                       

 

From: Gene
Sent: Friday, December 27, 2019 3:19 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] more confusion

 

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 which must be registered for NVDA to perform properly.

 

Gene

---[—Original Message -----

Sent: Thursday, December 26, 2019 9:13 PM

Subject: [nvda] more confusion

 

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 people who cannot do anything for you!                                                                       

 

 


Robert Doc Wright godfearer
 

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.

 

******

character is found in how you treat people who cannot do anything for you!                                                                       

 

From: Gene
Sent: Friday, December 27, 2019 3:19 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] more confusion

 

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 which must be registered for NVDA to perform properly.

 

Gene

---[—Original Message -----

Sent: Thursday, December 26, 2019 9:13 PM

Subject: [nvda] more confusion

 

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 people who cannot do anything for you!                                                                       

 

 


 

On Fri, Dec 27, 2019 at 05:14 AM, David Griffith wrote:
I would be tempted to do a Windows Re-install with all these difficulties with the core functioning of my main screenreader.
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 and Management) to Repair Windows 8 & 10 


2. 
Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

Everything that has been said in both topics related to this issue very directly suggest OS corruption, plain and simple.  The number and nature of the issues, which are atypical, are a big, red flag.

You can spend forever trying to determine what's wrong, and never get there, while using the above, followed by a completely clean reinstall if neither of those work, will get you back on track even if one has to reconfigure one's computer after a completely clean reinstall.

 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Most of the change we think we see in life is due to truths being in and out of favor.

         ~ Robert Frost, The Black Cottage (1914)

 

 


 

Hi,

Or perhaps a corrupt DLL registration, something Tyler talked about earlier as he noted a few moments ago, Let’s try that first, and if that doesn’t work, a restore is in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Friday, December 27, 2019 7:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] confused

 

On Fri, Dec 27, 2019 at 05:14 AM, David Griffith wrote:

I would be tempted to do a Windows Re-install with all these difficulties with the core functioning of my main screenreader.

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 and Management) to Repair Windows 8 & 10 


2. 
Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

Everything that has been said in both topics related to this issue very directly suggest OS corruption, plain and simple.  The number and nature of the issues, which are atypical, are a big, red flag.

You can spend forever trying to determine what's wrong, and never get there, while using the above, followed by a completely clean reinstall if neither of those work, will get you back on track even if one has to reconfigure one's computer after a completely clean reinstall.

 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Most of the change we think we see in life is due to truths being in and out of favor.

         ~ Robert Frost, The Black Cottage (1914)