Can't uninstall NVDA 2021.2 from Windows 10 21h1


George McCoy
 

A friend of mine was upgrading from 2021.1 to 2021.2. He got an error saying the installation failed, after which neither version of NvDA runs in either the admin or user account.

Since NVDA does not run, I don't know how to look at the log to see if it still contains any information about the installation error.

I decided to try to completely uninstall NVDA and reinstall it. NVDA does not appear in the list of installed programs in settings or the control pannel

The NVDA folder and at least some of its files still exist in c:\Program Files (x86).

I ran the uninstall.exe program from there, but it did not uninstall the program.

Uninstall.exe said it was uninstalling nvda from folder. It showed a blank read only edit box

any suggestions would be greatly appreciated.


Thanks,

George


 

Please just upgrade to NVDA 2021.3.1, the most current release.

There were problems with updating both NVDA itself and NVDA Add-Ons during the 2021.1 and 2021.2 era that have all been resolved in 2021.3 and later.

If he really wants 2021.2, then still install 2021.3.1, uninstall it, and then install 2021.2.  The thing that gets fixed, that is causing the problem, is external to NVDA itself and once 2021.3 or later has been installed the issue vanishes even if you go back to an earlier release that was balking at installing.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

Many thanks, Brian. I'll do that.


George

On 1/12/2022 1:09 PM, Brian Vogel wrote:
Please just upgrade to NVDA 2021.3.1, the most current release.

There were problems with updating both NVDA itself and NVDA Add-Ons during the 2021.1 and 2021.2 era that have all been resolved in 2021.3 and later.

If he really wants 2021.2, then still install 2021.3.1, uninstall it, and then install 2021.2.  The thing that gets fixed, that is causing the problem, is external to NVDA itself and once 2021.3 or later has been installed the issue vanishes even if you go back to an earlier release that was balking at installing.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

Unfortunately, NVDA 2021.3.1,fails to install, just like 2021.2. Can anyone suggest a possible next step?


Thanks,

George

On 1/12/2022 1:09 PM, Brian Vogel wrote:
Please just upgrade to NVDA 2021.3.1, the most current release.

There were problems with updating both NVDA itself and NVDA Add-Ons during the 2021.1 and 2021.2 era that have all been resolved in 2021.3 and later.

If he really wants 2021.2, then still install 2021.3.1, uninstall it, and then install 2021.2.  The thing that gets fixed, that is causing the problem, is external to NVDA itself and once 2021.3 or later has been installed the issue vanishes even if you go back to an earlier release that was balking at installing.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

You need to supply error messages.

Failure to install is a completely different thing than failure to upgrade from within.

One thing I always suggest when any "weirdness" is occurring under Windows 8 or later is:  Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8 & 10

If you're still unable to install error messages from Windows would be the next thing an assistant would need to know.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

The trouble is, I'm not onsite so I can't see the error message and the owner is not at all competant when things get sticky.

He'll never get through DISM and SFC. I got a portable copy to work so I might be able to deploy the utilities through that.


Thanks for your help, though.

George


On 1/13/2022 9:42 AM, Brian Vogel wrote:
You need to supply error messages.

Failure to install is a completely different thing than failure to upgrade from within.

One thing I always suggest when any "weirdness" is occurring under Windows 8 or later is:  Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8 & 10

If you're still unable to install error messages from Windows would be the next thing an assistant would need to know.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

On Thu, Jan 13, 2022 at 01:31 PM, George McCoy wrote:
He'll never get through DISM and SFC.
-
If he can copy and paste, he can get through these.  There's nothing that the end user does but issue the commands and wait.

Being on the remote support end of things with a relatively tech-illiterate to tech-phobic client is no picnic!  I can relate.  But sometimes you just have to give them a push to do what you tell them and it works.  They tend to overthink and worry way too much that, "I can't."  Well, in my extensive experience, in almost all cases, "Yes, you can, and with just a bit of guidance and a smidge of trust."
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


mike mcglashon
 

Brian quoted:

Being on the remote support end of things with a relatively tech-illiterate to tech-phobic client is no picnic!  I can relate.  But sometimes you just have to give them a push to do what you tell them and it works.  They tend to overthink and worry way too much that, "I can't."  Well, in my extensive experience, in almost all cases, "Yes, you can, and with just a bit of guidance and a smidge of trust."

End quote:

 

Believe me, I am one of those tech illiterate guys who just has to trust what the doc says and do it;

As long as he tells me what buttons to push,

I am good;

But, … I still have to push the buttons to make it do what we want  it to do;

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 13, 2022 1:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Can't uninstall NVDA 2021.2 from Windows 10 21h1

 

On Thu, Jan 13, 2022 at 01:31 PM, George McCoy wrote:

