Force Teams desktop client update

IanMurphy48 

I would suggest you check out the recently shared blog that explains a little about the update process at Why do I not see a feature but my colleague does? - Release Processes Microsoft Teams.

As explained it's entirely normal to have different versions while deployments are happening slowly, things are a little complex at the moment due to some delays, an apparent rollback and new versions through TAP and Public Preview. So if your users are guests in other tenants that may be in TAP you could be getting versions from there, I'm a guest in the microsoft tenant so my versions vary wildly.

As PDSDavid correctly explained the Machine Wide installer is more like a stub to create the installation for each user. Also the regular msi will be a little behind the newest version you may see, it trails rollout and doesn't lead.

It is quite unlikely that any specific build would cause the issues you describe, and that would seem to be largely verified by it remaining after a reinstall. I would be looking into driver versions perhaps.

Teams update process is unorthodox in enterprise, more like a consumer app, but this is deliberate from Microsoft to manage the far faster pace of change in what is really a web application in a wrapper. In my experience across Teams at many organisation it is very robust, the only issues I've seen are in locations where network restrictions are preventing access to the download service. Microsoft were planning to provide some more admin control, allowing you to control the day of the week and so on, but I think this has been pushed down the list due to priority works to support Teams being used by schools during the pandemic.