6.0.0-beta3 and 3.1 does not start anymore

TeamSpeak 6 Client
,
1

Does not start anymore without admin, and saw it once now the client was blank just background needed restart it.

2 Likes
2

When opening the client, it closes after 2 seconds.

1 Like
3

Is there any way to fix this. It starts but crashes after like half a second. I have tested basically everything

4

Do you have any logs in here?
%localappdata%\TeamSpeak\Logs\Default

Or crash dumps?
%localappdata%\TeamSpeak\User Data\Crashpad\reports

Have you tried this workaround? We are internally testing a version that will fix this issue, in the mean time, please test and see if it is a different issue.

Client crash or failure to start on Windows (AMD CPUs with iGPU)
Some users with AMD Ryzen 7000-series (or newer) CPUs that include an integrated GPU may experience instant crashes or the client not starting at all on Windows systems without AMD drivers installed. To fix this, install the latest AMD chipset and graphics drivers from amd.com and the issue should be resolved.

4 Likes
5

(joining in as an interested party)

Logs report that “client is already running”. GPU is Nvidia, Win 10, no matches for “known issues” that are floating around the forum so far. I am at the moment unable to send over logs due to Win update locking down PC in the process.

I would be really interested to know how to fix this “confusion” of the client. Beta 3 (recent) fails to run, meanwhile Beta 1 has no issues in any way.

6

Unfortunately my TS6 does not open aswell. Already cleared the cache and did a reinstall. No Log in the TS Folder. Only from Windows:

AppName TeamSpeak.exe 
  AppVersion 5.0.0.4282 
  AppTimeStamp 68ee1b38 
  ModuleName ntdll.dll 
  ModuleVersion 10.0.26100.6899 
  ModuleTimeStamp 234c0f50 
  ExceptionCode c0000005 
  FaultingOffset 000000000000aa83 
  ProcessId 0x3cd0 
  ProcessCreationTime 0x1dc3deb4d93dfc7 
  AppPath C:\Program Files\TeamSpeak\TeamSpeak.exe 
  ModulePath C:\WINDOWS\SYSTEM32\ntdll.dll 
  IntegratorReportId f8fdf9c5-9af3-4e50-b29f-d5f203fd69ff 
  PackageFullName  
  PackageRelativeAppId

Windows 11 24H2

Ryzen 7800X3D with current Chipset Driver

RTX4080 Super with Driver Version 581.57

7

Windows 10 22H2
Xeon E3 1270 v3
GTX 1050ti with Latest Driver

I tried reinstalling, restarting pc and previous windows version. TS always starting once after PC restart + deleting all cache + installing ts back.
After that, all attempts to run TS ends with Failed to start client, already running in logs while no ts client currently running.
PC restart didnt help. And there are no crash dumps in %localappdata%\TeamSpeak\User Data\Crashpad\reports.

8

"I have the same problems. I did all the updates, but it still won’t open. ‘’ [2025-10-15 19:23:12.769] [error] Failed to start client, already running ‘’ %localappdata%\TeamSpeak\Logs\Default

Haven’t you found the reason yet? In that case, revert the beta 2 update and do not release beta 3 until it is fully ready.

1 Like
9

SAme here have to reinstall every time

10

The same problem, it doesn’t start on my laptop
In the logs:
[2025-10-15 23:52:28.892] [error] Failed to start client, already running

11

Can anyone who knows the solution please help? To the developers seeing this, please fix this issue already. If it can’t be fixed, why don’t you just roll back to the beta 2 version?

Problem Description: Following an update to version 6.0.0-beta3, the TeamSpeak client fails to start. The application either does not open at all or closes immediately upon launch. All recommended troubleshooting steps listed below have been performed, but the issue persists.

Applied Troubleshooting Steps and Results:

  1. AMD Driver Update:

    • Action Taken: The latest chipset and integrated graphics (iGPU) drivers were checked, downloaded from the official AMD website, and installed on the system.

    • Result: The issue persisted after the driver update. TeamSpeak failed to launch.

  2. Windhawk Program Conflict Check:

    • Action Taken: The system was checked for the Windhawk application. Where applicable, TeamSpeak.exe was added to the “Process exceptions” list in the program’s “Advanced Settings.”

    • Result: This action resulted in no change. The issue was not resolved.

  3. Clearing the TeamSpeak Cache:

    • Action Taken: Both the %appdata%/TeamSpeak and %localappdata%/TeamSpeak directories were accessed via the “Run” command. All temporary files and cache data within these folders were completely deleted.

    • Result: Clearing the cache did not resolve the launch issue.

  4. Run as Administrator:

    • Action Taken: The “Run as administrator” option was attempted on the TeamSpeak.exe file and its desktop shortcut. Additionally, the “Always run this program as an administrator” option was permanently enabled in the compatibility settings.

    • Result: The application failed to launch even with administrative privileges.

  5. Complete Reinstallation of TeamSpeak (Clean Install):

    • Action Taken: TeamSpeak was completely uninstalled from the system via the Control Panel. Subsequently, the latest installer for version 6.0.0-beta3 was downloaded from the official TeamSpeak website, and a clean installation was performed.

    • Result: Even after a fresh installation, the issue was not resolved.

3 Likes
12

Same here on Intel and AMD as well, nothing helped from above

1 Like
13

on Intel doesn’t work as well

1 Like
14

Dev, give me the opportunity to return to the previous version

15

I do have some logs, one state teamspeak is already running, the other some gibberisch with auth failed. Not sure if it’s safe to post here.

I have 7900 XTX with the latest driver 25.9.1 and chipset 7.06.02.123, there are no updates avaible atm. And no i do not reinstall, fix your stuff. And yes i can sometimes start it normaly with admin, and yes i sometimes a blank window, and yes there multiple exe running under teamspeak

16

So after testing around, someone mention windhawk, i am using this too “Start menu” and “Task bar Styler”, and some icon changed DLL’s
I saw a pattern here, when closing windhawk. It was not always consistent (i guess depends how stuck the exe under taskmanger was from teamspeak), i could normaly start teamspeak. When windhawk was running (portable version), it only workedt as admin, sometimes even just blank window and starting normaly did nothing anymore.

I guess since teamspeak use some kind of UI Design, it access one of those elements and have problems, i still see the problem on Teamspeak side to fix it. Maybe some guys here posting have same or simillar problem with changed UI Windows Elements (maybe even just the out of box windows settings).

17

I also use Windhawk, and I noticed that TS6b3 only starts when I force it to run as administrator while Windhawk is running. When I disable Windhawk, TS6 launches without any problems, even without administrator privileges. What’s more interesting is that two days ago both programs were working fine at the same time, so something must have changed recently.

18

Is anyone experiencing issues trying to launch the client who does NOT use Windhawk?

3 Likes
19

Yes. I don’t use Windhawk and AMD CPU.

20

Download beta3.1 from teamspeak.com

An announcement for that is imminent. Please re-test with that client and also please report back if its fixed - we are holding back pushing it to all clients automatically until we have some more confirmation.

3 Likes