Steps to reproduce:

1. In NVDA menu -> Preferences -> Settings -> Remote, set up a remote computer as follows:
   • Enable remote access: checked
   • Automatically connect after NVDA starts: checked
   • Mode: Allow this computer to be controlld
   • Server: Host locally
   • Key: [some key of your choosing]
2. On the remote computer, in NVDA menu -> Preferences -> Settings -> General, press: Use currently saved settings during sign-in and on secure screens (requires administrator privileges).
3. On your local computer, use NVDA remote access to connect to the remote computer you set up in (1).
4. Switch to the remote computer.
5. Download the latest NVDA snapshot and run it.
   • Observe: When the snapshot launcher starts, a remote access connection is established as expected.
6. Choose to install NVDA, then press Install to confirm.

Actual behavior:

The UAC dialog appears, but no speech is transmitted to the local computer, nor can you use the keyboard on the local computer to interact with the UAC dialog. You're stuck!

Expected behavior:

A UAC dialog appears on the remote computer. Speech from the UAC dialog can be heard on the local computer and you can use the keyboard on the local computer to interact with it.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-37270,fc9a13e4 (2025.3.0.37270)

Windows version:

Windows 11 Version 24H2 (OS Build 26100.4652)

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, same behaviour.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Additional Details

I'm not quite sure how the secure handover works, but I think this has something to do with the name of the executable.

• If I run nvda_uiAccess.exe or nvda_noUiAccess.exe and then bring up a UAC dialog, I get the same problem.
• If I run nvda.exe even when it is a copy of nvda_noUiAccess.exe (i.e. no uiAccess privilege), UAC dialogs work as expected.

The secure desktop will of course start nvda.exe. I'm guessing the secure handover somehow requires the same executable name to do the handover.