Date   
Re: NVDA Buzzing and Speaking in a Compressed Way During Keyboard Input on a Fast Laptop

Jackie
 

Hey Luke? The file gives an unsupported video format error.

My first thought is that you're running RealTeck & that you need an
updated driver. You've also got some audio software on there called
Nahemic, & it wants to optimize your audio experience. Do not, under
any circumstances, allow that, as I will guarantee-told you it will be
beyond suboptimal. It's kind of a b-word to navigate, too,
unfortunately, but it is actually text-based, so object nav & the tab
key are your friends.

I realize the whole situation is unacceptable, unfortunately, I'm kind
of committed till after New Year's day, so I'm not in a position to
give much more help than this at present. Hopefully, though, it's
enough to give you a nudge in the proper direction. If not, we can
hopefully get together on the 2nd & troubleshoot this.

On 12/27/19, Luke Davis <luke@...> wrote:
Hello

Today I acquired an MSI laptop. Intel I7 Hexacore 2.6 GHZ (4.5 burst), 32 GB

RAM, 64 bit.

I ran 2019.2.1 as a portable without problem, and installed 2019.3 beta.
Then I
updated from Windows 110 Home 1709 to 1809, and noticed the following weird

behavior. I subsequently updated to 1909, and nothing has changed.
I have never seen this before.

Using either ESpeak or OneCore, whenever I type quickly or move the mouse, I

find that speech either hangs up in bad robotic sounding buzzes, or gets
really
"small", like a munchkin version of the synth in use.

It is a bit hard to describe. So I made a small recording:
http://newanswertech.com/Weird-NVDA1.m4a

It happens always when I am typing quickly, or just moving quickly through a

file list with the arrow keys. As you can hear from the file, it even
happens
periodically when I am typing slowly.

This is really unacceptable.

I purged 2019.3 and installed 2019.2.1, but the same behavior continues.

If this were the old days, I would think there was some kind of IRQ conflict

between the keyboard and the audio subsystem.
It's been so long since I have had to solve that kind of problem though,
that
I'm not immediately sure how to diagnose it.

Any thoughts would be welcome.

Luke



--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com

NVDA Buzzing and Speaking in a Compressed Way During Keyboard Input on a Fast Laptop

Luke Davis
 

Hello

Today I acquired an MSI laptop. Intel I7 Hexacore 2.6 GHZ (4.5 burst), 32 GB RAM, 64 bit.

I ran 2019.2.1 as a portable without problem, and installed 2019.3 beta. Then I updated from Windows 110 Home 1709 to 1809, and noticed the following weird behavior. I subsequently updated to 1909, and nothing has changed.
I have never seen this before.

Using either ESpeak or OneCore, whenever I type quickly or move the mouse, I find that speech either hangs up in bad robotic sounding buzzes, or gets really "small", like a munchkin version of the synth in use.

It is a bit hard to describe. So I made a small recording:
http://newanswertech.com/Weird-NVDA1.m4a

It happens always when I am typing quickly, or just moving quickly through a file list with the arrow keys. As you can hear from the file, it even happens periodically when I am typing slowly.

This is really unacceptable.

I purged 2019.3 and installed 2019.2.1, but the same behavior continues.

If this were the old days, I would think there was some kind of IRQ conflict between the keyboard and the audio subsystem.
It's been so long since I have had to solve that kind of problem though, that I'm not immediately sure how to diagnose it.

Any thoughts would be welcome.

Luke

Re: confused

Kevin Cussick
 

You were asked to run the com registration tool and You did not do this.

On 27/12/2019 07:20, Robert Doc Wright godfearer wrote:
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 <mailto:@joslee>
*Sent: *Thursday, December 26, 2019 8:48 PM
*To: *nvda@nvda.groups.io <mailto: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!

Re: confused

hurrikennyandopo ...
 

Hi


I did have another problem that was simular but involved fire fox and thunder bird etc and was able to fix it.


Not sure but if you look at the following link at https://nvda.groups.io/g/nvda/topic/nvda_web_browser_problem/4415326?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,140,4415326



