Forum Discussion
Bug Report: Quitting Teams app restarts it
Hello,
When quitting Teams for Windows the app restarts automatically by displaying the following message at the top "There was a glitch, and we had to restart the app. It's good to go now. until I quit it again and then it remains closed. Does anyone knows how to address this issue?
Thank you.
40 Replies
- tomthefocusmanCopper Contributor
I fixed this by restarting the device and disabling GPU hardware acceleration in the Teams settings before it crashed.
- Micael700Copper ContributorIT too got fixed here by itself. i dont think disabling gpu acceleration has anything to do and will hurt your perfs more than anything.
- Derek_WilliamsCopper Contributor
Micael700 It is still happening for me years later, and I am on the latest Apple MacBook with up-to-date macOS. I don't understand how a giant like Microsoft can build an app that you can't close. I'll try restarting the MacBook and see if that does anything. I am on an Edinburgh University account, so will report to them too.
- GeorgeMakrakisCopper Contributor
It seems that this bug is fixed in the latest updates.
- Peter Dam vanCopper Contributor
GeorgeMakrakis Seems like it. I happened to have re-installed my machine last friday and got all the most recent updates for everything. When I exit MS Teams now, it stays closed. Like it's supposed to.
Would be nice of Microsoft to drop by and confirm that this issue is indeed resolved. I really wonder what was the actual cause of this.
- LiquidFractalCopper Contributor
Peter Dam van Yep - Teams seems to have quietly fixed itself; I'm not getting this issue any more either. But this does nothing for my "consumer confidence" - was it fixed because someone took a look at Teams, or did some Windows Update haphazardly address the issue?
I ask because I know how sprawling and sloppy MS code and apps can be, so while I no longer get this issue (happily), I'm not ready to say MS "fixed" it.
- KrisDebSteel Contributor
OK, guys, I fixed it on my Surface:
It works for me in exactly this config:
- Micael700Copper Contributorheeeeeee, yep, changing anything will make it crash upon quitting... but I don't want auto-start!! What the....
- PatrickC50Copper ContributorI followed the instructions at the link below and it did the trick
https://answers.microsoft.com/en-us/windows/forum/all/teams-auto-restart/66615783-e6f8-4192-9a4f-6490eb080d82- BetaMenschCopper Contributor
PatrickC50Didn't work for me, but I appreciate the suggestion. I have neither the time nor the inclination to chase after MS to fix issues it obviously has so very little interest in fixing. Frustrating...
- nikohCopper Contributor
PatrickC50I tried clearing all the cache listed in that post, including Temp Internet Files and whatnot. Did not help at all, Teams still restarts every time I quit it.
- LiquidFractalCopper Contributor
PatrickC50 Thanks for the suggestion, but it did nothing to help my situation. Still glitching out when I try to exit (the only time it doesn't glitch for me is if I exit Teams without actually doing anything - which is, of course, useless).
And I'll reiterate: even if this did work, WHY should I go to such lengths to fix problems which should be handled by the software itself? It feels like I'm bug fixing when MS should be doing this!
- KrisDebSteel Contributor
I'm with you! Running 3rd party PowerShell scripts to fix chat app? What if I'm typical freelancer / smb user and I just don't know how to even run PS? What kind of advice is that?
- RichLonghurstCopper ContributorM$ fix this - quit means quit, not maybe later.
- LiquidFractalCopper Contributor
GeorgeMakrakis I have exactly this problem: I exit Teams, and it's caused my computer to completely freeze up at the worst possible times (e.g. during intensive processing sessions).
One time, after my HD was running so hard that everything (including sound) was stuttering and freezing, I hit Ctrl-Alt-Del to get the Task Manager (which took 5+ minutes to appear). It showed that Teams was taking up 3.8GB of memory and 91% of my HD resources!
The only thing I can suggest to others is, with MTSBob, that after exiting Teams (once or twice, as you require
), get into the Task Manager and end the Teams task (since it's obviously still there after exiting) - that's the only way I've ensured that it goes away.
What's worse: I have Teams installed on a desktop, a laptop and a mobile. Two months ago I deleted 4 Teams channels which were no longer required; on my desktop and my mobile they are gone, but when I boot up teams on my laptop they are STILL THERE after 2+ months and I CANNOT delete them. Mobile and desktop, fine - my laptop, nooooo…..
Sorry....Teams sucks. Microsoft, get off your collective butts and DO SOMETHING.
- BetaMenschCopper Contributor
LiquidFractalWe've unfortunately had to find an alternative and will soon remove teams altogether. Too buggy. Shouldn't be used in a production environment until it's actually ready. Genuinely sick of paying MS for beta software. And if it isn't beta software, then QC should all be fired...
- LiquidFractalCopper Contributor"Genuinely sick of paying MS for beta software" - nailed it.
And the crickets I hear from Microsoft's side of this says it all.
- Peter Dam vanCopper Contributor
In addition: I also have another issue with Teams. If I close the Teams app manually right before I shut down my computer, it will cause a critical error during the shutdown-process:
"The instruction at [address] references memory at [address]. The memory could not be read."
This seems to be caused by the automatic restart of the Teams app WHILE Windows is attempting to shut down. If you time the close-Teams-and-shutdown-Windows just right, I suspect more people get this error. I've managed to recreate it on several other machines (with colleagues).
- dinosmCopper Contributor
Same here. This is really frustrating. I have a low-memory laptop and Teams insists on being open, which takes up precious memory that I need for other tasks!
Constructive answers are one thing, but this is such a basic issue that it's just astounding Microsoft has not been able to a) detect it during their own testing and b) fix it for such a long time!
- AndyGadgetCopper Contributor
Its now feb and the problem continues - sometimes it takes three attempts to quit teams.
Please fix this app now - how it was ever released as a product in this state is ammazing - do they really expect the active ( subscription paying ) community to work as beta testers?
- TadeuszKMCopper Contributor
Also have this bug. Rather annoying, and is getting me a LOT of flak from the higher-ups.