Brief summary
I can't say exactly from when, but I've noticed these days that NVDA stopped reading the UAC (User Account Control) windows. I haven't checked, but I think the same is true for the Windows login screen.
The "Use NVDA during sign-in (requires administrator privileges)" option is checked. I even unchecked it, applied the settings, checked the option back and again applied the settings. It did not help.
Based on my visual observations, I think NVDA is not loading at all on those screens (visual highlight should be displayed even on those screens but it is not).
I'm running the latest alpha build of NVDA on a machine with Windows 11 version 25H2 (I'll provide more details of the test environment in the respective field below).
UAC (User Account Control) is set to 67%, which I think is the default value.
Steps to reproduce
- Launch NVDA.
- Launch a program with administrative privileges.
- Observe if NVDA reads the elements in the displayed UAC (User Account Control) window.
Actual behavior
NVDA behaves as if it is not loaded (e.g. does not read the elements in the UAC window).
Expected behavior
NVDA correctly reads the elements in the UAC window.
NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy
NVDA version
alpha-53423,57f2e9dc (2026.1.0.53423)
Have you tried any other versions of NVDA? If so, please report their behaviors.
No, because I don't (and I can't) have any other versions of NVDA installed on the machine.
Windows version
Windows 11 Pro version 25H2 (build 26200.7171), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
Name and version of other software in use when reproducing the issue
No response
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs
Brief summary
I can't say exactly from when, but I've noticed these days that NVDA stopped reading the UAC (User Account Control) windows. I haven't checked, but I think the same is true for the Windows login screen.
The "Use NVDA during sign-in (requires administrator privileges)" option is checked. I even unchecked it, applied the settings, checked the option back and again applied the settings. It did not help.
Based on my visual observations, I think NVDA is not loading at all on those screens (visual highlight should be displayed even on those screens but it is not).
I'm running the latest alpha build of NVDA on a machine with Windows 11 version 25H2 (I'll provide more details of the test environment in the respective field below).
UAC (User Account Control) is set to 67%, which I think is the default value.
Steps to reproduce
Actual behavior
NVDA behaves as if it is not loaded (e.g. does not read the elements in the UAC window).
Expected behavior
NVDA correctly reads the elements in the UAC window.
NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy
NVDA version
alpha-53423,57f2e9dc (2026.1.0.53423)
Have you tried any other versions of NVDA? If so, please report their behaviors.
No, because I don't (and I can't) have any other versions of NVDA installed on the machine.
Windows version
Windows 11 Pro version 25H2 (build 26200.7171), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
Name and version of other software in use when reproducing the issue
No response
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs