1. Topics
  2. Add-on Updater 21.10 (mandatory update) released

Add-on Updater 21.10 (mandatory update) released #addonrelease

Louise Pfau
 

Hi.  I received the notification to roll back to Add-on Updater 2021.09 after manually updating to 2021.10 as instructed at the beginning of this thread.  I just closed the notification.
 
Louise

Abdelrahman Osman
 

Hi Joseph,

  After entering the line, it does work as usual. I'm working with NVDA2021.2.

  Thanks!
Joseph Lee
 

Hi all,

Add-on Updater 21.10 is now being offered to Add-on Updater users. Note that if you still receive a message that says "error checking for add-on updates" when checking for add-on updates, you MUST install Add-on Updater 21.10 manually.

Cheers,

Joseph
Louise Pfau
 

When I checked for both add-on and NVDA updates, I got a message that none were available.  I’m using NVDA 2021.2.  I realized that I’d replied to the wrong thread last night when I indicated that I’d applied the python fix and installed the new add-on updater.  I don’t know if I was actually impacted in the way that some others were because I never received an error message, just the standard one saying that there were no updates.
 
Louise

Dan Beaver
 

It said that for me after installing the 21.10 update to the updater.  I did the check for add-on updates and got that message.


Dan Beaver

On 10/3/2021 12:33 AM, Ali Colak wrote:
  Hello,
I applied the mentioned fix, and while the addon updater checks for
updates, and I believe NVDA does the same, they do not say there are
no updates. All I see in that case is a close button. I am able to
infer that there are no updates obviously, but from previous
experience wouldn't it say, "there are no updates"?

On 10/2/21, Shaun Everiss <sm.everiss@...> wrote:

Well I submitted the python fix of yesterday to the forum and this
worked on my secondary network.

Saying that a lot on that forum, well some of them, aren't that smart,
there are a loot of crack hackers but there are also a lot of kids or at
least adults with kid brains that just do and say whatever.

I don't respond to much of it anymore.

Obviously that forum is where all the audiogame tests and stuff come
from so I do have a presence on there, but there are people that look
for trouble so I mostly keep it down.



On 3/10/2021 10:34 am, Joseph Lee wrote:

Hi,

I think I know the forum mentioned... Please tell folks there that, in
this case, downgrading may make things worse as the fix is unlikely to
be backported to older releases.

Cheers,

Joseph













.

-- 
Dan Beaver (KA4DAN)
Ali Colak
 

In addition to what I wrote above, I am running
Edition Windows 10 Home
Version 21H1
Installed on ‎11/‎16/‎2020
OS build 19043.1237
Experience Windows Feature Experience Pack 120.2212.3530.0

and
NVA 2021.2

On 10/3/21, Ali Colak via groups.io <alish54@...> wrote:
Hello,
I applied the mentioned fix, and while the addon updater checks for
updates, and I believe NVDA does the same, they do not say there are
no updates. All I see in that case is a close button. I am able to
infer that there are no updates obviously, but from previous
experience wouldn't it say, "there are no updates"?

On 10/2/21, Shaun Everiss <sm.everiss@...> wrote:
Well I submitted the python fix of yesterday to the forum and this
worked on my secondary network.

Saying that a lot on that forum, well some of them, aren't that smart,
there are a loot of crack hackers but there are also a lot of kids or at
least adults with kid brains that just do and say whatever.

I don't respond to much of it anymore.

Obviously that forum is where all the audiogame tests and stuff come
from so I do have a presence on there, but there are people that look
for trouble so I mostly keep it down.



On 3/10/2021 10:34 am, Joseph Lee wrote:

Hi,

I think I know the forum mentioned... Please tell folks there that, in
this case, downgrading may make things worse as the fix is unlikely to
be backported to older releases.

Cheers,

Joseph
Ali Colak
 

Hello,
I applied the mentioned fix, and while the addon updater checks for
updates, and I believe NVDA does the same, they do not say there are
no updates. All I see in that case is a close button. I am able to
infer that there are no updates obviously, but from previous
experience wouldn't it say, "there are no updates"?

On 10/2/21, Shaun Everiss <sm.everiss@...> wrote:
Well I submitted the python fix of yesterday to the forum and this
worked on my secondary network.

Saying that a lot on that forum, well some of them, aren't that smart,
there are a loot of crack hackers but there are also a lot of kids or at
least adults with kid brains that just do and say whatever.

