New Teams Application Constantly Crashes, I've tried multiple fixes HELP!

Update: I found what was causing this issue. It turned out to be conflicting software. In this case this user has a specific software called "MIDS Devices" which is a microscope software. During this installation, the program made a change to the "DLL_Files_in_WINSYSDIR". The only way I found this out was since I didn't run the program as admin, it gave an error. Then once I installed it, sure enough teams crashed within 10 minutes. I decided to install the additional software this user had one by one to find any conflicting software's and this turned out to be it which makes sense as the event viewer faulting module log points to the "ntdll.dll" file.

I uninstalled the software but the changes weren't reverted. I had to reimage the users computer to get teams to not crash again unfortunately. I have reached out to Microsoft to see if they have an explanation or way this can be reverted without reimaging the computer just out of curiosity. The new teams must use this ntdll.dll file in same way, or maybe the software fights for the same resource and causing them to conflict with eachother? Although this user had this program on their old computer working just fine until an update with new teams, classic always worked fine. So must be some resource the new teams uses.

I hope to update with a reasoning from microsoft with my open ticket with them.

Here is microsofts response:

Upon investigation, our backend team has identified that the error is related to an incompatible application extension. Rest assured; the Engineering team are actively working on a solution to address this issue. However, I regret to inform you that the fix will take some time to deploy, and currently, we do not have a specific timeline for its completion.

In the meantime, I recommend uninstalling any third-party applications that might be affecting the Teams client. This step may help mitigate the issue until the permanent fix is available.

So sounds like the fix is if you want to use the teams application that bad, you will have to uninstall whatever 3rd party software is causing issues. In my case uninstalling the conflicting software didn't resolve the issue as it didn't revert the changes it had made, it had to be reimaged. Maybe that's the specific software that decided not to revert the changes, maybe other's wont have this issue after uninstalling? The 3rd party software I had installed confirmed it was the issue though as this was the first software I installed where teams then began to crash afterwards. Software is no longer on the computer and teams doesn't crash.

Otherwise, just use the web based version for now if you have a 3rd party software that needs to be used.

Update as of 5/10. I have still been troubleshooting with Microsoft and they have failed to solve the issue. They have requested I send multiple logs, (5GB worth) and are still evaluating them. The fixes they have suggested have not helped. I will post once I get a fix.

Ditto......in an RDS environment, even in server 2022.....complete and absolutely unstable. The NEW Teams "team" should be ashamed....this has been persistent for MONTHS w/o any real solution. Just keep kicking the can down the road. Zoom here we come.

Update: I found what was causing this issue. It turned out to be conflicting software. In this case this user has a specific software called "MIDS Devices" which is a microscope software. During this installation, the program made a change to the "DLL_Files_in_WINSYSDIR". The only way I found this out was since I didn't run the program as admin, it gave an error. Then once I installed it, sure enough teams crashed within 10 minutes. I decided to install the additional software this user had one by one to find any conflicting software's and this turned out to be it which makes sense as the event viewer faulting module log points to the "ntdll.dll" file.

I uninstalled the software but the changes weren't reverted. I had to reimage the users computer to get teams to not crash again unfortunately. I have reached out to Microsoft to see if they have an explanation or way this can be reverted without reimaging the computer just out of curiosity. The new teams must use this ntdll.dll file in same way, or maybe the software fights for the same resource and causing them to conflict with eachother? Although this user had this program on their old computer working just fine until an update with new teams, classic always worked fine. So must be some resource the new teams uses.

I hope to update with a reasoning from microsoft with my open ticket with them.

No, they originally said it was pointing to the intel smart array microphone, I reinstalled the driver but the user is still experiencing crashes. They are still investigating and cant seem to give me a straight answer even after sending them multiple logs.