Client Beta 72 won't start anymore

TeamSpeak Client
4

Please try to answer all the questions from my Last Post.

Additional questions to this.

Which Operation system is this?
What Happens without Restart Button? Just Close the client and then start it manually.

2 Likes
5

OS: Windows 10 Pro
Restarting it manually doesn’t change anything, it just wont open

6

Have you checked the task manager, if there are any running tasks still there?

7

nothing there

8

Is there a way to stop ts from updating automatically, so that i can at least use it on the version before the update which is working?

9

Auto update can’t be disabled.

My first questions about a log or anything else remains unanswered.

Also make sure that your drivers are up to date and hardware still got some updates the last 2 years.
Same counts for Windows updates.

You may try to start the client with this parameter --no-sandbox
Explained in more details.

2 Likes
10

Adding this changes nothing for me. As for the logs, I don’t know how to get them :-/

11

  • Edited my post. Must be --sandbox as shown on the picture.

  • Open this folder. Clear all files in there. Then start the client.
    %LOCALAPPDATA%\TeamSpeak\Logs\Default

Remains

1 Like
12

Everything is up do date. Which file should i send, i guess its the cef.txt ,is it?

13

All in a zip.

1 Like
14

but i got i got 850 files in there

15

i wrote this!
Then start client and send what is generated.

2 Likes
16

Oh sorry, but i cant send zip files, they aren’t authorized to send

17

Upload it here https://easyupload.io/ or anywhere else you want.

PS i will move the conversation to a new thread where it is only about your issue!

1 Like
18

got it. Upload Files Easily | Fast File Upload and Sharing Up To 10GB

19

@Vantreex
Ok shows nothing i can work with.

  • What hardware do you use?
  1. Press Win + R key
  2. Type dxdiag
  3. In the dialog you will find Save All information
  4. Upload the file

  • is there a crashdump? Please clean folder first and then start client and see if a new one is generated.
    %LOCALAPPDATA%\TeamSpeak\User Data\Crashpad\reports

  • Anything in windows error report about that crash?

  1. Press Win key
  2. Type Event Viewer
    In the event viewer you find Windows logs > Application
    In Level should be a red x
2 Likes
20

The Event manager didn’t show any errors. Upload Files Easily | Fast File Upload and Sharing Up To 10GB

21

Thanks. Forwarded the crash dump to a developer.
Can not tell if there is going to be a fix soonish. Most of the company (including me) is on holiday already.

I got no idea what else i could ask.

As a temp solution you may use TS3 or beta 70 and delete the next.patch file from the config folder when stopping the client
Or use b71 and delete the next.patch file after you stopped the client.

Config path is:
%AppData%\TeamSpeak\Default

Beta 71 does crash often when pressing the mouse. So b70 is the better choice.

Unofficial beta 71 client. I can’t grab the official installer after our Build systems moved.

3 Likes
22

Yep, it works. Many thanks. Hope there’s gonna be a real fix out soon, but this will do for now. Until then, I hope you have a Merry Christmas and a good start into the New Year.

23

Thanks . You too :smiley:

We analyzed the crash dump and your crash happens in Chromium / CEF.

It looks like in your system Google’s OAuth2 is active and maybe set as an environment variable.
Now Chrome / CEF based applications will use this way to identify the user. Our application does not need and support that.

Similar to (read the comments. especially the last one)

Our Devs can’t fix this problem.
Now you must act and decide what to do:

  • Option 1 live with this
  • Option 2 wait for later updates and maybe a different Chrome / CEF will no longer trigger this crash. This is not in our hand.
  • Option 3 Remove the OAuth environment variable from you system or make it so it only uses specific apps (we do not know how to do this. This requires you to read Google’s Documentation in case there is one.
4 Likes