nvaccess
COM registration fixing tool fails to register X64 DLL's on ARM 64, and does not register native ARM 64 DLL's
Steps to reproduce:
- Run the COM registration fixing tool from the tools menu of NVDA on an arm64-based system.
Actual behavior:
a success message will appear, however an error sound plays and it appears in the log.
Expected behavior:
No errors.
NVDA logs, crash dumps and other attachments:
ERROR - RPC process 11496 (nvda_slave.exe) (21:21:37.063) - Dummy-4 (11808): COMRegistrationFixes.register64bitServer: Error registering C:\Windows\System32\oleaut32.dll in a 64-bit context: Command '['C:\Windows\Sysnative\regsvr32.exe', '/s', 'C:\Windows\System32\oleaut32.dll']' returned non-zero exit status 5. ERROR - RPC process 11496 (nvda_slave.exe) (21:21:37.096) - Dummy-4 (11808): COMRegistrationFixes.register64bitServer: Error registering C:\Windows\System32\actxprxy.dll in a 64-bit context: Command '['C:\Windows\Sysnative\regsvr32.exe', '/s', 'C:\Windows\System32\actxprxy.dll']' returned non-zero exit status 5.
The issue appears to be that on windows on ARM 64, system32 points to native ARM64 DLL's, or it might point to ARM 32 since a special folder is used, but definitely Not X64 DLL's. Also, the COm registration fixing tool simply checks if the installation of Windows is 32 or 64 bit, it doesn't differentiate from X64 and ARM64.
System configuration
NVDA installed/portable/running from source:
Installed.
NVDA version:
2024.1 beta 9
Windows version:
Windows 11 23H2 (ARM64) build 22631.3155
Name and version of other software in use when reproducing the issue:
None exactly, but i'm having issues with the native ARM versions of Microsoft Edge and VSCode where NVDA sometimes just says unknown and I'm hoping that running it can fix that.
Other information about your system:
Windows 11 virtualized on Parallels on Apple Silicon Macbook, I also have another installation on VMWare fusion and I have the same issue there.
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.
2023.3.3 has the same issue.
If NVDA add-ons are disabled, is your problem still occurring?
Yes.