He'll never get through DISM and SFC.

-
If he can copy and paste, he can get through these.  There's nothing that the end user does but issue the commands and wait.

Being on the remote support end of things with a relatively tech-illiterate to tech-phobic client is no picnic!  I can relate.  But sometimes you just have to give them a push to do what you tell them and it works.  They tend to overthink and worry way too much that, "I can't."  Well, in my extensive experience, in almost all cases, "Yes, you can, and with just a bit of guidance and a smidge of trust."
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

Hi all,

A few things come to my mind:

  1. User Account Control: usually there is a time limit when it comes to responding to UAC prompt. This happens when you install NVDA, too. If the user does not respond to UAC prompts, Windows will prevent NVDA from being installed and NVDA will report an error to that effect (the actual error is stored in NVDA log). This is a bit complicated if the system is part of a domain and a password is required to respond to UAC prompts. For consumers, responding to UAC is the best solution, but for enterprises, an IT professional should be contacted.
  2. Restarting the computer and transferring NVDA from portable copy to installed copy: this requires that a portable copy of NVDA is stored in an easy to access path (say, documents/NVDA folder). After restarting the computer, run the portable copy of NVDA and see if installation is possible (NVDA menu/Tools/Install). This is the method I personally use when installing NVDA on a new computer.
  3. File in use: sometimes some DLL's used by NVDA is used in other apps, particularly when interacting with 64-bit applications. IN this case, one way to resolve this is logging out and back in, as it then allows apps that are using some NVDA DLL's to terminate. Note that this procedure requires use of Narrator at the login screen, so for convenience, restart the computer.
  4. DISM might help but as a last resort: this assumes that it is more than just NVDA that is stuck.

Cheers,

Joseph


 

On Thu, Jan 13, 2022 at 02:09 PM, mike mcglashon wrote:
Please advise as you like.
-
What's to advise?  You'll do as you're told or you won't get my help, even when you're paying for it!!

[By the way, for those confused by the above:

1.  I know that "Please advise as you like" is a part of Mike's standard signature.
2.  Mike does precisely what he reports, and does as asked, even if he asks questions, and intelligent ones, before doing so.
3.  We have worked together on a paid professional basis, so he knows that the above is meant as an inside joke.

Now you all know.]
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

On Thu, Jan 13, 2022 at 03:09 PM, Joseph Lee wrote:
DISM might help but as a last resort: this assumes that it is more than just NVDA that is stuck.
-
While I absolutely agree with the latter, the use of DISM does assume that more than just NVDAmay be stuck, I vehemently disagree with the former.

Neither DISM nor SFC are, or can be, destructive.  I'm not saying anyone has to run them, or even that DISM needs to be run first, but not destructive "system scan and correct" utilities should never be feared nor considered "a last resort" simply because the worst they can do is nothing.  Often they do fix things you may have had no idea were wrong (and which, I'll admit, may not fix the issue that triggered you to run them in the first place).
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

Thank you very much, Joseph. I will try your suggestions. What is the NVDA log filespec?


George

On 1/13/2022 2:09 PM, Joseph Lee wrote:

Hi all,

A few things come to my mind:

  1. User Account Control: usually there is a time limit when it comes to responding to UAC prompt. This happens when you install NVDA, too. If the user does not respond to UAC prompts, Windows will prevent NVDA from being installed and NVDA will report an error to that effect (the actual error is stored in NVDA log). This is a bit complicated if the system is part of a domain and a password is required to respond to UAC prompts. For consumers, responding to UAC is the best solution, but for enterprises, an IT professional should be contacted.
  2. Restarting the computer and transferring NVDA from portable copy to installed copy: this requires that a portable copy of NVDA is stored in an easy to access path (say, documents/NVDA folder). After restarting the computer, run the portable copy of NVDA and see if installation is possible (NVDA menu/Tools/Install). This is the method I personally use when installing NVDA on a new computer.
  3. File in use: sometimes some DLL's used by NVDA is used in other apps, particularly when interacting with 64-bit applications. IN this case, one way to resolve this is logging out and back in, as it then allows apps that are using some NVDA DLL's to terminate. Note that this procedure requires use of Narrator at the login screen, so for convenience, restart the computer.
  4. DISM might help but as a last resort: this assumes that it is more than just NVDA that is stuck.

Cheers,

Joseph


 

Well I have had it where I have people that under do, they can't fix whatever so they give it to a friend to help.

That friend does in fact help, they read all the things on the net including all the adds and loads what looks cool.

Here is the thing.

What looks cool usually isn't necessarily cool.

Or they may load all sorts of things to fix 1 issue.

I had both cases.

The first one ended with a reformat because there was to much dammage to fix in a reasonable time.

The next almost did.

I had the thing sitting on a table cleaning junk and reinstalling security software and stuff.

