I downloaded the TS6b31 installer again, and with Windhawk running in the background, something launched—I’m not sure what. In the Control Panel, I have two ‘Teamspeak’ entries, but the important thing is that it works haha.
2 Likes
So, for the people having windhawk you can add teamspeak to the exclusion as follow:
C:\Program Files\TeamSpeak\*
For the other people it would be best make own post, or think if you got any “injection” apps running or other stylation. If not, close all apps not needed and test it out, even services running in background.
Adding an exclusion should not be necessary with beta3.1 anymore.
3 Likes
This version now works for me, and I don’t use Windhawk. It must have been something else. Thank you for releasing a fix.
2 Likes
Excellent! Thanks for the quick response, everything works perfectly!
I had never used Windhawk before, but I was having a problem and thought I could solve it that way. I installed and tried Windhawk, but it still didn’t work. I think you should just accept it and cancel the beta3 version. I’ve tried all the solutions, and it’s not working
Check the Announcement post for Beta3.1
3 Likes
After the update to Beta3.1 TS will not start anymore and is stuck at the first loading screen :
I’ve tried to clear AppData\Local\TeamSpeak\Cache but it didn’t help
I do not use Windhawk.
Logs:
[2025-10-16 13:56:23.176] [info] Notifications_Windows ctor
[2025-10-16 13:56:23.191] [info] TeamSpeak Client 6.0.0-beta3.1 (2025-10-16 09:34:21)
[2025-10-16 13:56:23.191] [info] SystemInformation: Windows 10 (19045) x64 (AMD or Intel) Binary: 64bit
[2025-10-16 13:56:23.241] [warning] sound mode_id Windows Audio Session is already loaded
[2025-10-16 13:56:23.559] [error] File validation failed for main.js, expected b91ad4f9e358a2fd565c22e0115d6b7075b9f5cd73a3e72a998c4e7dacb4c20266127c917ec0ce82f97b28b1a683d3c61acc2e32a96302be7848a1a4f7bdd076 got b54a12bb65dd63a93dce8d5117c9c206c45352542068679e3255dd5225c85e604e4ac96bb7ebd1461f1d00044d1e1a37f3349e4908b8fdd26c03d6b81c7ce384
[2025-10-16 13:56:23.753] [warning] sync_event, account status change: 2
[2025-10-16 13:56:53.179] [info] starting download for http://update.teamspeak.com/windows/x64/latest/info.json
[2025-10-16 13:56:53.432] [info] connected to push system.
1 Like
Now I get an empty window with the following error in logs:
File validation failed for main.js, expected b91ad4f9e358a2fd565c22e0115d6b7075b9f5cd73a3e72a998c4e7dacb4c20266127c917ec0ce82f97b28b1a683d3c61acc2e32a96302be7848a1a4f7bdd076 got b54a12bb65dd63a93dce8d5117c9c206c45352542068679e3255dd5225c85e604e4ac96bb7ebd1461f1d00044d1e1a37f3349e4908b8fdd26c03d6b81c7ce384
Tried to clear ts cache in appdata, but it didn’t help.
My TeamSpeak app hasn’t been opening for two days, and dealing with this has been truly exhausting. I’ve tried everything, and I’ll list it below. The problem hasn’t been resolved, and the app won’t open at all.
- I uninstalled and reinstalled TeamSpeak from the Control Panel.
- I manually deleted all files and reinstalled it.
- I tried repairing it using the repair button during the installation.
- I created a new user in Windows and installed TeamSpeak (this worked, but when I tried moving all TeamSpeak files from the new user to my main user, TeamSpeak still wouldn’t open on my main user.)
- Since some people in the forum reported that it was caused by Windhawk, I followed Windhawk’s instructions and even tried disabling it.
- I tried deleting all TeamSpeak files on my computer, including the registry, and reinstalling.
And despite all this, I still can’t open TeamSpeak. I even installed the newly released version 6.0.0-beta3.1, but my problem still hasn’t been resolved, and I’m not sure what to do.
1 Like
Still not working after I cleared all cache, restarted PC and fully reinstalled it. Same error
In that case, it seems the update process failed unexpectedly. Try uninstalling & then deleting your installation folder e.g. C:\Program Files\TeamSpeak and then install using the beta3.1 installer.
4 Likes
You might also want to try the above steps.
3 Likes
Thanks, complete uninstall and deleting folder fixed this one. Though TS is installed for my user only, so it was not C:\Program Files\TeamSpeak, but %LocalAppData%\Programs\TeamSpeak.
1 Like
That was the fix
1 Like
[2025-10-16 17:38:47.669] [error] Failed to start client, already running
[10780:10776:1016/173847.635:WARNING:..\116d0f\1\chromium\src\chrome\browser\signin\account_consistency_mode_manager.cc:74] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
Still not fix on my side. I deleted everything after the uninstalling process.
Have you cleared your cache folder located at %localappdata%/TeamSpeak, and then tried starting the client again?
2 Likes
Still not effective at fixing. Cache cleared, installed for user (prior to it cleared all install directories), beta 3.1, on Win 10 22H2 (19045.6456), Nvidia GeForce GTX 1050 Ti and Intel Core i5-10400F.
Can we pretty please have some sort of a fix that does work? Really sucks to have this “issue” interrupt what I was doing with TS.
Sorry to hear that. As you can see from other voices, the fix does seem to work for most people. We are currently investigating what issue persists with the current client.
You can PM me the log from %localappdata%/TeamSpeak/Logs/Default to determine if you are falling into the same category as @Caesium e.g.
2 Likes
[840:10368:1016/194654.863:WARNING:..\116d0f\1\chromium\src\chrome\browser\signin\account_consistency_mode_manager.cc:74] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[10708:2000:1016/194654.928:ERROR:..\116d0f\1\chromium\src\ui\gl\direct_composition_support.cc:616] AMD VideoProcessorGetOutputExtension failed: Неопознанная ошибка (0x80004005)
