Respected NVDA Group,

 

While installing any NVDA Add-ons, I get the following error:

 

You will need a new app to open this .NVDA-addon file.

Look for an app in the Microsoft Store.

 

 

The device that I am using is a HP Pavilion laptop upgraded to Windows 11. Please give your kind suggestion to solve this error.

 

With Best Regards

Sanjog Kumawat

Membership Support for Asia & Africa at Bookshare

A Benetech Initiative

IAAP Individual Member

 

 

I have the Code Factory Eloquence installed on my system  I have

hesitated to upgrade to the latest builds of Nvda because I was informed

by the add-on installer that Eloquence wasn't compatible.  This was

about a month or 6 weeks back.  Has the situation changed with

Eloquence?  Any information would be appreciated.

Dave Marthouse

dmarthouse@...

Hi

The information you see on the lock screen is controlled through the Personalization sub-menu in the Settings app. (Windows+I).  Arrow down the list of categories after opening the Personalization sub-menu and press enter on “Lock Screen”.  You can choose what to display in the controls on this screen.  When my lock screen opens after start-up, I just press control and that puts me in the Pin number box and after entering that, my NVDA user profile loads..

 

Cheers

Chris 

 

Sent from Mail for Windows

 

From: Artin Dekker
Sent: 27 November 2021 18:52
To: nvda@nvda.groups.io
Subject: Re: [nvda] Strange behavior of NVDA and Windows 10 at machine startup

 

Hello everyone,

 

Has anyone ever found a solution for this? I have a new laptop with Windows 10 20H2 and NVDA 2021.2 and run into the same problem.

 

Kind Regarts,

Artin Dekker

On Thu, May 17, 2018 at 02:06 PM, Kostadin Kolev wrote:

Hello all,

I've noticed this strange behavior after the update of Windows 10 to version 1803. The behavior is the following. When the machine starts and Windows 10 loads, it gets to the lock screen as it should. Initially it all looks normal, but only for a while. Moments after that, the lock screen displays not only the time and date as it normally does, but user-specific information as well (e.g. weather forecast, upcoming alarms, etc.). Not only that, but the NVDA startup sound is heard, as if the desktop copy of NVDA is loaded, even though it should load only when the specific user signs in. I can't tell for sure if the desktop copy of NVDA loads, because my NVDA settings for the desktop and secure screen copies of it are the same. On top of that, the "Ease of access" menu appears and NVDA starts reading its menu items one by one. This happens when I power up the machine with "Fast Boot" enabled. I haven't tried with "Fast Boot" disabled, but when I restart the machine, the behavior described above does not occur. So, it must be related to "Fast Boot" somehow. And this did not occur before the update to version 1803 of Windows 10.

Has anyone else experienced the behavior described above? Have you found any solutions besides turning off "Fast Boot"? Turning off "Fast Boot" is also a solution, but I'd prefer to keep it on if possible.

______
Best wishes,
Kostadin Kolev

 

 

 

Hi,

Actually, far from useless. December 6, 2021 is a credible date because:

1. There is a forum (hosted on Groups.IO) where NVDA translators hang out, and members were asked to finish 2021.3 translation by end of November.
2. After translators send in their final data, NV Access publishes release candidates, in this case I expect 2021.3 RC to be released anytime this week.
3. At least a week after the first RC is released, the stable version is released. If translations schedule holds, next week is when I expect NVDA 2021.3 stable version to come out. Things can change if folks discover a really serious problem that must be fixed right away.

I said "credible date" precisely because of point 3 above: things can change. A rule of thumb is that:

1. A given NVDA release will go through beta/RC phase for at least three weeks: two weeks while translators put finishing touches (translatable string freeze), then an RC week. NV Access can choose to declare string freeze (two weeks) right as they release beta 1 but typically developers have waited several days after releasing beta 1 to tell translators that they have two weeks to finalize translation data.
2. We can guess as to when the next stable version of NVDA might be released, which takes place within a week after end of translatable string freeze. Folks can "guess" this date not only because NV Access has documented this in many places (including in various In-Process blog posts), but also since things can change without notice.
3. For backwards incompatible releases, beta phase is longer - not only developers are finalizing the release, but beta is used by add-on authors to make their add-ons compatible. These days more add-on authors have realized that they must prepare their add-ons a bit early, going so far as willing to think about testing their add-ons against alpha releases (not often but happens; the practice of testing add-ons while using NVDA alpha builds is optional). I expect there will be announcements about NVDA 2022.1 after the new year.

Cheers,

Joseph

Hi,

A birdy or two tells me that NVDA 2021.3 will be here sooner than we think, perhaps before Christmas. As Quentin said, it is up to you as to when you would like to install it. However, I strongly recommend Windows 11 users to install the upcoming NVDA release as soon as possible because it contains an important fix for users, specifically NVDA will not get stuck when switching between apps. There are more major changes scheduled for 2022.1, but that's getting ahead of the story - in particular, NVDA 2022.1 will resolve a long-standing issue where NVDA would not announce File Explorer status bar items but only on Windows 8.1 and later (Windows 8 is unsupported).

