TS6-beta2 Client does not start

TeamSpeak 6 Client
21

We are trying to narrow down the issue and identify the root cause. Therefore we need to know if this is a problem that only appears on modified / old Windows versions.

4 Likes
22

windows 10 1809 LTSC (Last update 15.01.2025)

23

Yup, Windows 10 Enterprise, LTSB. Just for Fun, I tried to Install the VC-Runtimes 64 and 32 bit. Still no Success.

24

Bump

25

Should this work on Linux as well? I installed over there and just never opensā€¦

26

Guess Itā€™s just too oldā€¦ I use LTSC 21H2 and seems to be working just fine

27

The client should work on Linux. Recently there was a report from the flatpak maintainer, that the new version does not work, so you probably need to install it manually.

3 Likes
28

I only saw Teamspeak 6 in the flatpak package so maybe that was the reason thenā€¦

1 Like
29

More than a month has passed, and the developer has not offered anything to solve the problem. It seems that Teamspeak and I are not on the same path and it will not be able to become an alternative to Discord. These restrictions are probably artificial. It is very strange that we still have not seen the system requirements in which these restrictions could be specified.

30

The Flatpak package should work in itself. It just shows a few messages regarding D-Bus access, for which we have not found any functional limitations so far.
What exactly the individual accesses to the system D-Bus are used for is not yet known in detail.
(Forum Thread / GitHub Issue)

One functionality that is unfortunately missing under Linux is the tray icon. However, this is not supported by the client itself, so it makes no difference whether you download the Flatpak, a system package or the official TS6 client from the website (please add this for TS6 Linux :pleading_face:).
(Forum Thread / GitHub Issue)

Further differences to the Windows client are currently unknown. However, with the necessary dependencies, packages for your own distribution as well as the official download and the Flatpak should work.

However, I noticed that opening the client directly as a Wayland window introduces some additional errors. If I am not mistaken, the client opens as an XWayland window under KDE by default. So maybe check if that isnā€™t installed correctly.

If it still doesnā€™t work properly after that, try running it in a console and post the log, that might help the team to fix bugs. The TeamSpeak client itself also writes its own logs.

31

Bumping the thread.
Iā€™m having issues with the latest ts6 client as well.
When I attempt to start the client Iā€™m met with an error from hotkey_helper:
ā€œA referral was returned from the server.ā€
The client then starts, but I cannā€™t use any hotkeys and thus my PTT doesnā€™t work.
Tried just about every solution Iā€™ve found while googling, but itā€™s still not working..

32

Any news here? I tried still cannot start TS 6. I tried beta 2 today but nothing happens when I am starting.

Windows 10 22H2 Build 19045.6216

