Brief summary

nvdaHelperRemote.dll and nvdaHelperRemoteLoader.exe are not signed on X86

Steps to reproduce

1. Download a recent snapshot
2. Investigate said files digital signature

Actual behavior

Signature is missing. On corporate environments where signed binaries are required, NVDA can't start.

Expected behavior

Binaries are properly signed

NVDA logs, crash dumps and other attachments

CRITICAL - __main__ (11:54:33.139) - MainThread (15228):
core failure
Traceback (most recent call last):
  File "nvda.pyw", line 309, in <module>
  File "core.pyc", line 725, in main
  File "NVDAHelper\__init__.pyc", line 851, in initialize
  File "NVDAHelper\__init__.pyc", line 752, in __init__
  File "winKernel.pyc", line 462, in CreateProcessAsUser
PermissionError: [WinError 5] Access is denied.

NVDA type

installed copy, portable copy, installer/launcher copy

NVDA version

alpha-53089

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

Yes, alpha-53083 is also affected

Windows version

Windows 11 25h2, Windows Server 2022

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 not restarted my computer

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 not run the COM Registration Fixing Tool