Follow-up: Sound Split mode settings resetting on Windows 11 / NVDA 2025.3.3

[Mister Kayne]

Dear Group Members,

 

I’m writing to follow up on my previous message regarding an issue I’m experiencing with the Sound Split mode and to see if it reached everyone.

 

To recap, I am finding that my default settings for Sound Split are consistently changing or resetting whenever I wake my computer from Sleep or Hibernate.

For context, I am using a Windows 11 system running NVDA 2025.3.3.

 

Has anyone else in the group noticed similar behavior with their audio ducking or splitting settings after the computer resumes from a low-power state? If you have encountered this—or if you have found a way to make the settings persist—could you please reply and let me know?

 

I would appreciate any insights or confirmation that I'm not the only one facing this challenge.

 

Warm regards,

 

Mister Kayne
"It's a bitter, sweet symphony this life…"

Author: The Somebody, Nobody, Anybody & Everybody Blog!

Mail: writ...@mister-kayne.com

Sent from Outlook® for Windows 11

 

 

[Gene Asner]

I may have seen one other complaint about this on a list about a month
ago. Regardless, hibernate and sleep used to be notorious for losing or
changing settings on waking the computer. While I don't think this
happens much anymore, I haven't seen complaints about it for years,
evidently, it still may on occasion.

As to how it might be prevented, someone else with more technical
knowledge will have to discuss that but I'll make a suggestion about
returning to proper behavior:
When this happens, issue the command NVDA key shift r to restore the
previous configuration, in other words the configuration used when you
run NVDA. That may restore proper operation. I doubt it, but it's a
very simple test and it might work.

Gene

> <https://www.mister-kayne.com/>
>
> Mail: writ...@mister-kayne.com <mailto:writ...@mister-kayne.com>

>
> Sent from Outlook® for Windows 11
>

> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the
> rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nvda-users+...@nvaccess.org
> <mailto:nvda-users+...@nvaccess.org>.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D72BD59EBC786C5968429D46A%40TYZPR02MB9171.apcprd02.prod.outlook.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D72BD59EBC786C5968429D46A%40TYZPR02MB9171.apcprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.

[Sean Randall]

have you considered that the copy of NVDA on the lock screen might be causing a conflict? Are you running identical  settings across? Do secure screens even support the feature? 

given the ringing silence  on this list after this, your third message by my count, I'd presume it to be quite a rare phenomenon or one that a quick restart fixes easily enough not to bother most people.    

Thanks

Sean

On 10 Mar 2026, at 14:03, Mister Kayne <mister...@outlook.com> wrote:



--

***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 

You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D72BD59EBC786C5968429D46A%40TYZPR02MB9171.apcprd02.prod.outlook.com.

[Mister Kayne]

Dear Gene and Group Members,

Thank you both for taking the time to reply and share your observations.
Gene, I appreciate the suggestion of using NVDA+Shift+R. I gave it a quick test, and while it's a helpful command to have in the toolkit, it didn't quite resolve the persistent reset after waking the system. It is interesting to hear that Sleep and Hibernate still carry that reputation for configuration quirks!

At this stage, I think the best path forward is to perform a clean uninstal of NVDA, ensuring I manually remove the user profiles and leftover configuration folders. I'm hoping a fresh instal of version 2025.3.3 will eliminate any underlying conflicts and allow the Sound Split settings to stick.

I’ll be sure to update the group if this fixes the behavior, in case anyone else runs into this a month or two down the line.

Have a good one!

Warm regards,

Mister Kayne
"It's a bitter, sweet symphony this life…"
Author: The Somebody, Nobody, Anybody & Everybody Blog!

Mail: writ...@mister-kayne.com

Sent from Outlook® for Windows 11

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/34120904-23c5-b7f6-9b21-50d33e4eb155%40gmail.com.

[Gene Asner]

I didn't say NVDA shift r. The command is NVDA control r. You may have
miswritten and you may have used that command.

Also, you are going through a lot of what may well be unnecessary work.
Create a portable version, don't have it save the current
configuration and it will be a completely clean copy. then test.

There is no reason to completely remove NVDA when you can easily test a
clean copy.

Gene
Gene

[Mister Kayne]

No worries, thank you for your help!

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/55278dc4-89b8-7924-e19c-92250518fc09%40gmail.com.

[Sean Randall]

it would be worth knowing about the NVDA that runs on secure screens still: does a portable copy tap into this version in any way? Does it still run, even if you're running a portable copy?
these screens may be triggered during the sleep/hibernation process and I don't know the impact of any sound split settings here, if any work. Even if they don't, the fact that the standard settings are in force, even temporarily, may be causing a problem.
Thanks

Sean


On 10 Mar 2026, at 18:28, Gene Asner <gsa...@gmail.com> wrote:

I didn't say NVDA shift r. The command is NVDA control r. You may have

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/55278dc4-89b8-7924-e19c-92250518fc09%40gmail.com.

[Gene Asner]

It won't speak secure screens but it says something about secure desktop
when it becomes active and in my experience, you can always issue the
command control y, then do what you want to do in the secure desktop.

Gene

[Gene Asner]

I'll add that if you are doing something in a secure desktop, output
won't be spoken. But you already know what to do in this case, so you
shouldn't need speech. Also, you can test using the installed version,
resuming from hibernate or sleep, then starting NVDA again to see if
that solves the problem. You need only issue one command, control alt n
to cause the installed NVDA to restart. I don't know how long restart
takes on different computers. On my old not very fast machine, it takes
about eight or nine seconds.

Gene

[Sean Randall]

Alt+y to dismiss the UAC usually, I think.
Probably not relevant to the "Windows is resuming" screen which may appear after hibernation etc, though.

>>> nvda-users+<mailto:nvda-users+...@nvaccess.org>. To view
>>> nvda-users+this

>>> discussion visit
>>> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02M
>>> B9171D72BD59EBC786C5968429D46A%40TYZPR02MB9171.apcprd02.prod.outlook

>>> .com
>>>
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D72BD59EBC786C5968429D46A%40TYZPR02MB9171.apcprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.
>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
>
> You can contact the group owners and moderators via nvda-user...@nvaccess.org.
> --- You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
> To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/55278dc4-89b8-7924-e19c-92250518fc09%40gmail.com.
>

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md

You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/c7fee379-c615-9f3b-7ab1-b3cc56dc0f82%40gmail.com.