Can't boot TeamSpeak 5 after update 72

[MightyMidget]

As the title says, Updating to TeamSpeak 5 beta 72 doesn’t let me boot TS after it is finished…
I’ve been on other topics to see if I can find a fix myself to no avail, so here I am…

Things I’ve done:
1: Rebooted PC after install, update, uninstall, and repeat…
2: Tried looking at logs located in %LocalAppData% but they’re all blank (no text)
3: Tried the Sandbox param, does nothing
4: Tested TeamSpeak 5 beta 70 and this works buttery smooth like god intended (So to my stupid mind it’s gotta be the 72 update, something is going wrong)

I can upload the logs if needs be but I’m unsure if anything will come of it… Just want to stop using Discord…

This is my first post so sorry if this format is wrong or annoying to read!

Edit: OS is windows 10 and drivers are all up to date…

[TS.ChrisR]

You may have this problem when older beta works but 72 doesn’t

Client Beta 72 won't start anymore

Thanks . You too 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 lat…

Client Beta 72 won't start anymore

It’s not Chrome to blame here. It’s Chromium we are using here. I will change that in my reply. The crash happens in Chromium / CEF and any software using Oauth2 may have added a system variable to use it or is running in background and triggers it. Ps if there are crashes generated, then there are crash dumps. (Not talking about mostly useless Windows crash dumps for software)

[MightyMidget]

I was afraid this might be it… Guess this only option I have is deal with it, fun!