Cisco Support Community
Community Member

Jabber on Windows 10 Not Saving Audio Settings After Reboot

Cisco Jabber Audio Settings are not being saved or remembered after a reboot. I have set the audio settings to use the Headset Earphone/Microphone and clicked Apply then OK. Calls are sent and received properly through the headset. However, whenever Windows reboots, and Cisco Jabber opens, the Audio settings are automatically changed to use the built-in Speakers/Microphone. Please help.

  • Jabber Version: 10.6.2 Build 59142
  • OS: Windows 10 Professional
  • External Headset: Plantronics C310-M
  • Internal Audio: Realteck HD Audio



You are probably hitting bug CSCus78888

Try the suggested workaround and let me know if it works.




Please rate all helpful posts "The more you help the more you learn"

Re: Hi.

I followed the reccommended steps for the work-around and it does not work.  Are there any other ideas about how to get Jabber to retain the headset/ringer setttings?

Community Member

i had similar issue and it

i had similar issue and it got resolved by changing the preference setting under advance tab in Jabber client.

Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Hi mbernardo1,

How did you finally resolve this issue. Did you have GPO or driver/PnP issues un the Win side ?
I hit exactly the same issue in newer Jabber 11.8.4 or 11.8.5 versions where the configured headset audio stays not selected in the headset list under advanced settings, and this not only on one laptop, but on several PC/Laptops in a bank.
We are searching for troubleshooting ideas, but we have a suspicion about the Win ID of the audio device thet could change during PnP, and Jabber is writing a fixed ID of the first discovered headset in a file under appdata.

Any idea in the blog ?

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

I know this is an older thread now, but just in case this helps someone else, here is the location of the file which stores the speaker, microphone, and camera preferences.

%appdata%\Cisco\Unified Communications\Jabber\CSF\Config

C:\Users\USERNAME\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config



Jabber reads the file "" on startup and writes to it when changes are made to the speaker, microphone, or camera preferences. You can read the contents of the file with a text editor and even make your own changes. However, if you do make manual changes, the jabber client will need to be restarted as it appears the file is only read once initially and is not scanned for further changes when Jabber is running.


Here is an example of what some of the file contents look like:

Speaker-ID-0: USB\VID_046D&PID_0A44&MI_00
Speaker-Name-0: Speakers (2- Logitech USB Headset)
Speaker-SelectionID-0: {}.{c780344e-7c62-450b-b47b-d88c1912e34c}
Speaker-Volume-0: 100
Speaker-DeviceInterface-0: \\?\usb#vid_046d&pid_0a44&mi_00#6&b879def&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
Speaker-FriendlyName-0: Logitech USB Headset
Speaker-Name-1: Remote Audio
Speaker-SelectionID-1: {}.{6C26BA7D-F0B2-4225-B422-8168C5261E45}
Speaker-Volume-1: 100

Microphone-ID-0: USB\VID_046D&PID_0A44&MI_00
Microphone-Name-0: Microphone (2- Logitech USB Headset)
Microphone-SelectionID-0: {}.{22b8b43a-6e05-4f7f-b28b-fa15e9dd2d82}
Microphone-Volume-0: 40
Microphone-DeviceInterface-0: \\?\usb#vid_046d&pid_0a44&mi_00#6&b879def&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
Microphone-FriendlyName-0: Logitech USB Headset
Microphone-Name-1: Microphone (Logitech USB Headset)
Microphone-SelectionID-1: {}.{5f39f9e5-c055-4f98-94b0-dbaf33e4044c}
Microphone-Volume-1: -1
Microphone-DeviceInterface-1: \\?\usb#vid_046d&pid_0a44&mi_00#6&30faff39&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
Microphone-FriendlyName-1: Logitech USB Headset

Camera-Name-0: TANDBERG Video
Camera-SelectionID-0: \\?\usb#vid_1f82&pid_0001&mi_00#6&14a9a643&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
Camera-Volume-0: 80
Camera-DeviceInterface-0: \\?\usb#vid_1f82&pid_0001&mi_00#6&14a9a643&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
Camera-FriendlyName-0: TANDBERG Video

Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Hi Jonathan,


it's an interesting information of yours. I retain the static behavior of Jabber about the discovery of audio devices and this behavior could conduct to audio device loss.


From what I'm seeing on customer site, even a headset (Jabra, Plantronics,...) has been correctly priorized in the advanced settings, the same headset appears a second or a third time in the audio device list and only one is coloured in black. The other are greyed out.


Unfortunately the used audio device (same headset without any changes) seems to be newly discovered and is not placed on top of the list as configured.


A Microsoft MCSE has analyzed the headset driver and PnP discovery into Windows and has concluded that Windows makes his PnP job as usual.


Have you ever seen this behavior ?





Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Hi Jacky,


I have not seen this behaviour before.


