Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA no longer recognises that the system has switched to a secure desktop when dismissing the lock screen #14094

jcsteh opened this issue Sep 1, 2022 · 1 comment · Fixed by #14105
bug/regression p2


Copy link

jcsteh commented Sep 1, 2022

Steps to reproduce:

  1. Press Windows+l to lock the computer.
  2. Press escape to dismiss the lock screen.

Actual behavior:

NVDA reports the Windows sign-in screen.

Expected behavior:

NVDA should first say "Secure Desktop" before reporting the sign-in screen.

System configuration

NVDA installed/portable/running from source:


NVDA version:

alpha-26424,2392d13c (2022.4.0.26424)

Windows version:

Windows 11 Version 21H2 (OS Build 22000.795)
Windows 10 Version 21H2 (OS Build 19044.1889)

Other Information

While this doesn't seem to matter on the surface, it causes a significant problem for NVDA Remote. Because of this, NVDA Remote doesn't know that the system has switched to a secure desktop when the lock screen is dismissed and so it doesn't react accordingly. That means that the user can't interact with the sign-in screen remotely, effectively locking them out of their system.

This issue was introduced in either 2022.2.1 or 2022.2.2. My guess is the former. I haven't dug into this much, but looking at the commit log, I'm guessing that IAccessibleHandler.SecureDesktopNVDAObject needs to be treated as secure or something like that.

Copy link

Brian1Gaff commented Sep 1, 2022 via email

@seanbudd seanbudd added bug/regression p2 labels Sep 1, 2022
@seanbudd seanbudd self-assigned this Sep 1, 2022
@nvaccessAuto nvaccessAuto added this to the 2022.4 milestone Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
bug/regression p2
None yet

Successfully merging a pull request may close this issue.

4 participants