TeamSpeak Server Randomly Shuts Down After Starting when using it on a OneDrive file path

Hi all,

I’m trying to run a TeamSpeak 6 server locally, but every time I launch tsserver.exe, the process shuts down immediately without any visible error or log file. It doesn’t matter whether I run it from the console or by double-clicking the executable — it just closes right away.

:wrench: Setup Info:

  • Server Version: TeamSpeak 6 (latest available version)
  • OS: [Windows 11 Pro 64-bit]
  • Run Method: Directly launching tsserver.exe
  • Log Files: None created — neither logs nor crash dumps
  • Permissions: Running as administrator; tried both normal and admin mode
  • Antivirus/Firewall: Tried disabling — no change

Edit:
I also tested the TeamSpeak 3 server on the same machine, and it runs without any issues — no shutdowns, and logs are generated as expected. This seems to be an issue specific to the TeamSpeak 6 server.

Video:
Watch 2025-07-03 21-56-35 | Streamable (Available untill 07/05)

Final Update / Solved:
Turns out the issue was caused by trying to run the TeamSpeak 6 server from a “OneDrive” folder path — even though OneDrive isn’t actually installed on my PC. The path still pointed to a OneDrive-managed directory (probably due to Windows default folder redirection), and that caused the server to shut down immediately without generating logs.

After moving the server files to a normal local folder (like C:\TS6Server), everything started working as expected.

Thanks to everyone who offered help — hopefully this saves someone else a headache!

2 Likes

Is this the first time you’ve run the executable?

Have you accepted the license agreement?

tsserver.exe --accept-license=accept

Yes, I’ve already tried starting the server with --accept-license=accept on a fresh server folder. I also made sure to run it with administrator rights, but the server still shuts down immediately with no logs or crash dumps created.

I’m currently uploading a video to show the exact steps I’m taking and what happens when I launch the server. Hopefully that helps clarify the issue.