I don't respond to much of it anymore.

Obviously that forum is where all the audiogame tests and stuff come
from so I do have a presence on there, but there are people that look
for trouble so I mostly keep it down.



On 3/10/2021 10:34 am, Joseph Lee wrote:

Hi,

I think I know the forum mentioned... Please tell folks there that, in
this case, downgrading may make things worse as the fix is unlikely to
be backported to older releases.

Cheers,

Joseph
Shaun Everiss
 

Well I submitted the python fix of yesterday to the forum and this worked on my secondary network.

Saying that a lot on that forum, well some of them, aren't that smart, there are a loot of crack hackers but there are also a lot of kids or at least adults with kid brains that just do and say whatever.

I don't respond to much of it anymore.

Obviously that forum is where all the audiogame tests and stuff come from so I do have a presence on there, but there are people that look for trouble so I mostly keep it down.



On 3/10/2021 10:34 am, Joseph Lee wrote:

Hi,

I think I know the forum mentioned... Please tell folks there that, in this case, downgrading may make things worse as the fix is unlikely to be backported to older releases.

Cheers,

Joseph
Joseph Lee
 

Hi,

I think I know the forum mentioned... Please tell folks there that, in this case, downgrading may make things worse as the fix is unlikely to be backported to older releases.

Cheers,

Joseph
Shaun Everiss
 

You just hit enter jean.

you will get no indication its worked exactly but then it just does so it works.



On 3/10/2021 3:05 am, Gene wrote:

After we enter the text, do we just leave it there or is there a save or execute command?
 
Gene
-----Original Message-----
From: Joseph Lee
Sent: Saturday, October 02, 2021 8:58 AM
Subject: Re: [nvda] Add-on Updater 21.10 (mandatory update) released #AddonRelease
 

Hi,

To resolve the error message when checking for updates to NVDA itself, try:

  1. Open Python Console (Control+NVDA+Z).
  2. Enter the following AS EXACTLY AS SHOWN:

import updateCheck; updateCheck._updateWindowsRootCertificates()

