I'm fighting with the Outlook teams meeting add-in. I did the install with the correct ALLUSERS=1 parameter etc. I also checked the registry and confirmed the fastconnect entries are there. However, my teams add-in doesn't load and says "A runtime error occurred during the loading of the COM addin" when I check under COM addins in Outlook. If I run "%SystemRoot%\System32\regsvr32.exe /n /i:user %LocalAppData%\Microsoft\TeamsMeetingAdd-in\1.24.19202.0\x86\Microsoft.Teams.AddinLoader.dll" it works next time I launch outlook but I have to do this everytime. I've not had to do this in a different environment. Am I missing something? I'd rather fix this without resorting to login scripts etc.

You're not alone.

Known issue. Outlook does not append „.0“ to the version number therefore searches in a non existing directory

You have a link on the known issues? Not questioning you, 4 am this morning I tore this apart and found the same deal. I been rewriting scripts to temporary fix it.

Just a chat with an msft guy. Nothing official

This add-in issue is for more recent Teams version? Did you try an older revision?

The hoops you have to jump through to install this program in VDI is bananas

Hi, you're installing for All Users, but using regsrv32 to Local User. New Teams v2 is PITA. If you don't install Add-In using ALLUSERS=1 it will install automatically in Local User when user first start Teams. So best way for now is to have an install script that install both New Teams and Add-In (remember to uninstall Add-In prior, yeah it doesn't auto upgrade if older version is already installed). Work in progress, but had lots of tickets this week in #CK6TKS43U

Even if you install the add-in as all users with the latest 2 builds it doesn't honor it, it keeps trying to pull from the users directory.

Then when it pulls from the user directory, it missing the .0 Example

Get-AppLockerFileInformation -Path "C:\PROGRAM FILES\WINDOWSAPPS\MSTEAMS_24026.1000.2656.1710_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" | Select -ExpandProperty Publisher | select BinaryVersion

BinaryVersion

What is in the MSTeams WindowsApp extraction

1.24.2203.0

Outlook complains because it wants: ( Again, resulting in per user, which should NOT do this) C:\Users\%username%\Appdata\Local\Microsoft\TeamsMeetingAdd-in\1.24.19202 with no 0 Even if you run, for example purposes Start-Process "c:\windows\System32\regsvr32.exe" -ArgumentList @("/s", "/n", "/i:user", "`"$TargetDir\x64\Microsoft.Teams.AddinLoader.dll`"") -Wait Or Start-Process "c:\windows\SysWOW64\regsvr32.exe " -ArgumentList @("/s", "/n", "/i:user", "`"$TargetDir\x86\Microsoft.Teams.AddinLoader.dll`"") -Wait It still pulls the user side from outlook. I have work arounds to fix this, but it's a temp solution, until they fix it.

I have a rhetorical question about this bug....its so egregious, how did this not get discovered during testing before release?

So much going on these days, human error is going to happen. Other than that, just suck it up and move forward LOL. not sure man.