Comment 1 by jteh on 2014-07-12 09:12
This works as expected for me in both Windows 7 and 8.1. I'd be interested to know whether this occurs for anyone else.

Please set your log level to input/output and provide a log of reproducing this. See LogFilesAndCrashDumps for details.

Comment 2 by blindbhavya on 2014-07-12 10:41
Hi.
I have changed the level as instructed.
Another update to this issue. Twice I tried to reproduce the problem on the same machine in the same manner but was unsuccessful. However, later when I actually wanted to change the volume without any intention to reproduce I did it! NVDA did announce the changes. So this problem is inconsistent. I will create a log and attach it after some time.

Attachment nvda log.log added by blindbhavya on 2014-07-12 11:00
Description:
log file to reproduce the issue, please note that the first time I tried to reproduce I was unsuccessful, however the second time I was successful so both success and non-success are included in this log file

Comment 3 by briang1 on 2014-07-13 08:26
One comment. On a HP laptop I was looking at once, this effect happened and it was HP's own version of the volume control applet which caused it. Making it work through the norml Microsoft control fixed it. However now you are saying its sometimes there, sometimes not, so I'm thinking around some other software which is interacting with it in some way. What does nvda/f1 give when on the control in silent mode, so to speak.

Attachment NVDA F1 log viewer.rar added by blindbhavya on 2014-07-13 09:27
Description:
The NVDA log viewer for the Speakers/HP icon in the System Tray

Comment 4 by blindbhavya on 2014-07-13 09:29
Hi.
All the log viewer information is present in the archive in the form of a text document.
Have a look.
Please someone fix this issue.

@bhavyashah are you still able to replicate this? I am not able to using Windows 10. I wonder if this has to do with the manufacturers volume control versus Microsoft's Volume control.

@ehollig I don't have access to the HP machine I experienced this issue on. I do not encounter this anymore with a Windows 8.1 power Dell laptop. All in all, I am happy for this ticket to be safely closed.

Thank you @bhavyashah. Closing as requested in #4269 (comment)