Update of MSI download


Could the MSI downloads for x86 & X64 (Teams Machine-Wide Installer) please be updated as a matter of urgency?


My Teams client on my PC was updated from version to on June 3rd, but the MSI download links:





Are still downloading version


Before anyone asks why it matters, this is for regular maintenance of VDI environments...





11 Replies
Thanks for your comments. Please open a feature request at our Uservoice feedback forum: https://microsoftteams.uservoice.com/
Er, that's not the MSI, as I specifically requested in my original post?

@Eric Marsi where or how did you find this version number?

Since if I go to https://docs.microsoft.com/it-it/microsoftteams/msi-deployment I can only get



The client itself auto-updates. If you simply know the above link, you can replace the client version number in it and get up-to-date files. This came from a production (GA/Ring4) Tenant.

As I've supposed.. 

But if I click "Check updates" I don't get this version..

Anyway thanks 


Exactly my problem. The links in my OP are supposed to be 'placeholder' links to be able to download the latest available version.


@Eric Marsi 

I'm not sure how much more you could get wrong:


My OP was asking about the Machine-Wide Teams installer, for updating a VDA environment. As per Microsoft's own instructions to update this, you first have to uninstall the previous version. That does not sound like automatically updating to me.


You also provided a version-specific link to a .EXE binary to download, when I'd specifically asked for the latest version of the .MSI binary. It is all very well posting a link to the latest version at that very moment, but as I said to Massimo above, the whole point of the aka.ms download links (or indeed the link that Massimo refers to) is that they enable you to download the latest production version at any time.


Not really MVP-level knowledge in my humble opinion.

@jdseymour1978  Wow, that's a bit harsh.

I can only assume it wasn't meant that way when it was originally written and has translated poorly to text or you were super frustrated at the time.

Whilst I can appreciate your frustration at getting potentially unhelpful information. There is no reason to belittle someone based on their title. Remember that MVP's are admins, just like you. We don't work for Microsoft, we don't have a special "magic book" with everything in it next to us and we spend our free time helping individuals such as yourself for free in our own time.

I can't speak for Eric, but for myself, it was to give back to the community that helped me when I was a wee young sysadmin running exchange 2003.




Anyway, back on topic.

I understand the frustration of working with VDI servers and clients myself having been dealing with it since Lync 2013.


My understanding is one of the main reasons the placeholder is on a specific version is because of the Office365 rollout strategy. With that version being the "safest" version to deploy regardless of tenant status and VDI plugin build.


Your Teams client will update itself depending on many things, including the ring you are on, your tenancies environment/region, the rollout stage on your tenancy/ your office update channel (Preview/Targeted/Current) status etc. None of which can be determined by a simple URL redirect.

(interesting fact, you can kinda get Teams to do weird things by jumping from a TAP tenant to a normal tenant using the same build. Despite flags being set to remove features some weirdness still occurs)


I assume you're already across it, but if your running Teams in a VDI environment you are running the VDI plugin/registry changes as well?



Hope this helps.

Thank you for your reply @James Arber. MY response was written in a moment of extreme frustration, leading to a tone that is regrettable, for which I apologise to you and @Eric Marsi. I take on board your point about the responses being done by people in their own time. MY frustration was that my original post had not been read properly; my query was regarding MSI binaries not EXE ones, and was regarding the aka.ms placeholder links rather than specific versions.

Unfortunately our VDI deployment is 'on premises' and not in Azure, so your link is not strictly relevant to our configuration. Plus the documentation I have read regarding a VDI installation (ALLUSER=1) is that the updates have to be done manually, by removing the old version first prior to installing the new version.

Your best bet then is going to be determining the build number based on an SOE machine in your environment, then downloading that version using the links Eric advised before.
(Interesting fact, the MSI's literally just contain the EXE.)

As I hinted to before. the AKA.MS links cannot determine what version of Teams is appropriate for your Tenant Region / Roll out Status / Channel / Preview status / User preview policy so are typically kept at a Safe version assuming the desktop client will auto-update. Which obviously won't work in a packaged VDI image.

Edit: Spelling mistake