the new teams keeps on crashing

I am uncertain how M(b)S measures effectiveness anymore.

I work in a hosted implementation. Oooh pretty. MS hosed outlook. OK... I could care less, they killed off MS admins several years ago.

Teams is ok for meetings. Teams with Files. I will give a 2 percent. Do I have metrics? No. It will work "sometimes". Can I quantify sometimes. No. It sometimes stays open and allowing me to stay in teams. The "REST" of the time, I get kicked out, with lost documents. I have had people report me for "being unavailable in meetings.". I thought I was in the meetings, I opened a document, and "Poof" MS magic, I am gone.

Teams...

Meetings work.

Shared documents. "To me a 100% fail." If you love it, please demand they make it work for about at least 5%." I am not the only one. But I do not think most people actually scratch to 10% surface.

Give me back a desktop that I keep backups.

I keep copies.

Archives.

I am responsible. Because cushy warm feelings, havent come over for me. MS is about billing, they get that, they fail on service.

I want cloud to be viable. MS demonstrates 1(5)%. Where does the decimal belong. I am not in a rating business. My docs are lost, I am kicked from meetings. Am I wrong to say 1.5%. I am giving a benefit of the doubt. Availability for meetings 100%. Availability with document access 0.5%. This is **** service.. So why don't I believe in cloud.

I am uncertain how M(b)S measures effectiveness anymore.

I work in a hosted implementation. Oooh pretty. MS hosed outlook. OK... I could care less, they killed off MS admins several years ago.

Teams is ok for meetings. Teams with Files. I will give a 2 percent. Do I have metrics? No. It will work "sometimes". Can I quantify sometimes. No. It sometimes stays open and allowing me to stay in teams. The "REST" of the time, I get kicked out, with lost documents. I have had people report me for "being unavailable in meetings.". I thought I was in the meetings, I opened a document, and "Poof" MS magic, I am gone.

Teams...

Meetings work.

Shared documents. "To me a 100% fail." If you love it, please demand they make it work for about at least 5%." I am not the only one. But I do not think most people actually scratch to 10% surface.

Give me back a desktop that I keep backups.

I keep copies.

Archives.

I am responsible. Because cushy warm feelings, havent come over for me. MS is about billing, they get that, they fail on service.

I want cloud to be viable. MS demonstrates 1(5)%. Where does the decimal belong. I am not in a rating business. My docs are lost, I am kicked from meetings. Am I wrong to say 1.5%. I am giving a benefit of the doubt. Availability for meetings 100%. Availability with document access 0.5%. This is **** service.. So why don't I believe in cloud.

At this point I have talked to many people in our organization.
Looks like only 25% or 30% are having this problem.
The problem is: new Teams is consistently crashing after 10 to 11 seconds. 100% reproducible.
Cleaning cache, reinstalling Teams, installing recent Windows updates, rebooting PC, etc, does not help.
Current workaround is to use teams.microsoft.com in Edge.

Looks like Microsoft is not able to make the new desktop application to work reliably? Perhaps, it is time for Microsoft to be honest to customers and retire the application and tell customers to use the web site instead, or roll back to the old, stable version? Because "Install Teams desktop application and see whether it will crash" is not an industrial-grade work instruction.

We are having the same issue on both Macs and PC's. Uninstalled new version. Cleared caches. Our default Teams Update policy was to run new version. Classic works fine, but when Microsoft controlled update kicks in, Classic on Mac stops having access to audio devices. New Teams simply shows a "connecting to meeting screen" with no access to any controls even though the user might be able to be seen and heard. Setting Teams Update policy to "Default to Classic" doesn't help. It appears it is the mere updating of new Teams that causes the issues. We also tried uninstalling Classic, clear all caches and installing only the new version, and that has same behavior. Some, but not all, PC users experiencing similar glitches. Only thing that fixed it for us was to change the Teams Update policy in the Admin center to Not Enabled, remove new version, and revert to classic.

Figure it out Microsoft. This new version is REALLY buggy. At the very least, you should revert the global default policy on teams installations away from "Microsoft controlled."

Hi thanks for your input, I did uninstall teams and delete the appdata teams cache but I did not delete the one on localdata.

I'll try this and see if it improve anything.

Today I saw on my comptuer which has ot yet has this issue that there's a teams update, maybe it will fix the problem on the impacted computers ( so far 5) , I'm hopefull that it will