[wdmaudiodev] Re: Unexpected default sound device on Windows 10
- From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
- To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Wed, 20 Dec 2017 16:01:04 +0000
Expected behavior for the property key is to prevent the endpoint from becoming
the default under any circumstances. (If it is the only endpoint, then there
will be no default, just as if there were no endpoints at all.)
If you want to allow the endpoint to be the default (by user choice), but just
make it much less attractive than the other endpoints on the system, then the
property key is not for you. As an alternative you could take a look at the
Windows default device selection heuristics:
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Eugene Muzychenko <reg.wad@xxxxxxxxxxxxxx>
Sent: Wednesday, December 20, 2017 5:33:27 AM
To: Matthew van Eerde
Subject: [wdmaudiodev] Re: Unexpected default sound device on Windows 10
At Mar 1, 2017 you wrote:
You can set this property in your .inf to make your audio device ineligible to
I have the same problem as the topic starter, and added
PKEY_AudioDevice_NeverSetAsDefaultEndpoint to all my virtual device
endpoints. It works as described, removing "Set as default device"
items from endpoint's context menu, but Windows 10 (including 10.0.16299)
automatically sets last endpoint as default upon device installation.
Such behavior looks irrational. Should it be expected?
I wanted to just prevent *automatic* default endpoint assignment upon
device installation, allowing a user to assign default endpoint
manually later. Is there a way to accomplish that?
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
Other related posts: