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 ...
Administrator
best practices
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.

  • BrechtMo's avatar
    BrechtMo
    Copper Contributor
    Jan 22, 2021

    A lot of machines in our environment are stuck on version 1.3.00.30866 which dates back to November. Initiating check for updates in the client does not install a new version. Up until November, updating worked fine.

     

    logs.txt tells me:

     

    Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Checking for update from /package/desktopclient/update/1.3.00.30866/windows/x64?ring=general 
Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Downloading file from - https://teams.microsoft.com/package 
Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Browser Window HTTP: Get Data HTTP with url:https://teams.microsoft.com/package/desktopclient/update/1.3.00.30866/windows/x64?ring=general 
Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Browser Window HTTP: Push url in request queue:https://teams.microsoft.com/package/desktopclient/update/1.3.00.30866/windows/x64?ring=general 
Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Browser Window HTTP: Download URL:https://teams.microsoft.com/package/desktopclient/update/1.3.00.30866/windows/x64?ring=general 
Fri Jan 22 2021 10:01:07 GMT+0100 (Central European Standard Time) <14096> -- info -- Downloading Browser Window HTTP:x64.json 
Fri Jan 22 2021 10:01:08 GMT+0100 (Central European Standard Time) <14096> -- info -- Browser Window HTTP: Resolving. Download completed for:x64.json 
Fri Jan 22 2021 10:01:08 GMT+0100 (Central European Standard Time) <14096> -- info -- App up-to-date

     

     

    • ChristianBergstrom's avatar
      ChristianBergstrom
      Silver Contributor
      Jan 22, 2021
      Any specific new setting or feature you’re missing? You don’t necessarily have to use a newer released version as most updates happen backend. In my case though I had to force a version update as I was missing them.
      • BrechtMo's avatar
        BrechtMo
        Copper Contributor
        Jan 22, 2021

        ChristianBergstromI'm not missing any functionality but I find it strange that it doesn't update a version dating back to November. Even triggering the update process in the client does not update it.

         

        Microsoft states that clients older than three months won't be able to access the service. But if the client which is supposed to update automatically doesn't update and thinks there is no update available, I might have a problem.
        https://docs.microsoft.com/en-us/microsoftteams/teams-client-update

Resources