I've had one repeat user and I have had worse than that though not recently.





On 14/01/2022 8:09 am, mike mcglashon wrote:

Brian quoted:

Being on the remote support end of things with a relatively tech-illiterate to tech-phobic client is no picnic!  I can relate.  But sometimes you just have to give them a push to do what you tell them and it works.  They tend to overthink and worry way too much that, "I can't."  Well, in my extensive experience, in almost all cases, "Yes, you can, and with just a bit of guidance and a smidge of trust."

End quote:

 

Believe me, I am one of those tech illiterate guys who just has to trust what the doc says and do it;

As long as he tells me what buttons to push,

I am good;

But, … I still have to push the buttons to make it do what we want  it to do;

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 13, 2022 1:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Can't uninstall NVDA 2021.2 from Windows 10 21h1

 

On Thu, Jan 13, 2022 at 01:31 PM, George McCoy wrote:

He'll never get through DISM and SFC.

-
If he can copy and paste, he can get through these.  There's nothing that the end user does but issue the commands and wait.

Being on the remote support end of things with a relatively tech-illiterate to tech-phobic client is no picnic!  I can relate.  But sometimes you just have to give them a push to do what you tell them and it works.  They tend to overthink and worry way too much that, "I can't."  Well, in my extensive experience, in almost all cases, "Yes, you can, and with just a bit of guidance and a smidge of trust."
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

Hi,

It is a typical text file - one can open the log by pressing NVDA+F1 (although that command is meant for developers, it has also found useful for troubleshooting, too).

Cheers,

Joseph


Arlene
 

Hi, there might be some other thing that might be stuck when you are trying to uninstall NVDA or whatever it is.  I had this happen when I tried to uninstall NVDA 2019 when my windows 7 was about to bite the dust. I was getting rid of things on there.  When I tried to uninstall NVDA. There were error messages. Don’t ask me what it was. I’ll make it up. It was something like 8554something something. I told the tec person at the source where I got this ten box. He knew what the errors were. He did fix something in the windows bios or some place.  He thanked me for telling him the error messages.  He did scrub the hard drive and recycled it. 

 

Sent from Mail for Windows

 

From: Brian Vogel
Sent: January 13, 2022 7:42 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Can't uninstall NVDA 2021.2 from Windows 10 21h1

 

You need to supply error messages.

Failure to install is a completely different thing than failure to upgrade from within.

One thing I always suggest when any "weirdness" is occurring under Windows 8 or later is:  Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 8 & 10

If you're still unable to install error messages from Windows would be the next thing an assistant would need to know.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

 


 

On Thu, Jan 13, 2022 at 06:08 PM, Arlene wrote:
Hi, there might be some other thing that might be stuck when you are trying to uninstall NVDA or whatever it is.
-
Indeed.  But the way to determine what those "some other things" might be is by analyzing error messages and/or logs.

As a general rule, always, you need to supply the specific error message text and/or codes when you get them.

Saying to a potential assistant, "I got an error message, can you fix it," is akin to telling someone who can't see you and has no idea where you are on the surface of the earth, "I live on land, can you find me."

Specificity is necessary, not optional, when tech solutions are being sought.  That's the point I'm trying to make.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

And a very good point it is, Brian.  Now that I know where the nvda.log file is written, I can try installing from the portable copy and, if it fails, hopefully, the error code will show up in the log file.


On 1/13/2022 5:20 PM, Brian Vogel wrote:
On Thu, Jan 13, 2022 at 06:08 PM, Arlene wrote:
Hi, there might be some other thing that might be stuck when you are trying to uninstall NVDA or whatever it is.
-
Indeed.  But the way to determine what those "some other things" might be is by analyzing error messages and/or logs.

As a general rule, always, you need to supply the specific error message text and/or codes when you get them.

Saying to a potential assistant, "I got an error message, can you fix it," is akin to telling someone who can't see you and has no idea where you are on the surface of the earth, "I live on land, can you find me."

Specificity is necessary, not optional, when tech solutions are being sought.  That's the point I'm trying to make.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


 

George,

           Did this issue ever reach the desired resolution?
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 


George McCoy
 

Hello Brian,


For my friend, the solution was surprisingly simple.  We ended up renaming c:\program files (X86)\nvda to c:\program files (X86)\old_nvda.

We then renamed all instances of appDada\roaming\nvda to AppData\old_nvda

At that point, we installed from a portable copy of NVDA 2021.3.1 checking the copy user configuration checkbox and everything came round right.

Not the most elligant solution, but it worked.


Thanks, everybody, for your help and great suggestions.


George

On 1/17/2022 11:50 AM, Brian Vogel wrote:
George,

           Did this issue ever reach the desired resolution?
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)