05-10-2017 02:24 AM
05-10-2017 02:24 AM
Some of our users reported problems starting the Teams desktop client today.
Problem came out of the blue, has worked before.
Gave error message "There was a glitch and we're recovering..."
05-10-2017 04:16 AM
I have users expericiencing the same issue.
The error is related to GPU Crash. Already sent an e-mail to 'email@example.com'
Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- error -- GPU process crashed, restarting the app.
Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Saved renderer crash info
Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Set restartReason state.
Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Restarting app Teams with reason crash
Waiting for feedback. So far no one is using Teams!...
05-10-2017 06:37 AM
05-10-2017 06:37 AM
I'm having the same problem on a 2008 R2 Remote Desktop environment. I just tried re-running the installer and that seemed to get it working.
05-10-2017 06:45 AM
05-10-2017 06:49 AM
I have the same environment, 2008 R2 in Terminal Server, and re-installing solved it for some minutes, but then started to glitched again...
You didn't have anymore issues after that?
05-10-2017 07:15 AM
It has started glitching again, I think it may be updating itself as I had installed an older copy of the installer.
05-10-2017 07:18 AM
I had to uninstall the desktop app to get it to stop looping through the restart. Was very annoying. Couldn't kill it from Task Manager (threw an error message when I tried).
05-10-2017 07:21 AM
Yep, I did the same and had the same problem...
Already investigate and didn't find any documentation about auto-update process and how to stop if exists.
05-10-2017 07:35 AM
05-10-2017 10:00 AM
05-10-2017 10:14 AM
Same problem out of the blue. Windows 7 Enterprise, 64 bit running in a VMware VM.
05-10-2017 06:44 PM
We have the same issue, I've raised a case with support teams, so I'll let you know how we go.
05-11-2017 02:22 AM
05-11-2017 02:55 AM
Same thing happening here too. For non virtualised desktops it is fine, but everyone else using Xendesktop suffers from that issue since yesterday.
05-11-2017 03:01 AM
Ours are almost all virtual desktops, same build on vanilla Win10 is working fine. Logs are off to the engineering teams and hope to hear more back US time.
05-11-2017 05:05 AM
I'm also getting the same issue from a couple of days,
Uninstalling and reinstalling doesn't help, I'm using this on a machine which is Remotely connected(Remote Desktop Connection).
05-11-2017 06:31 AM
We have this happening on on Win7 32bit machine. We have tried reinstalling, including blowing out the teams and Squirrel directories then rebooting and downloading a fresh installer. The problem is still happening.
05-11-2017 07:25 AMSolution
We have found a work around. The recent update is a problem. I expect the work-around will also become problematic.
What we have done is to create a shortcut to:
(change username to the current user's name)
The standard shortcut runs "Update.exe" each time Teams is launched.
Very best regards,
05-11-2017 07:39 AM
Tried the workaround to no avail. The update exe must have already updated. Tried to extract the original Teams.exe from the install package and running it from a shortcut, also to no avail.
05-11-2017 07:41 AM
05-11-2017 07:42 AM
For those users that still have the folder previous (You have the option to copy it from user to user), it's a workaround to open the application.
It's a way to force opening teams in the previous version.
I change the shortcut to a user and so far, it's ok. (Again, important to point out, this way is using the version before the problem one)
05-11-2017 08:27 AM - edited 05-11-2017 08:49 AM
Sadly no previous folder in mine. It got removed in troubleshooting yesterday.
Got a copy of previous from an unaffected co-worker. I'm back up. Thanks
05-11-2017 02:25 PM
I have been playing with this on 2008 R2 and found that if you edit the settings.json file and change the entries for
to true it will run once, but the app resets those values and it will crash the next time you try to run it.
05-12-2017 05:50 AM
I tried downloading the program yesterday and now the error message regarding the glitch has been popping up on my screen...CONTINUALLY...every 5 seconds...ever since. I can't get it to stop. I have since deleted the program from the computer. I've tried deleting it from the task manager when it pops up, I've tried "x-ing" it out when it pops up, I've tried minimizing it - NOTHING stops it. It's been over 24 hours. It pops up over everything I'm using...even typing this message. I'm about to lose my mind.
05-12-2017 05:55 AM
Can confirm workaround works for us. We manually distributed a working "previous" folder for affected users.
We have also raised issue with Microsoft through O365 support. It has now been sent to "back end engineers". Hopefully we will soon see a new update that resolve the issue. Fingers crossed.
05-12-2017 09:30 AM
Unfortunately, only one 32 bit system here and original folder got deleted before we found work around so we are unable to resolve at this time.
05-13-2017 02:30 AM
The latest update (Microsoft Teams Version 1.0.00.13152 (64-bit)) installed today fixed this issue.
05-15-2017 07:30 AM
On 2008 R2 I had to reinstall from the newest available version 1.0.00.13152 from Microsoft and then it works. When trying to run the update from the previous version of the client I couldn't get it to work.
08-01-2018 06:37 AM
This is the only thing that worked for me, thank you for the information.
10-16-2018 09:55 PM
MFA seems to break the update process? I signed out from Teams desktop app and after that the app realized need to authenticate again. Fixed the issue.
03-06-2019 01:41 AM
Facing issue while login into teams, getting error oh no .... we cant connect to the internet . Check your connection, kindly suggest.
rest everything is working fine only for teams getting error Code: Request time out.