Cheers,

Joseph

Hi,

A birdy or two tells me that NVDA 2021.3 will be here sooner than we think, perhaps before Christmas. As Quentin said, it is up to you as to when you would like to install it. However, I strongly recommend Windows 11 users to install the upcoming NVDA release as soon as possible because it contains an important fix for users, specifically NVDA will not get stuck when switching between apps. There are more major changes scheduled for 2022.1, but that's getting ahead of the story - in particular, NVDA 2022.1 will resolve a long-standing issue where NVDA would not announce File Explorer status bar items but only on Windows 8.1 and later (Windows 8 is unsupported).

Cheers,

Joseph

Hi Eduardo,

I think I lost something in translation, but are you asking if it is ok to NOT install the NVDA 2021.3 beta ?  If so, then that is absolutely fine - Your previous version of NVDA will let you know when the final version is out* and so will I here as you noted.  We haven't had any serious reports of issues with the beta, so don't anticipate anyone should have any problems, but if you are a bit nervous about installing software before the stable version, then waiting is perfectly ok.

*The one caveat to your existing version letting you know about the new version is the issue which I think most here are already across - that the way our recent security certificate upgrade was done did not propagate out to everyone and so there are some users who will receive an error when they try and check for updates.  For those users, you can either:

- Live with it until NVDA 2021.3 comes out and then download and install that manually

- Download the Beta from https://www.nvaccess.org/post/nvda-2021-3beta2/ - run it (you don't have to install it) and from the help menu choose "check for updates" - that alone should fix it, you can then exit and go back to your old version.

- Download the add-on we put out in October.  I mentioned this in our In-Process blog at the time, which you can still find here: https://www.nvaccess.org/post/in-process-19th-october-2021/ - The add-on does exactly the same thing as checking for updates from the beta (and from future versions of NVDA).

Kind regards

Quentin.

On Mon, Nov 29, 2021 at 1:44 PM Eduardo Fermiano Luccas <25102008luccas@...> wrote:

I would like to discuss not installing NVDA 2021.3 now1: if I am using NVDA 2021.2, I do not have to install anything as I know I am using the latest NVDA, and when NVDA 2021.3 arrives I can download manually.2: if i'm using NVDA 2020.3, i can still download NVDA 2021.2 manually.3: we know there's no updates for now, so let's have no fear.4: if you're subscribed to this group, quentin will let you know about the release of NVDA 2021.3. waiting for your answers!

Sorry for the translation errors

--

Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org 

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess

Hi Listers

Is there any add-on for nvda to use facebook messenger desktop version?

Thanks

Hi

Yes it does run the terminal as batch files are essentially a series of DOS commands that require that environment to run.  The following will start the specified program and exit the command prompt environment:

@echo off

start <full pathname including drive letter>

Exit

Example:

@echo off

start %windir%\system32\notepad.exe

exit

Cheers

Chris

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

*From: *Shaun Everiss <mailto:sm.everiss@...>
*Sent: *28 November 2021 04:04
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] NVDA Portable Start

Thats a problem really.

Yeah, there is no way to actually do this with aditional mucking about.

You can use nircmd or other program to run your batch file.

You can run them with a script.

You can run them from a shortcut.

You can run and edit a shortcut to hide or minimise a window.

You can run the batch file normally, then once nvda is running hit alt f4.

You can just type x:\nvda211\nvda into run as long as you know the drive letter.

On 28/11/2021, Gene <gsasner@...> wrote:

I tried doing what you do and it runs the terminal, which I know nothing

about.  I closed it in the following way:

I opened the system menu with alt space.  I either down arrowed or up

arrowed to close and pressed enter. The terminal closed and I was

back in

Windows.  You can also use c in the menu to close the terminal

instead of

arrowing to close, as follows:

alt space

type c.

Gene

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

From: Gene

Sent: Saturday, November 27, 2021 9:33 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA Portable Start

I’m not sure what is going on.  When you say it won’t exit to

Windows, have

you tried typing exit and pressing enter?  While convenient, you

don’t have

to use a batch file.  If necessary, I’ll discuss how to run NVDA without

one.

Gene

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

From: Howard Traxler

Sent: Saturday, November 27, 2021 7:09 PM

To: NVDA

Subject: [nvda] NVDA Portable Start

I have a portable copy of "NVDA on a thumb drive in a folder called

NVDA211.  It contains NVDA version 2021.1.  When I shut down my

installed NVDA, switch to the thumb drive and execute a batch file that

starts the portable version, it starts in a command mode that does not

accept commands; nor will it exit back to windows.  This does not seem

normal to me.  Wonder how I can make it stay in windows when I start the

portable?

Thanks.

Howard