Share via


Setting playback and communication device via registry

Question

Thursday, October 25, 2018 1:53 AM

We have over 500 VMs that keep reverting the default playback and communication device every time users log in. 

We spent some time trying to track down what gets changed in the registry when user manually picks the playback and communication device, but aren't able to pin point what exactly is getting changed. Assuming it's an HKLU setting 

we are seeing many events around

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render

key, but not quite sure which registry operation is actually responsible for the setting. 

same question was asked here, with no solution provided.

https://community.spiceworks.com/topic/307276-gpo-script-to-set-the-sound-playback-default-device

Here is another post which actually shows what we are trying to get the registry key for

https://voxoa.zendesk.com/hc/en-us/articles/220963088-Setting-up-correct-playback-and-communication-device-in-Windows-10

Any help is greatly appreciated 

Thank you 

All replies (5)

Thursday, October 25, 2018 8:51 AM | 1 vote

Hi, 

We could use registry capture tool "regshot" to monitor the changed registry key after we changed default playback through GUI. 

Please search the tool on Google and use it to check the changed parts. 

As the issue occur on multiple virtual machine device, please check if you applied any related group policy to them if they are all domain joined computers. Try command line as administrator "gpresult /h C:\gp.html" could export applied group policy items. 

Bests, 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Thursday, October 25, 2018 5:09 PM

this is helpful

can anyone elaborate on the changed values ?

Values modified: 9

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:0:  01 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:0:  05 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:1:  01 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:1:  05 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:2:  01 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\4881a41f-5c14-4c1a-a1c4-85ea7803ad84}\Level:2:  05 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:0:  17 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:0:  1B 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:1:  17 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:1:  1B 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:2:  01 00 00 00 00 00 00 00

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\3a8b93b6-ef06-479d-9c31-d3ec25c6634d}\Level:2:  05 00 00 00 00 00 00 00

Total changes: 9


Friday, October 26, 2018 3:10 AM

Hi, 

Thank you for your cooperation!

I noticed all captured registry keys are located in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture and HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render, so I suspect if the user privilege was configured well for the 2 keys "Capture" and "Render".

Please find a works well computer which will not change default playback, and check the permission under the 2 keys. Then compare the permission with issue occurred computers. 

Bests, 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Saturday, October 27, 2018 12:25 AM

It's probably by design, the perms on HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture key are configured to allow non admin users to make changes. 

Between info posted here 

https://www.codemachine.com/article_how_windows_sets_default_audio_device.html

and our findings, we were able to resolve the problem.


Thursday, November 8, 2018 2:50 PM

Hi,

Thank you for your sharing and your efforts. It would be useful for other customers who have similar issue with you. For saving others customers research time, would you mark the helpful reply as an answer?

Bests,

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].