You may have some luck with opening a TAC case to dig further.


Have you been testing using the latest version of jabber?

Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Hi Jacky,

Were you able to repair this issue? I find that our audio preference list will change seemingly on its own from time to time. We use Plantronics audio devices for our Jabber softphone. I've been working with Plantronics Support to determine why the devices may be reordered in Jabber - perhaps due to power savings or PnP - but no luck thus far. I'm a little surprised reports of this issue aren't widespread across the web. Either it's something in our environment that causes this, or not many people are using Jabber as their softphone with an external audio device (or maybe it doesn't bother them)? In any case, it's big problem for us. Also, based on our experience and what I've read elsewhere, this doesn't seem to be exclusively related to Windows 10. In fact, we're using Jabber 11.7 on Windows 7 64-bit.


I commented on an old thread here which illustrates how easy it is to recreate this problem when you use Remote Desktop, but the problem is certainly prevalent even with users who don't use RDP:



Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Hi All, 


I was able to resolve the issue. Thanks to another post in this list. 

After testing a bunch of solutions, I was able to make the settings stick by modifying the file
C:\Users\user\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config



1- Log off jabber

2- Exit

3- Open the file in notepad++

4-Manually place the device you want in order and change their ID

For example If I want to use my computer speakers by default instead of the Sennheiser Dongle



Microphone-ID-0: USB\VID_1395&PID_002D&MI_00
Microphone-Name-0: Headset Microphone (Sennheiser BTD 800 USB for Lync)
Microphone-SelectionID-0: {}.{ed0eb6da-101a-406d-9a37-7bcdc89871cf}
Microphone-Volume-0: 100
Microphone-DeviceInterface-0: \\?\usb#vid_1395&pid_002d&mi_00#6&7889738&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
Microphone-FriendlyName-0: Sennheiser BTD 800 USB for Lync
Microphone-DeviceVendor-0: Unknown Vendor
Microphone-ID-1: HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_10431080
Microphone-Name-1: Microphone (Realtek High Definition Audio)
Microphone-SelectionID-1: {}.{1a894faa-ba3c-4833-a3a3-adb202ca7654}
Microphone-Volume-1: 89
Microphone-DeviceInterface-1: \\?\hdaudio#func_01&ven_10ec&dev_0668&subsys_10431080&rev_1000#4&172bd3b9&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\rtmicinwave
Microphone-FriendlyName-1: Realtek High Definition Audio
Microphone-DeviceVendor-1: Unknown Vendor




Microphone-ID-0: HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_10431080
Microphone-Name-0: Microphone (Realtek High Definition Audio)
Microphone-SelectionID-0: {}.{1a894faa-ba3c-4833-a3a3-adb202ca7654}
Microphone-Volume-0: 89
Microphone-DeviceInterface-0: \\?\hdaudio#func_01&ven_10ec&dev_0668&subsys_10431080&rev_1000#4&172bd3b9&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\rtmicinwave
Microphone-FriendlyName-0: Realtek High Definition Audio
Microphone-DeviceVendor-0: Unknown Vendor

Microphone-ID-1: USB\VID_1395&PID_002D&MI_00
Microphone-Name-1: Headset Microphone (Sennheiser BTD 800 USB for Lync)
Microphone-SelectionID-1: {}.{ed0eb6da-101a-406d-9a37-7bcdc89871cf}
Microphone-Volume-1: 100
Microphone-DeviceInterface-1: \\?\usb#vid_1395&pid_002d&mi_00#6&7889738&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
Microphone-FriendlyName-1: Sennheiser BTD 800 USB for Lync
Microphone-DeviceVendor-1: Unknown Vendor


Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Thanks, Danik. I find that I too can edit this file the way you described if I want to control the list, however the order still changes on its own. Did you do anything more than simply edit the file? Perhaps you also restricted permissions to the file? I found that I can setup this file the way I want per your description and give the user read-only permissions to it which will force Jabber to order the devices correctly on clean launch, however they will still get reordered mid-Jabber session. In short, this method requires the user to exist Jabber and launch it to pull in the correct settings. This is close to working, but still not ideal.


Any other thoughts? 

Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

I have to confirm this behaviour of Jabber app. We are using 11.9.1 and by some users change the jabber app the setting during the day even if read-only is. Is there any news regarding this issue?

Community Member

Re: Jabber on Windows 10 Not Saving Audio Settings After Reboot

Anyone make any progress on this?  We are having volume problems with out headsets.  We are using 11.9.1 and VXME on our VDI environment.  With VXME on both the thin client and VM.  When disconnecting from the VM the microphone volume on the headset changes when connecting back to the VM.  I've tried playing with volume in the file but that doesn't do anything.  it doesn't seem to recognize the volume change for the microphone in that file.  Anyone have any ideas?  Thanks.  

CreatePlease to create content