I give steps on how to fix it but because no one else really had the same problem I did not put it up on my website under trouble shooting.


Look for hurrikenny and opo or gene nz it is near the top with steps.


You may have to refresh me on what is happening.


Gene nz


On 28/12/2019 7:23 am, Brian Vogel wrote:
As to Tyler's earlier additional suggestion, the NVDA issue on GitHub that he originated on MathPlayer dates from approximately one year ago is:  COM Registration Fixing tool doesn't work

I remain unclear as to exactly what did end up working after having read through the topic.
--

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)

 

 

Re: confused

hurrikennyandopo ...
 

Hi


I am pretty sure when you uninstalled the maths player it uninstalled other stuff that if i remember right gave those similar results. Not sure if it is that ticket or not.


Was that around the time of the com fixing tool or earlier?


It was meant to have been fixed with the uninstall process.


I think at that time when you re installed maths player every thing went back to normal but sure was able to uninstall it at a later date with no problems?


Gene nz


On 28/12/2019 7:23 am, Brian Vogel wrote:
As to Tyler's earlier additional suggestion, the NVDA issue on GitHub that he originated on MathPlayer dates from approximately one year ago is:  COM Registration Fixing tool doesn't work

I remain unclear as to exactly what did end up working after having read through the topic.
--

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)

 

 

Re: winamp is invisible with extention

Gene
 

Did the older one work properly?  Is it still available? If you have to use it with an older version of NVDA, do you want or need the new version for any reason?  Just because there is an update to something doesn't necessarily mean you should use it and people would save themselves trouble if they didn't reflexively update everything just because an update is available.  If the new update does nothing you want, you may be better off leaving things as they are.
 
Gene

----- Original Message -----
Sent: Friday, December 27, 2019 1:27 PM
Subject: Re: [nvda] winamp is invisible with extention

Yeah, you need to alt tab a couple times and then it works doesn't seem to completely load the extention on launch of the player almost like its not in focus if an extention can be out of focus.



On 28/12/2019 4:56 am, ken lawrence via Groups.Io wrote:

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 arrowing up or down just see “list item. Insirt t does’t talk it can’t read anything on my computer with1.2 installed.  And I can’t mute or change volume or view how must time is left in a song without the winamp extention.  I can’t believe it’s just my computer.  Should I wait and update windows 10 to the 1909 version and then try it?  As mentioned it ca’t even tell me I’m sitting on winamp with the extention. If I prep a show in advance I like to use winamp because I have better control of hearing what sounds right with what.  I can’t believe it’s just me what is wrong with 1.2 winamp extention? 

 

Sent from Mail for Windows 10

 

Re: winamp is invisible with extention

 

Yeah, you need to alt tab a couple times and then it works doesn't seem to completely load the extention on launch of the player almost like its not in focus if an extention can be out of focus.



On 28/12/2019 4:56 am, ken lawrence via Groups.Io wrote:

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 arrowing up or down just see “list item. Insirt t does’t talk it can’t read anything on my computer with1.2 installed.  And I can’t mute or change volume or view how must time is left in a song without the winamp extention.  I can’t believe it’s just my computer.  Should I wait and update windows 10 to the 1909 version and then try it?  As mentioned it ca’t even tell me I’m sitting on winamp with the extention. If I prep a show in advance I like to use winamp because I have better control of hearing what sounds right with what.  I can’t believe it’s just me what is wrong with 1.2 winamp extention? 

 

Sent from Mail for Windows 10

 

Re: confused

Tyler Spivey
 

Sorry, it wasn't as obvious as I thought; that issue wasn't very clear.

I think this should be fixed in the tool, though; trying to walk someone through this can be difficult.

On Fri, Dec 27, 2019 at 10:41:31AM -0800, Brian Vogel wrote:
Tyler,

This is what's in the issue, and I quote:

" On my win10 machine, this python console command fixes it if NVDA is run as administrator, but I forgot exactly what it does. It seems to return an error, but I'm not sure how to turn the int back into a HRESULT. However, it doesn't work on the win7 VM:
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p, ur"c:\windows\syswow64\oleacc.dll", None) "

