-
-
Notifications
You must be signed in to change notification settings - Fork 768
64 bit NVDA is bundled with 32 bit vccorlib140.dll #18827
Copy link
Copy link
Labels
epic/64bit-migrationp1https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
epic/64bit-migrationp1https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Steps to reproduce:
Actual behavior:
The launcher is unpacked, but running the temporary copy of NVDA fails with error 0xc000007b.
Expected behavior:
NVDA should run.
NVDA logs, crash dumps and other attachments:
N/A
Further information
Discovered when testing #18814. in #18814 (comment), @hwf1324 noticed that
vcruntime140.dllwas causing the problem. I inspectedvccorlib140.dllandvcruntime140.dlland determined that they're compiled for x86 machines, which explains why NVDA can't load them.System configuration
NVDA installed/portable/running from source:
(Not) running from launcher
NVDA version:
Tested with try-fixTouchHandler-52257,05947e24
Windows version:
Windows Sandbox:
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
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.
No
If NVDA add-ons are disabled, is your problem still occurring?
N/A
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A