On Sun, Apr 12, 2020 at 07:11 PM, Joseph Lee wrote:

I advise not advertising beta software

Not to mention that the beta won't be picked up by the check for updates feature (NVDA+N,H,C) in a production release.

I can't imagine why NVDA 2019.3 would not pick up on 2019.3.1 unless it was already offered in the last 24 hours and declined.  I seem to recall that if you decline it sets some sort of flag that won't offer the update again until the following day.  If the same flag is also checked by Check for Updates and happens to be set, that might do it.

Joseph, I imagine you might be able to confirm or refute my speculation and if so, please do so.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

Hi Joseph,

I am wondering. I almost never get the full installer from the website now that you have the automatic updater which prompts you with every new release.  As per your description, I was able to find the updates folder under program files (x86)\NVDA \systemConfig folder structure. If when I am prompted to update NVDA, I should choose the later option and then go and copy the file from the updates folder and leave the original in that folder, would that interfere with the automatic updates when a few minutes later, I chose to install the update?  If not, that's a nice way to get the original installer in the event that you have a system crash where a reformat is necessary.

Hi,

If you tell NVDA to remind you later, it will remind you of an update later.

Technical: the following goes into how NVDA update actually takes place (a bit geeky):

The NVDA updater component will check for, download, and apply NVDA updates. This is divided into the following parts:

• Update checker: this component will access NVDA update server and will fetch update information based on certain details about your machine such as Windows version, processor architecture, NVDA version you’ve got and what not.
• The NVDA update check interface that presents the actual update check dialog.
• Update downloader: this component consists of a file transfer agent and the user interface to report download progress.
• NVDA installer: updates NVDA given specific flags.
• Update check timer: a timer that will activate the components above every 24 hours if NVDA is told to check for updates automatically.
• Update check database: a Python-specific data file (a pickle file) that records the last update check timestamp, the update version presented, pending update installer file (if this is such a case) and other settings.

 

When you or NVDA check for updates:

1. NVDA will access its own update server hosted on nvaccess.org.
2. NVDA will pass on information about your NVDA installation such as whether it is an installed copy, Windows version, processor architecture, NVDA version, and if you enabled them, information about current speech synthesizer and braille display in use and other various information used for collecting statistics.
3. NV Access server will then present either a dictionary-like data detailing any updates it finds, the download URL for the update so the update download agent can fetch it, the hash of the update file and other information. Alternatively, NV Access will say nothing (returns empty data), which means there is no update.
4. NVDA will then present the appropriate message (update is ready or no update).
5. If you do choose to download the update, after presenting the donation screen, the update download agent will download the update file, periodically letting NVDA know the transfer progress.
6. If you do decide to be reminded, NVDA will not remind you for a while.
7. After downloading (i.e. transferring) the update file, NVDA will ask if you would like to install now or do it later.
8. If you do choose to install then, the just downloaded NVDA installer will run with special flags, telling it to update NVDA.
9. If you choose to install the update later, it’ll save the downloaded installer to a special folder named “updates” inside user configuration folder and will add an option to exit NVDA dialog, which will let you install NVDA whenever you are ready.

 

Cheers,

Joseph

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, April 12, 2020 4:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I'm not able to update to the latest version of nvda!

 

On Sun, Apr 12, 2020 at 07:11 PM, Joseph Lee wrote:

I advise not advertising beta software

Not to mention that the beta won't be picked up by the check for updates feature (NVDA+N,H,C) in a production release.

I can't imagine why NVDA 2019.3 would not pick up on 2019.3.1 unless it was already offered in the last 24 hours and declined.  I seem to recall that if you decline it sets some sort of flag that won't offer the update again until the following day.  If the same flag is also checked by Check for Updates and happens to be set, that might do it.

Joseph, I imagine you might be able to confirm or refute my speculation and if so, please do so.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 

-- 

They Ask Me If I'm Happy; I say Yes.

They ask: "How Happy are You?"

I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"

Hi,

If you tell NVDA to remind you later, it will remind you of an update later.

Technical: the following goes into how NVDA update actually takes place (a bit geeky):

The NVDA updater component will check for, download, and apply NVDA updates. This is divided into the following parts:

• Update checker: this component will access NVDA update server and will fetch update information based on certain details about your machine such as Windows version, processor architecture, NVDA version you’ve got and what not.
• The NVDA update check interface that presents the actual update check dialog.
• Update downloader: this component consists of a file transfer agent and the user interface to report download progress.
• NVDA installer: updates NVDA given specific flags.
• Update check timer: a timer that will activate the components above every 24 hours if NVDA is told to check for updates automatically.
• Update check database: a Python-specific data file (a pickle file) that records the last update check timestamp, the update version presented, pending update installer file (if this is such a case) and other settings.

When you or NVDA check for updates:

