Open CyrilleB79 opened 11 months ago
Usually I see this problem for those who have user Account Control disabled. Not notifications , but control itself. A simple way to check to run command line and see if the administrator will be written in the window name. If the user account control is disabled, then any program will be ran as administrator
One question.
Does this person UAC turned off?
If yes, this might be an issue.
On 11/16/23, Cyrille Bougot @.***> wrote:
Issue reported on behalf of another user (Vincenzo); see this thread and this trhead and this thread.
Steps to reproduce:
Press NVDA+shift+D to enable audio ducking.
Note: this was tested with and without WASAPI enabled.
Actual behavior:
Message "Audio ducking not supported" is heard.
Expected behavior:
Audio ducking should be enabled.
NVDA logs, crash dumps and other attachments:
See message .
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3
Windows version:
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
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?
Yes
Does the issue still occur after you run the COM Registration Fixing
Tool in NVDA's tools menu? Yes, since NVDA has been reinstalled from scratch.
-- Reply to this email directly or view it on GitHub: https://github.com/nvaccess/nvda/issues/15790 You are receiving this because you are subscribed to this thread.
Message ID: @.***>
-- with best regards Beqa Gozalishvili Tell: +995593454005 Email: @.*** Web: https://gozaltech.org Skype: beqabeqa473 Telegram: https://t.me/gozaltech facebook: https://facebook.com/gozaltech twitter: https://twitter.com/beqabeqa473 Instagram: https://instagram.com/beqa.gozalishvili
See also #12430
Yes, the UAC was at 0%. Setting it to 67% solves the issue.
I thought that we already had a ticket for this issue, but I cannot find it.
The same underlying cause as #13591
cc @seanbudd @CyrilleB79
Specifically, the registry key that can actually affect this issue are as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Set the value of EnableLUA
to 1 to enable audio ducking mode.
Thanks
Note: Narrator is not affected by the above reg key. This may be something NVDA needs to fix.
Issue reported on behalf of another user (Vincenzo); see this thread and this trhead and this thread.
Steps to reproduce:
Press NVDA+shift+D to enable audio ducking.
Note: this was tested with and without WASAPI enabled.
Actual behavior:
Message "Audio ducking not supported" is heard.
Expected behavior:
Audio ducking should be enabled.
NVDA logs, crash dumps and other attachments:
See message #18787.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3
Windows version:
Windows 11
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
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?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes, since NVDA has been reinstalled from scratch.