I'm sorry, but even as a computer geek with decades of experience it was not entirely clear to me under what conditions this worked, or didn't.  And I doubt that most readers here, including myself, have Python console expertise or even a moment's experience, which matters.
--

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)


Re: confused

 


To be honest, I have had issues with file explorer off and on with the windows 19xxx releases.

In 1909 its a hell of a lot better but its still about.

Its also happened on multiple computers not just yours.

I agree with the poster, a full reformat will probably make it go away though to be honest, I have been looking for a explorer replacement as I can't rely on it.

It choaks with folders with single files, folders more than 2-5 levels deep, or if you have 1 or 2 folders open and you transfer to a third or another folder on another drive.

It seems to half crash.

The only thing that saves me from doing anything really drastic is that bar times where I transfer stuff about which I do off and on the shell is not used much.

99.9% of the time, my daily work involves using programs on the system or directly doing stuff I know the paths for.

I don't need windows shell functions for most of my daily routeens.

When I am doing admin stuff I usually don't need the shell at all and if I do its 1 folder and 1 window only either a usb or a download but to be honest most of that I can do with stuff on the system which do not need me to go to folders.


On 27/12/2019 11:14 pm, 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.

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!                                                                       

 

 

 

Re: confused

 

Hi,

If this code works, it should let 32-bit apps use 32-bit Oleacc.dll by registering it.

Cheers,

Joseph

 

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

 

Tyler,

           This is what's in the issue, and I quote:

"On my win10 machine, this python console command fixes it if NVDA is run as administrator, but I forgot exactly what it does. It seems to return an error, but I'm not sure how to turn the int back into a HRESULT. However, it doesn't work on the win7 VM:
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p, ur"c:\windows\syswow64\oleacc.dll", None)
"

I'm sorry, but even as a computer geek with decades of experience it was not entirely clear to me under what conditions this worked, or didn't.  And I doubt that most readers here, including myself, have Python console expertise or even a moment's experience, which matters.
--

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)

 

 

Re: confused

 

Tyler,

           This is what's in the issue, and I quote:

"On my win10 machine, this python console command fixes it if NVDA is run as administrator, but I forgot exactly what it does. It seems to return an error, but I'm not sure how to turn the int back into a HRESULT. However, it doesn't work on the win7 VM:
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p, ur"c:\windows\syswow64\oleacc.dll", None)"

I'm sorry, but even as a computer geek with decades of experience it was not entirely clear to me under what conditions this worked, or didn't.  And I doubt that most readers here, including myself, have Python console expertise or even a moment's experience, which matters.
--

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)

 

 

Re: confused

Tyler Spivey
 

This Python console command, as it says in the issue:

import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p, ur"c:\windows\syswow64\oleacc.dll", None)</p>

I know from personal experience that at least that works.
Of course, you could reproduce the issue to figure out which one of the many suggestions actually fixes things.

On Fri, Dec 27, 2019 at 10:23:46AM -0800, Brian Vogel wrote:
As to Tyler's earlier additional suggestion, the NVDA issue on GitHub that he originated on MathPlayer dates from approximately one year ago is: COM Registration Fixing tool doesn't work ( https://github.com/nvaccess/nvda/issues/9039 )

I remain unclear as to exactly what did end up working after having read through the topic.
--

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)


Re: confused

 

As to Tyler's earlier additional suggestion, the NVDA issue on GitHub that he originated on MathPlayer dates from approximately one year ago is:  COM Registration Fixing tool doesn't work

I remain unclear as to exactly what did end up working after having read through the topic.
--

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)

 

 

Re: confused

Gene
 

I saw that but I thought you were sayng that you would repair Windows as a first option.  Evidently, you weren't saying that.
 
I don't recall what corrected the problem, though I recall seeing a message about it perhaps two days ago.
 
Gene

----- Original Message -----
----- Original Message -----
Sent: Friday, December 27, 2019 11:42 AM
Subject: Re: [nvda] confused

