-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVDA does not produces sound on lock screen with UAC disabled #12430
Comments
This can't be fixed, NVDA needs UAC privileges to be able to read secure screens like the lock screen. |
Disabling UAC seems to mean that all programs that run in the system have administrator privileges. |
Reopening this as per #13591 (comment) |
@josephsl any thoughts?
|
Hi, Any comment from the original poster now that:
Apart from this, I have no idea. Thanks. |
@josephsl I apologize, I tagged you on the wrong issue. I was actually asking if you had any thought on the related comment: #13591 (comment) |
Hi! |
Steps to reproduce:
Actual behavior:
NVDA working normally (with debug logging level nvda does not log any error, it logs information about pressed keys, speaked messages and other).
But NVDA does not produces any sound (synthesized speech, beeps and sound from addon, that plays url stream by BASS library).
Expected behavior:
NVDA correctly sends all sounds to output device.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.4
Windows version:
10.0.19042 workstation
Name and version of other software in use when reproducing the issue:
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.
If add-ons are disabled, is your problem still occurring?
Yes, NVDA without addons in primary nvda configuration (%appdata%\nvda) and without addons in system config (c:\program files (x86)\nvda\systemConfig) have that problem.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The text was updated successfully, but these errors were encountered: