Anybody experienced all of a sudden TMA not loading properly on this version? Teams 24215.1007.3082.1590. You get a run time error. on version teams version when checking the plugin com add-on in outlook. I done almost a dozen of these with good successful results, noticed this is a customers environment today. Decided to go back into my lab and I started getting the same thing. Tried 3 different community scripts to validate it not my script and got the same results. For some odd reason and I say extremely odd. By not installing the meeting add-in separately. It works fine and unpacks things they way it was originally designed before the separate install of the TMA msi. but doing it via all users switch(separate install) as most of us do, it appears to choke. Still analyzing things on my side to validate. But I'm curious if others have seen this in the last couple of days. Fresh install any OS but 2019. Seen it in my lab today, customers setup and server 2022 now. FSLogix HF4 and CPM containers, also just doing a local profile to rule things out from a vdi prespective

@Ray Davis that known good snapshot I mentioned in the other thread that never had the issue with TMA, now does the same thing all of the sudden. Makes no sense

I am guessing no one else has issues lol.

I think everyone’s sick and tired of the teams nonsense

Correct me here, but outlook would pull in the plugin from the path the TMA msi was installed. Therefor showing under coms add in it would be to that team add-in dll to machine wide installer. Now with 24215 I am see its looking for it from the user profile app data location as if it was a user install and its looking for TeamsMeetingAd-in folder name. Which was TeamsMeetingAdin location before. Resulting in the LoadBehavior regkey switching back from 3 to 2, because it cannot find the path anymore. You can force it back to 3 but if the path isn't found it goes back to 2 by design. Anybody that on a version before 24215, what is your plugin path showing in outlook under coms add location?