Forum Discussion

jdseymour1978's avatar
jdseymour1978
Brass Contributor
Jan 14, 2021

Teams client not updating

Hello,

 

Microsoft Teams client on Windows 7 endpoints (with ESU) - 32-bit client, and Windows 10 - 64-bit client are not updating via Avatar -> Info -> Check for Updates

 

Teams is installed on both endpoints in Machine-Wide mode with source=default

 

Checking storage.json in %AppData%\Microsoft\Teams\  the latest version (.nupkg) that it pulls down is 1.3.00.28779.

 

I can manually download from https://statics.teams.microsoft.com/production-windows-x64/1.3.00.32283/Teams-1.3.00.32283-full.nupkg

 

Any idea on how to resolve?

 

Thanks,

 

Jonathan

Administrator
best practices

20 Replies

  • AC_Martin's avatar
    AC_Martin
    Copper Contributor
    Apr 16, 2021

    jdseymour1978 

     

    I just wanted to pop in here and share my findings, because I've had a lot of troubles updating Teams in our environment. Our users have started to see "Teams needs to be updated" whenever they open Teams and we have tried manual updates but it keeps coming back.

    In our case, uninstall/reinstall, clearing cache, adding the user temporary as local admin to install update and a few other attempts didn't solve our issue, so I did some digging and here's what I found:

    We opened Task Manager -> Processes tab, right clicked the top bar with all the headings and toggled process name and command line on. After that, expanding the Teams-app in the list revealed that the executable was actually run from the "Default"-user directory.

    So I shut down teams, and then uninstalled Teams through control panel add/remove programs, and verified that it was also gone in the new Windows 10 Settings -> Apps window.

    Then I changed the name of the following folder:
    C:\Users\Default\AppData\Local\Microsoft\Teams
    To
    C:\Users\Default\AppData\Local\Microsoft\Teams.old

    And finally reran the installation, and that appears to have solved our issue. Hopefully this will help some of you who experience the same.

    • Briggidy's avatar
      Briggidy
      Copper Contributor
      Mar 25, 2022

      AC_Martin 

       

      I was playing around with this a little today.  Try this.

       

      Download the latest - https://statics.teams.microsoft.com/production-windows-x64/1.5.00.7765/Teams-1.5.00.7765-full.nupkg

      then from the cmd line run

      c:\users\<userdir>\AppData\Local\Microsoft\Teams\Update.exe --update <path to nupkg>

  • jdseymour1978's avatar
    jdseymour1978
    Brass Contributor
    Feb 05, 2021
    Now stick on 1.3.00.34662 on my domain PC (Windows 7, Teams 32-bit). Again, I can manually download the nupkg for 1.4.00.2781.

    Some pointers on diagnosing this would be appreciated
    • jdseymour1978's avatar
      jdseymour1978
      Brass Contributor
      Jan 14, 2021

      adam deltinger 

      Thanks for your reply. It's not the machine-wide installer that I'm worried about updating, it's the per user client that is installed by the machine-wide installer on logon. This is on PCs/laptops, installed as per the instructions with the MSI property  ALLUSERS=1 set. I'm aware that the VDI installation - installed with the MSI properties  ALLUSERS=1 ALLUSER=1 - needs uninstalling and then manually updating, but this is not the case with the regular PC version.

       

      Until recently, checking for updates in the client would force the client to check on the Internet for a newer version (.nupkg) and update and then prompt for restart, but this is no longer happening.

Resources