petben Posted September 23, 2025 Posted September 23, 2025 We deploy Teams with the other Microsoft365 Apps to the default folder C:\Program Files\WindowsApps\MSTeams*. When users (including admins) open Teams it opens as below 'Teams needs an update' and no further options. Can't see any filtering issues. Manually running ms-teamsupdate.exe from the WindowsApps\MSTeams folder does nothing. Microsoft says it should auto check and update every few hours, we have 100's of machines on different Teams versions, depending when Win11 was installed. Any ideas...?
machy Posted September 23, 2025 Posted September 23, 2025 Teams is a pain. It installs the installer to the C Drive, then installs to the user profile, which is the version effected by updates when the user is updated. You will need to update the MSI You are pushing out (I think once a term the last time i looked at dates and how long versions can update too) Anyone having issues will need a profile wipe, or to manually update teams.
MYK-IT Posted September 23, 2025 Posted September 23, 2025 We deploy Microsoft Teams via Machine-Wide installer method Bulk deploy the Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn which manages to maintain and update OK. We did have some clients with the older per-user installation that caused similar outdated prompts you are experiencing. We just uninstalled those instances. Latest versions of Microsoft OneDrive client Versionen – Hans Brender's Blog
petben Posted September 23, 2025 Author Posted September 23, 2025 MYK-IT how do you deploy the Bootstrapper version? do you have some kind of 'If version is current then exit' process? we would probaby go for Powershell startup, but the latest versions of Office aren't supported installing as system, which this would also be. Thanks for any ideas.
colly72 Posted September 23, 2025 Posted September 23, 2025 Try using Action 1 to push out Teams - it uninstalls the per user install and replaces it with the machine-wide version. It's been a god send for us!
MYK-IT Posted September 23, 2025 Posted September 23, 2025 (edited) Apologies.. totally mixed up MS Teams and OneDrive! 🫣 Just checked, we are deploying MS Teams part of Office install (e.g. config.office.com) Edited September 23, 2025 by MYK-IT ignore
2097 Posted September 30, 2025 Posted September 30, 2025 (edited) On 23/09/2025 at 10:02, petben said: We deploy Teams with the other Microsoft365 Apps to the default folder C:\Program Files\WindowsApps\MSTeams*. When users (including admins) open Teams it opens as below 'Teams needs an update' and no further options. Can't see any filtering issues. Manually running ms-teamsupdate.exe from the WindowsApps\MSTeams folder does nothing. Microsoft says it should auto check and update every few hours, we have 100's of machines on different Teams versions, depending when Win11 was installed. Any ideas...? Ours is doing the same , Our original package was created in Oct 2024 , and has been updating fine ( Machine installer ) May need to create a new package and push it out again with the latest version. I created the package before using the bootstrapper. Edited September 30, 2025 by 2097
SeniorFeet Posted October 1, 2025 Posted October 1, 2025 We had the same issue, the bootstrapper we deployed in June 2024 evidently doesn't support the latest updates. As it is only impacts new profiles that haven't auto-updated Teams, the issue hasn't been that widely reported yet. We've just deployed the latest bootstrapper from Microsoft and it seems to have resolved the issue with Teams on new profiles. The most difficult bit was identifying a robust detection method, in the end I just created a tag file and checked for that.
DavR Posted October 1, 2025 Posted October 1, 2025 5 minutes ago, jackfeet said: We had the same issue, the bootstrapper we deployed in June 2024 evidently doesn't support the latest updates. As it is only impacts new profiles that haven't auto-updated Teams, the issue hasn't been that widely reported yet. We've just deployed the latest bootstrapper from Microsoft and it seems to have resolved the issue with Teams on new profiles. The most difficult bit was identifying a robust detection method, in the end I just created a tag file and checked for that. If you're using InTune, there's a custom detection script available on the MS deployment page. I'm not sure whether it can discriminate between different versions, though. If you're installing with a startup script, we use the following if exist command to check for a specific version: If exist "%PROGRAMFILES%\WindowsApps\MSTeams_25212.2204.3869.2204_x64__8wekyb3d8bbwe\ms-teams.exe"
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now