On Fri, Dec 27, 2019 at 12:14 PM, Gene wrote:
But running the registration fixing tool is fast and easy and would take much less time than the Windows correcting procedures.
Which, Gene, as I and the original poster have already stated, has been done, at least once and now possibly twice, to no effect.  See:  https://nvda.groups.io/g/nvda/message/68112 including the quote of Tyler's suggestion at the bottom.

Doing it again is not likely to have any effect.  We're now on to plans B, C, D, etc.
 
--

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)

 

 

Re: confused

 

On Fri, Dec 27, 2019 at 12:14 PM, Gene wrote:
But running the registration fixing tool is fast and easy and would take much less time than the Windows correcting procedures.
Which, Gene, as I and the original poster have already stated, has been done, at least once and now possibly twice, to no effect.  See:  https://nvda.groups.io/g/nvda/message/68112 including the quote of Tyler's suggestion at the bottom.

Doing it again is not likely to have any effect.  We're now on to plans B, C, D, etc.
 
--

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)

 

 

Re: confused

Jackie
 

Hey Robert, just for the halibut, does Narrator perform likewise?

On 12/27/19, Gene <gsasner@...> wrote:
But running the registration fixing tool is fast and easy and would take
much less time than the Windows correcting procedures.

If the problem were only the treeview, it would be unlikely to correct it,
but when browser problems that are typical of unregistered dll files started
to be discussed, then I think that should have been tried first.

Gene
Gene
----- Original Message -----
From: Brian Vogel
Sent: Friday, December 27, 2019 11:07 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] confused


On Fri, Dec 27, 2019 at 12:03 PM, Joseph Lee wrote:

I cannot discount Tyler’s comment though, as whatever he did cured it.
And I'm not, either, but I am always one who takes the "path of least
resistance" first. I've just seen too many problems, of too many varieties,
never be fixable except by trying to clean up Windows first, so I always do
that since it's simple. If that doesn't work then I'll go into under the
hood digging.

--

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)








--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com

Re: confused

Gene
 

But running the registration fixing tool is fast and easy and would take much less time than the Windows correcting procedures.
 
If the problem were only the treeview, it would be unlikely to correct it, but when browser problems that are typical of unregistered dll files started to be discussed, then I think that should have been tried first.
 
Gene
Gene

----- Original Message -----
Sent: Friday, December 27, 2019 11:07 AM
Subject: Re: [nvda] confused

On Fri, Dec 27, 2019 at 12:03 PM, Joseph Lee wrote:
I cannot discount Tyler’s comment though, as whatever he did cured it.
And I'm not, either, but I am always one who takes the "path of least resistance" first.  I've just seen too many problems, of too many varieties, never be fixable except by trying to clean up Windows first, so I always do that since it's simple.  If that doesn't work then I'll go into under the hood digging.
 
--

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)

 

 

Re: confused

 

On Fri, Dec 27, 2019 at 12:03 PM, Joseph Lee wrote:
I cannot discount Tyler’s comment though, as whatever he did cured it.
And I'm not, either, but I am always one who takes the "path of least resistance" first.  I've just seen too many problems, of too many varieties, never be fixable except by trying to clean up Windows first, so I always do that since it's simple.  If that doesn't work then I'll go into under the hood digging.
 
--

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)

 

 

Re: confused

 

Hi,

I cannot discount Tyler’s comment though, as whatever he did cured it.

Cheers,

Joseph

 

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

 

I have merged the "more confused" topic into this one as they are about one and the same machine and issue.

Joseph, the OP indicates they've tried the COM registration fixing tool with no change, but that was in the former "more confused" topic that's now merged with this one.

I stand by my suggestions at this juncture as appropriate first steps in light of the tool already having been run and failed.  Using SFC/DISM or doing a Repair Install risks nothing.  At worst it doesn't work.

--

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)

 

 

Re: confused

 

I have merged the "more confused" topic into this one as they are about one and the same machine and issue.

Joseph, the OP indicates they've tried the COM registration fixing tool with no change, but that was in the former "more confused" topic that's now merged with this one.

I stand by my suggestions at this juncture as appropriate first steps in light of the tool already having been run and failed.  Using SFC/DISM or doing a Repair Install risks nothing.  At worst it doesn't work.

--

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)