1. NVDA will access its own update server hosted on nvaccess.org.
2. NVDA will pass on information about your NVDA installation such as whether it is an installed copy, Windows version, processor architecture, NVDA version, and if you enabled them, information about current speech synthesizer and braille display in use and other various information used for collecting statistics.
3. NV Access server will then present either a dictionary-like data detailing any updates it finds, the download URL for the update so the update download agent can fetch it, the hash of the update file and other information. Alternatively, NV Access will say nothing (returns empty data), which means there is no update.
4. NVDA will then present the appropriate message (update is ready or no update).
5. If you do choose to download the update, after presenting the donation screen, the update download agent will download the update file, periodically letting NVDA know the transfer progress.
6. If you do decide to be reminded, NVDA will not remind you for a while.
7. After downloading (i.e. transferring) the update file, NVDA will ask if you would like to install now or do it later.
8. If you do choose to install then, the just downloaded NVDA installer will run with special flags, telling it to update NVDA.
9. If you choose to install the update later, it’ll save the downloaded installer to a special folder named “updates” inside user configuration folder and will add an option to exit NVDA dialog, which will let you install NVDA whenever you are ready.

Cheers,

Joseph

On Sun, Apr 12, 2020 at 07:11 PM, Joseph Lee wrote:

I advise not advertising beta software

Not to mention that the beta won't be picked up by the check for updates feature (NVDA+N,H,C) in a production release.

I can't imagine why NVDA 2019.3 would not pick up on 2019.3.1 unless it was already offered in the last 24 hours and declined.  I seem to recall that if you decline it sets some sort of flag that won't offer the update again until the following day.  If the same flag is also checked by Check for Updates and happens to be set, that might do it.

Joseph, I imagine you might be able to confirm or refute my speculation and if so, please do so.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

-----Original Message-----
From: Chris Mullins
Sent: Apr 13, 2020 5:05 AM
To: "nvda@nvda.groups.io"
Subject: Re: [nvda] I'm not able to update to the latest version of nvda!

Hi

To check what version of NVDA is running, press NVDA+n to open the NVDA menu then press t followed by v to view the NVDA log.  The second line of the log file tells you what NVDA version is currently loaded.

 

Cheers

Chris

 

From: Joseph Lee
Sent: 13 April 2020 01:01
To: nvda@nvda.groups.io
Subject: Re: [nvda] I'm not able to update to the latest version of nvda!

 

Hi,

If you tell NVDA to remind you later, it will remind you of an update later.

Technical: the following goes into how NVDA update actually takes place (a bit geeky):

The NVDA updater component will check for, download, and apply NVDA updates. This is divided into the following parts:

• Update checker: this component will access NVDA update server and will fetch update information based on certain details about your machine such as Windows version, processor architecture, NVDA version you’ve got and what not.
• The NVDA update check interface that presents the actual update check dialog.
• Update downloader: this component consists of a file transfer agent and the user interface to report download progress.
• NVDA installer: updates NVDA given specific flags.
• Update check timer: a timer that will activate the components above every 24 hours if NVDA is told to check for updates automatically.
• Update check database: a Python-specific data file (a pickle file) that records the last update check timestamp, the update version presented, pending update installer file (if this is such a case) and other settings.

 

When you or NVDA check for updates:

1. NVDA will access its own update server hosted on nvaccess.org.
2. NVDA will pass on information about your NVDA installation such as whether it is an installed copy, Windows version, processor architecture, NVDA version, and if you enabled them, information about current speech synthesizer and braille display in use and other various information used for collecting statistics.
3. NV Access server will then present either a dictionary-like data detailing any updates it finds, the download URL for the update so the update download agent can fetch it, the hash of the update file and other information. Alternatively, NV Access will say nothing (returns empty data), which means there is no update.
4. NVDA will then present the appropriate message (update is ready or no update).
5. If you do choose to download the update, after presenting the donation screen, the update download agent will download the update file, periodically letting NVDA know the transfer progress.
6. If you do decide to be reminded, NVDA will not remind you for a while.
7. After downloading (i.e. transferring) the update file, NVDA will ask if you would like to install now or do it later.
8. If you do choose to install then, the just downloaded NVDA installer will run with special flags, telling it to update NVDA.
9. If you choose to install the update later, it’ll save the downloaded installer to a special folder named “updates” inside user configuration folder and will add an option to exit NVDA dialog, which will let you install NVDA whenever you are ready.

 

Cheers,

Joseph

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, April 12, 2020 4:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I'm not able to update to the latest version of nvda!

 

On Sun, Apr 12, 2020 at 07:11 PM, Joseph Lee wrote:

I advise not advertising beta software

Not to mention that the beta won't be picked up by the check for updates feature (NVDA+N,H,C) in a production release.

I can't imagine why NVDA 2019.3 would not pick up on 2019.3.1 unless it was already offered in the last 24 hours and declined.  I seem to recall that if you decline it sets some sort of flag that won't offer the update again until the following day.  If the same flag is also checked by Check for Updates and happens to be set, that might do it.

Joseph, I imagine you might be able to confirm or refute my speculation and if so, please do so.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna