-
-
Notifications
You must be signed in to change notification settings - Fork 783
nvda_synthDriverHost.exe: Incorrect version information #19654
Copy link
Copy link
Closed
Labels
bugci-cdcomponent/buildp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritysecuritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
bugci-cdcomponent/buildp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritysecuritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for Bug.
Brief summary
It seems that some of the version information of
nvda_synthDriverHost.exeis not set correctly.Steps to reproduce
nvda_synthDriverHost.exe.*The company name was confirmed in the tooltip of the file.
Actual behavior
CompanyNameisunknown.ProductVersionis a string starting withsource-.-Expected behavior
CompanyNameisNVAccess.ProductVersioncontains correct version information.NVDA logs, crash dumps and other attachments
No response
NVDA type
portable copy
NVDA version
alpha-54695,cc554e1d (2026.2.0.54695)
Have you tried any other versions of NVDA? If so, please report their behaviors.
No response
Windows version
Windows 11 25H2 (AMD64) build 26200.7840
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