In order to verify that this issue is specific to NVDA 2021.2, please tell us which NVDA version you are using (please don't say "I'm using the latest version" because "latest version" can mean 2021.2, whatever version you might be using, or the latest alpha build). Thanks.

Cheers,

Joseph
Shaun Everiss
 

Well using the python import line mentioned yesterday has fixed both so maybe thats another alternitive to that also.

On a forum I use audiogames they are having issues with some addons and a few people think to just downgrade nvda so who knows.



On 3/10/2021 2:38 am, Gene wrote:

That’s what I would expect since they aren’t related.  Changing one doesn’t change the other. 
 
It works here, too.
 
Gene
-----Original Message-----
From: Don H
Sent: Saturday, October 02, 2021 8:35 AM
Subject: Re: [nvda] Add-on Updater 21.10 (mandatory update) released #AddonRelease
 
This did indeed fix the checking for addon updates under the tool menu
of the NVDA UI.  Checking for a NVDA update under the help menu still
causes a error message.

On 10/2/2021 8:21 AM, Joseph Lee wrote:
> Hi all,
>
> First, thank you for reporting add-on update error messages. The issue
> was traced to NVDA not looking for the correct SSL error, possibly
> caused by expired root certificate from Let’s Encrypt. As a result,
> Add-on Updater 21.10 was just released (manual download for now):
>
> https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon
> <https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon>
>
> IMPORTANT: Add-on Updater 21.10 is a MANDATORY update to anyone using
> NVDA 2021.1 or later. I cannot backport this to earlier NVDA releases as
> the add-on uses features introduced in NVDA 2021.1.
>
> In addition to fixing SSL certificate verification error, Add-on Updater
> 21.10 makes it possible to check for add-on updates after you perform a
> clean Windows installation without connecting to the Internet and then
> go online afterwards. This change comes from upcoming NVDA 2021.3 (alpha
> snapshots at the moment).
>
> I advise applying this update as soon as possible – for now after
> installing Add-on Updater 21.10, ignore an offer from Add-on Updater to
> install Add-on Updater 21.09 – I will update this thread once Add-on
> Updater 21.10 is indeed offered.
>
> Cheers,
>
> Joseph
>
>




Dan Beaver
 

Thank you Joseph,  the version you told us about fixes this problem on my system.  I hope it fixes it for all.


Dan Beaver

On 10/2/2021 12:21 PM, Chris via groups.io wrote:

 

And a big thank you to Joseph for his quick response in releasing a resolution to this issue

 

Thank you

 

 

From: Joseph Lee
Sent: 02 October 2021 14:21
To: nvda@nvda.groups.io
Subject: [nvda] Add-on Updater 21.10 (mandatory update) released #AddonRelease

 

Hi all,

First, thank you for reporting add-on update error messages. The issue was traced to NVDA not looking for the correct SSL error, possibly caused by expired root certificate from Let’s Encrypt. As a result, Add-on Updater 21.10 was just released (manual download for now):

https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon

 

IMPORTANT: Add-on Updater 21.10 is a MANDATORY update to anyone using NVDA 2021.1 or later. I cannot backport this to earlier NVDA releases as the add-on uses features introduced in NVDA 2021.1.

 

In addition to fixing SSL certificate verification error, Add-on Updater 21.10 makes it possible to check for add-on updates after you perform a clean Windows installation without connecting to the Internet and then go online afterwards. This change comes from upcoming NVDA 2021.3 (alpha snapshots at the moment).

 

I advise applying this update as soon as possible – for now after installing Add-on Updater 21.10, ignore an offer from Add-on Updater to install Add-on Updater 21.09 – I will update this thread once Add-on Updater 21.10 is indeed offered.

Cheers,

Joseph

 

-- 
Dan Beaver (KA4DAN)
Gene
 

I don’t know if there is anything to do but use Firefox for sites you can’t open in Chrome-based browsers.  If your Windows is up-to-date with all updates available before support ended, there may be nothing else that can be done. 
 
Chrome-based browsers and browsers in general rely on Windows itself for verification that sites are ;properly certified.  Firefox has its own certificates and is unusual among browsers.
Gene

-----Original Message-----
Sent: Saturday, October 02, 2021 11:42 AM
Subject: Re: [nvda] Add-on Updater 21.10 (mandatory update) released #AddonRelease
 
I've also tried to open www.nvaccess.org via Chrome and Opera, but to no
avail. Both are up-to-date. Firefox fires it up at once. I'm asking
myself what steps to take due to the fact that I've been using Windows 7
SP1. Am I supposed to do something about it myself? If yes, what? If no,
I'd be glad because I'm not as computer savvy as Joseph and those like
him. 🤣

On 02/10/2021 15:35, Don H wrote:
> This did indeed fix the checking for addon updates under the tool menu
> of the NVDA UI.  Checking for a NVDA update under the help menu still
> causes a error message.
>
> On 10/2/2021 8:21 AM, Joseph Lee wrote:
>> Hi all,
>>
>> First, thank you for reporting add-on update error messages. The issue
>> was traced to NVDA not looking for the correct SSL error, possibly
>> caused by expired root certificate from Let’s Encrypt. As a result,
>> Add-on Updater 21.10 was just released (manual download for now):
>>
>> https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon
>>
>> <https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon>
>>
>>
>> IMPORTANT: Add-on Updater 21.10 is a MANDATORY update to anyone using
>> NVDA 2021.1 or later. I cannot backport this to earlier NVDA releases as
>> the add-on uses features introduced in NVDA 2021.1.
>>
>> In addition to fixing SSL certificate verification error, Add-on Updater
>> 21.10 makes it possible to check for add-on updates after you perform a
>> clean Windows installation without connecting to the Internet and then
>> go online afterwards. This change comes from upcoming NVDA 2021.3 (alpha
>> snapshots at the moment).
>>
>> I advise applying this update as soon as possible – for now after
>> installing Add-on Updater 21.10, ignore an offer from Add-on Updater to
>> install Add-on Updater 21.09 – I will update this thread once Add-on
>> Updater 21.10 is indeed offered.
>>
>> Cheers,
>>
>> Joseph
>>
>>
>
>
>
>
>
> .

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Joseph Lee
 

Hi,

Firefox works because it comes with its own set of security certificates and doesn't rely on Windows to provide such information (the ultimate cause is Windows not being aware of expired certificate, and NVDA is involved because it fails to check the actual error in question). As for relationship with Windows 7, it was established (from some reports) that this is occurring across Windows releases (I do know that some folks will advise you to upgrade to Windows 10, but it is not for me to advise this as part of this thread).

Cheers,

Joseph
Joseph Lee
 

Hi,

I see. The next step then is a debug log from people experiencing it (ideally attached as part of a GitHub issue comment, but since not everyone has a GitHub account...).

Can people try doing a data analysis based on information we get from users - NVDA versions in use, debug log analysis, etc.?

Cheers,

Joseph
Dejan Ristic
 

I've also tried to open www.nvaccess.org via Chrome and Opera, but to no avail. Both are up-to-date. Firefox fires it up at once. I'm asking myself what steps to take due to the fact that I've been using Windows 7 SP1. Am I supposed to do something about it myself? If yes, what? If no, I'd be glad because I'm not as computer savvy as Joseph and those like him. 🤣

On 02/10/2021 15:35, Don H wrote:
This did indeed fix the checking for addon updates under the tool menu
of the NVDA UI.  Checking for a NVDA update under the help menu still
causes a error message.

On 10/2/2021 8:21 AM, Joseph Lee wrote:
Hi all,

First, thank you for reporting add-on update error messages. The issue
was traced to NVDA not looking for the correct SSL error, possibly
caused by expired root certificate from Let’s Encrypt. As a result,
Add-on Updater 21.10 was just released (manual download for now):

https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon
<https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon>

IMPORTANT: Add-on Updater 21.10 is a MANDATORY update to anyone using
NVDA 2021.1 or later. I cannot backport this to earlier NVDA releases as
the add-on uses features introduced in NVDA 2021.1.

In addition to fixing SSL certificate verification error, Add-on Updater
21.10 makes it possible to check for add-on updates after you perform a
clean Windows installation without connecting to the Internet and then
go online afterwards. This change comes from upcoming NVDA 2021.3 (alpha
snapshots at the moment).

I advise applying this update as soon as possible – for now after
installing Add-on Updater 21.10, ignore an offer from Add-on Updater to
install Add-on Updater 21.09 – I will update this thread once Add-on
Updater 21.10 is indeed offered.

Cheers,

Joseph




.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Chris
 

 

And a big thank you to Joseph for his quick response in releasing a resolution to this issue

 

Thank you

 

 

From: Joseph Lee
Sent: 02 October 2021 14:21
To: nvda@nvda.groups.io
Subject: [nvda] Add-on Updater 21.10 (mandatory update) released #AddonRelease

 

Hi all,

First, thank you for reporting add-on update error messages. The issue was traced to NVDA not looking for the correct SSL error, possibly caused by expired root certificate from Let’s Encrypt. As a result, Add-on Updater 21.10 was just released (manual download for now):

https://github.com/josephsl/addonUpdater/releases/download/21.10/addonUpdater-21.10.nvda-addon

 

IMPORTANT: Add-on Updater 21.10 is a MANDATORY update to anyone using NVDA 2021.1 or later. I cannot backport this to earlier NVDA releases as the add-on uses features introduced in NVDA 2021.1.

 

In addition to fixing SSL certificate verification error, Add-on Updater 21.10 makes it possible to check for add-on updates after you perform a clean Windows installation without connecting to the Internet and then go online afterwards. This change comes from upcoming NVDA 2021.3 (alpha snapshots at the moment).

 

I advise applying this update as soon as possible – for now after installing Add-on Updater 21.10, ignore an offer from Add-on Updater to install Add-on Updater 21.09 – I will update this thread once Add-on Updater 21.10 is indeed offered.

Cheers,

Joseph

 
Don H
 

The dialog box says Error checking for updates and there is a OK button

On 10/2/2021 10:37 AM, Joseph Lee wrote:
Hi,
I see. If so, what is the exactly message you hear? If it says "no update available", then you are fine as 2021.2 is the latest release.
Cheers,
Joseph
Joseph Lee
 

Hi,

I see. If so, what is the exactly message you hear? If it says "no update available", then you are fine as 2021.2 is the latest release.

Cheers,

Joseph
Don H
 

Sorry I forgot to provide that info. I am running NVDA 2021-2.

On 10/2/2021 10:04 AM, Joseph Lee wrote:
Hi,
I see. At least this confirms that NVDA itself is not detecting the correct error when checking for updates. Are you prehaps using NVDA 2021.1? If so, this explains the situationa bit more clearly.
Cheers,
Joseph
1 - 20 of 30