Thanks for bringing this up again internally 
I’m usually running Wave Link with some VST Plugins on my Mic channel and using the corresponding virtual audio device (Wave Link MicrophoneFX) and Teamspeak breaks everytime I update the Wave Link software for example. My current workaround is to delete the whole audio_settings section from the database file, but I’ll try your suggestion with the default device.
This bug has been there since the first releases of Teamspeak 6, making it unusable for those in a noisy environment.
The toggle in settings → audio → audio processing → Echo Cancellation
Can be enabled, but as soon as any other settings menu is selected, like account or identities, instead of audio settings, then it gets turned off.
This is very annoying, running Teamspeak6 as admin does not fix this bug.
Please fix.
It’s just sad that the developers haven’t managed to fix this problem in three years…
Since some time I experience the issue that whenever I launch Teamspeak 6 the VAD sets itself to automatic and when I change it to another mode it switches back immediately after exiting or changing the settings tab. I tried to reinstall the App but didn’t help. When being long enough in the settings it seems to “apply” the VAD mode and it doesn’t switch back.
I’m on Win11 and one other friend of mine has this issue.
It is unfortunately an annoying issue we’ve tried to fix in the past but had no success at.
5 Likes
The problem has still not been fixed
1 Like
I’ve moved the topic to the corresponding thread
As explained earlier this year, it is an issue we’ve struggled to fix in the past. We expect to be able to address this once the hardware acceleration update is released and we have a shorter update cycle.
2 Likes
Client uninstalled immediately after i have recognized that i can’t even switch to volume gate mode…
There is no Save/Ok Button but when i leave the settings page, it switches back to automatic mode. And the “automatic” mode behaves like “record everything”. My record lamp is always on and my mates here everything, useless.
Oh, and if there is somewhere something to save, then maybe rethink the UI. I mean the UI is definitely to be reinvented in my humble opinion.
1 Like
This is still a problem. Using Win 11 on a Mackie DLZ as input device. I am stuck to permanently transmitting. However, when switching recording to my headset, it saves.
Clearly being related to the input type bounding somewhere.
1 Like
This still hasn’t been addressed.
My friends can sometimes save out of luck but it’s REALLY not helping with them forgetting Discord…. I’m having a hard time because of this, you guys should really make this a priority hotfix.
Can’t save microphone device in settings with this version now on Windows. Switched back to TS3 because no alternative 
just install 6.0.0-beta3.2 - Foundation I Hotfix 2. This resolve my problems with mic. Update by 09.12.25 broke mic settings.
Helpful information if TS will crash after launch
Hello all,
TS6 user since 3 months here, I never had any trouble of that kind during those 3 months, and i’m using a GO XLR Mini.
Today, I moved my computer and after unpluging then plugging all my cables back, my microphone was also always ON and impossible to modify in the settings (VAD on automatic).
After trying some of the solutions displayed here, the problem stayed the same.
Then I realized that I did not plugged my GO XLR in the same USB port than it was earlier. After putting it back to its old port, everything was back to normal, mic detecting my voice when I speak and not my keyboard and settings being saved.
Not sure if this will help someone but I do hope this could lead to finding the reason it happens, maybe linked to the USB Port address or idk. (if needed, the USB Port I use for my GO XLR is the one closest to my Ethernet Port, motherboard is Asus Z490-A)
Hi there,
I’ve recently gotten the TS6 server set up and have moved over to using the TS6 client as well. I set my mic to Voice Activity Detection in Automatic mode, like I usually do. The problem is, when I close the client and re-open it, my mic “hangs open.” In the settings, it will still show VAD as enabled in Automatic mode, but my mic is continually transmitting. If I toggle VAD on and off, the problem goes away. The same thing happened to my friend I was chatting with. We are both on 6.0.0-beta3.4 (Windows 10 / Windows 11), and the server is on v6.0.0-beta8 (Linux).
They don’t seem to put older builds of TS6 onto their FTP server. Do you know where folks can download this previous version you noted?
My topic that I made was moved here by a mod because it does seem like a similar issue, but I’m not convinced that it is just one issue. Reading back on the history in this thread, most people are talking about making specific setting changes and them not persisting. To be clear, I do experience issues with that. If I change the VAD mode to Hybrid for example, when I change settings pages and go back the setting is not saved.
However, what my original post was about has to do with Automatic VAD getting “hung open” when you initially launch the application. I leave my VAD set to Automatic anyway from a practical standpoint because I run RNNoise on my mic externally. When I first launch the app though, I’m continually transmitting until I go into the settings, toggle VAD off and then on again.
I’m not convinced this is only about settings not saving. I think the stuck Automatic VAD and the settings not persisting are probably the same underlying issue.
I’m using an Elgato Wave XLR with Wave Link, and every time Wave Link updates I run into the same problems in TeamSpeak: Automatic VAD is stuck open on first launch (constant transmitting), and if I change audio settings like switching VAD mode to Hybrid, they don’t stick after leaving the settings page.
The only workaround that consistently helps me is deleting the audio_settings entry from settings.db in %APPDATA%\TeamSpeak\Default. I open it with DB Browser for SQLite, go to json_blobs, delete the row called audio_settings, save, and restart TeamSpeak. Sometimes TeamSpeak needs one extra restart, but after that everything works normally again.
And looking at the audio_settings json, it seems that TeamSpeak is storing full WASAPI endpoint IDs along with all device-specific config (AGC, denoise, VAD mode, levels, etc.). So if Wave Link re-enumerates devices during an update and those IDs change, TeamSpeak is loading a blob that references endpoints that technically no longer exist.
That maybe would explain both behaviors:
-
settings not persisting
-
Automatic VAD stuck open on startup
-
deleting audio_settings fixing it completely (forces full rebuild)
If even a single stored endpoint ID is no longer valid and isn’t handled gracefully, that alone could obviously cause things to break.
So this feels less like a simple “settings not saving” bug and more like TeamSpeak not properly invalidating or rebuilding audio_settings when endpoint IDs change, which happens pretty often with virtual mixers.
That makes sense to me. My friend and I that both experienced this issue are musicians with home studios and several audio devices are connected at all times. We also both do VR stuff and streaming so there are several fake audio devices in there such as VB Audio cable, etc. Looking at my audio settings blob, it looks like this:
It seems to be listing devices that aren’t even connected, such as my BT headset and my old VR headset. The ID’s also seem to have port information on them, as if they would be recognized as a different device if plugged into a different port?
After deleting the audio settings blob from the DB and having TS recreate the record, it looks like this:
You can see that all of the disconnected devices are gone, but it didn’t seem to matter. My mic was still hung open upon starting the TS6 client.