cef.log:
[17744:14488:0820/034507.492:WARNING:chrome_main_delegate.cc(747)] This is Chrome version 130.0.6723.117 (not a warning)
[17744:14488:0820/034507.573:WARNING:account_consistency_mode_manager.cc(77)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[17216:12904:0820/034507.942:WARNING:viz_main_impl.cc(85)] VizNullHypothesis is disabled (not a warning)

tschat.log:
[2025-08-20 03:45:07.801] [info] TSBindingBrowserTSChat ctor
[2025-08-20 03:45:07.801] [info] TSChat library version: 1

Everything else is empty.

33

Are you also using a ā€œLTSBā€ of Windows?

2 Likes
34

I am experiencing this issue and have almost identical symptoms as stated above. I am running Windows 11 Home Version 24H2. What other information is needed to more easily debug this issue?

I see the application open and then instantly clolse in Task Manager. Event Viewer doesnā€™t provide anything useful. Log files are empty except for what has already been stated in this thread. I am open to providing more information if needed

35

Problem Description:
My TeamSpeak client window is not showing up properly when starting the client. I can see the window in the taskbar preview, but when I click on the taskbar icon, the window never appears on my monitor - it only displays a blank blue screen in the taskbar preview with no interface elements or controls visible.

image
image193Ɨ266 4.8 KB

Background:
Iā€™ve been using TeamSpeak 6 client daily on this PC without any problems ever since the first beta releases. This issue randomly occurred today when I started my computer - everything was working fine yesterday. TeamSpeak 3 works perfectly fine as a backup solution.

What Iā€™ve Already Tried:
Iā€™ve searched through several existing forum topics with similar issues and have attempted all the recommended solutions:

From the community discussions I found:

Solutions attempted:

  • Cleared all application data: Completely removed TeamSpeak folders from %AppData%\Roaming\ and %AppData%\Local\ before reinstalling
  • Multiple clean reinstalls: Uninstalled and reinstalled TeamSpeak several times using the official installer
  • System restarts: Restarted my PC multiple times between troubleshooting attempts
  • Launched as Administrator: Right-clicked the TeamSpeak executable and selected ā€œRun as administratorā€
  • Launch parameters tested:
    • --no-sandbox parameter (no change - still blue screen)
    • --disable-gpu parameter (this changed the blank screen from blue to gray in the taskbar preview, but still no interface)
  • Compatibility mode: Tried running TeamSpeak in Windows 7/8 compatibility mode
  • Graphics driver update: Updated my graphics drivers to the latest version
  • Windows updates: Ensured my system is fully up to date

System Information:

  • TeamSpeak version: 6.0.0-beta2
  • Windows version: Windows 11 Pro (Build 26100)
  • CPU: AMD Ryzen 9 9950X3D 16-Core Processor
  • RAM: 64GB DDR5
  • Graphics card: NVIDIA GeForce RTX 4090
  • GPU driver version: 32.0.15.8115 (dated 21.08.2025)
  • Monitor: 57" Samsung Odyssey Neo G9 (G95NC) (Ultrawide 7680 x 2160 @ 120Hz)
  • Motherboard: MSI MPG X870E CARBON WIFI

Additional Details:
The TeamSpeak 6 process appears in Task Manager as running normally, and I can see the window preview in the taskbar showing a blank blue/gray screen, but clicking on the taskbar icon never brings the window to my monitor. No error messages are displayed during startup. TeamSpeak 3 works without any issues on the same system.

Given the ultrawide monitor setup, Iā€™m wondering if there might be a window positioning issue or scaling problem that emerged after a recent update.

Request:
Has anyone encountered this specific issue recently with TS6 beta2? Since this worked perfectly until today on the same system, Iā€™m wondering if this could be related to a recent Windows update, driver change, or display configuration issue with ultrawide monitors. Are there any additional troubleshooting steps I should try that arenā€™t covered in the older forum topics?

Thanks for any help you can provide!

36

Thanks for the detailed post:

  • Can you try renaming the database within this folder?

    • settings.db ā†’ oldsettings.db
    • %appdata%/teamspeak/default

  • Can you try renaming the cache within this folder?

    • Default ā†’ OldCache
    • %localappdata%/teamspeak/cache

  • Please try starting the client with this start parameter --cpa=ā€œTestā€

    • This will create a new user profile for the TeamSpeak client. You can either use this in the CMD but will probably not be a persistent fix. Therefore you should add that to the desktop shortcut.

  • Have you tried a different installation path? Maybe on a different drive?

  • Did you try moving the window with keyboard shortcuts?

Keyboard shortcuts to move a window

Snap an App Window

In Windows, there is a feature that allows you to snap the window to the right or left side of the computer screen. When dragging the window to the left or right, it will automatically snap to the side and resize.

Here are two keyboard shortcuts to move window:

  • Win + Left Arrow: snap the window to the left
  • Win + Right Arrow: snap the window to the right

Besides, there are some other keyboard shortcuts to manipulate the active window:

  • Win + Home: minimize all windows except the foreground window
  • Win + Up Arrow: maxmize a window
  • Win + Down Arrow: minimize the window if the window is not maximized, or else, it restores the window to its original size
  • Win + Shift + Up: maximize a window vertically

Move Window to Another Monitor

If you want to move your window between multiple monitors, use these keyboard shortcuts:

  • Win + Shift + Left Arrow: move a window to the monitor on the left
  • Win + Shift+Right Arrow: move a window to the monitor on the right

Watch an Expert Guide - Move Window with Keyboard (3 Key Tips)

What happens when using the latest version of TS5 [Download 5.0.0-beta77]?
The last version before TS6 got released?

2 Likes
37

Thanks for taking the time to help me troubleshoot this issue! Here are the results:

What I tried from your suggestions:

  • Moving window with keyboard shortcuts: I had actually tried this before - the problem is that I canā€™t even properly select the window via the taskbar, so keyboard shortcuts donā€™t work either.

  • Renaming settings.db ā†’ oldsettings.db: No change, still blank blue screen in taskbar preview.

  • Renaming Default ā†’ OldCache: No change, same issue persisted.

  • Starting with --cpa=ā€œTestā€: This worked! The client started normally with the new test profile.

Resolution:
Since the new profile parameter worked, I realized it was definitely a profile/settings issue. I then completely cleared both the %appdata%/teamspeak and %localappdata%/teamspeak directories again. After that, TeamSpeak started with the initial logging screen and has been working perfectly ever since.

Additional note:
Interestingly, I had the exact same behavior on my second PC (laptop) as well, and resolved it the same way. It seems like there was some weird glitch with my account data or corrupted settings that affected both machines simultaneously.

I didnā€™t need to test the TS5 version since my problem is now resolved.

Thank you so much for your time and help! Iā€™m very grateful that the problem is resolved. The --cpa="Test" parameter was the key that led me to the solution - it confirmed that it was indeed a profile corruption issue rather than a broader system problem.

1 Like
38

Iā€™ve tried all of the above, no luck still.

What I am experiencing
Launching TeamSpeak results in no window. I do notice a process within Task Manager start but then closes within 1 second. I tried the steps seen above, even uninstalling again and downloading version 5, I still have the same thing. No launch, no error in log files.

1 thing to note, I used to have TeamSpeak 3 installed around 8 years ago, would that have any conflict?

39

It should not conflict with the TS3 installation as it is a different installation path.

  • Have you had TS5/6 installed at some point before and was it working?

  • Do you have any anti virus software running which might block the start?

  • Did you try the steps Lokzmir mentioned?

2 Likes
40

All of the above was attempted, still no luck. I do see the program appear in Task Manager for a split second, then it closes.