1. Messages
  2. Strange behavior of NVDA and Windows 10 at machine startup

Re: Strange behavior of NVDA and Windows 10 at machine startup

Chris Mullins
 

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


 

 

 
Join {nvda@nvda.groups.io to automatically receive all group messages.