the new teams keeps on crashing

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.

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.

For anyone that states, uninstall it and reinstall.

This is an IT admin role.

Most subscribers have zero access to the information and credentials to allow this response.

I do not like to down vote, but I must in this instance. If MS admins disagree, please downvote. Also please leave active so resolution seekers can fix a viable solutions instead of noise. And if downvoted, please leave a link to 2024 active links to follow.

For anyone that states, uninstall it and reinstall.

This is an IT admin role.

Most subscribers have zero access to the information and credentials to allow this response.

I do not like to down vote, but I must in this instance. If MS admins disagree, please downvote. Also please leave active so resolution seekers can fix a viable solutions instead of noise. And if downvoted, please leave a link to 2024 active links to follow.

What are you trying to say? Most of us here are sys admins getting mad with the problem raised from end users like you. We're in the process of gathering and sharing potential solutions, that's how IT job works, going by chances until you find a fix/workaround.