Forum Discussion
Windows Explorer Crashes / Microsoft Team
osamamansoor
Did you deploy Teams using "Teams Machine-Wide Installer" within your org?
If so, please check if new users on an affected mashine are showing an old version of "Microsoft Teams Meeting Add-in for Microsoft Office".
We are having the same issue at one of our customers and noticed that the plugin is sort of stuck at very old version (1.0.x) but as of today should be be at version >1.23.x.
Since new useres are still getting this old add-on version despite having a recent teams client installed, i supect a broken "Teams Machine-Wide Installer" installation beeing the root cause.
We inspect it further and keep you guys up to date.
In this specific case, we were able to identify the root cause. Affected users had attempted to use the "New Teams Client" but were reverted back to the classic Teams version due to a global policy. Despite this, the new client remained installed and continuously attempted to update the Outlook Add-on in the background. This action repeatedly led to the issues described in this thread, including crashes of Explorer, Teams, and other Office applications.
Look for "MsiInstaller" errorcode 11321 within the eventlog followed by "RestartManager" events.The resolution for the affected users was simple: removal of the new Teams client. This was achieved with the following command:
Get-AppxPackage -Name MSTeams | Remove-AppxPackageIt's important to note that the "Microsoft Teams Meeting Add-in for Microsoft Office" in Version 1.0.x is associated with the classic Teams, whereas versions >1.2x are for the new Teams client.
The affected customer plans to transition to the new Teams client at the beginning of next year but is currently using the older version due to compatibility issues.