Teams downloading NUPKG files in user download folder
Teams at every startup downloads the nupkg package in the username download folder instead of %localappdata%\Microsoft\Teams\packages
Can someone tell me what the fix was for this? do we need to download an update? we are having this happen on a VDI and it is filling up their download folder to the point they can no longer log into their desktop.
From Microsoft Answer:
We had this issue, and put a case in with Office 365 support. According to the latest notes we received this was an issue on the backend and has been resolved. We did test, and confirm that the nupkg files are not being downloaded anymore and that teams is now successfully updating.
Just letting everyone know, so if you are having this issue - it might be worthwhile to test again - or open a case (in case it is a per tenant issue)
Since June 12, I am up to 31 instances of the Teams-1.3.00.13565-full.nupkg file in my downloads folder. There is also a copy in %AppData%\Local\Microsoft\Teams\packages. This matches the installed version.
It has now been 6 weeks since the initial post in the thread that led me here (https://answers.microsoft.com/en-us/msteams/forum/all/teams-downloading-nupkg-files/b33078ba-2aa9-4d75-9d61-5bcb36a49684?page=1) and there appears to be no solution to the issue. I am now getting 2 to 4 copies of this file every day. Ridiculous!
This report only has 16 votes, but on the link in the original posting 95 people report having the same question, which suggests it is more widespread than the 16 votes suggest.
I also have this issue, I keep seeing a popup reporting that 'Teams Downloaded' or something similar and I see multiple nupkg files (Teams-1.3.00.13565-full.nupkg' in my case. I don't see any errors in the teasm logs.txt file though. This has been going on for a few weeks now. I am on version 1.2.00.32462 so presumably the Teams automatic update is failing, it was last updated 2nd June 2020.
Using this as guidance: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot-installation
Log files can be found in %AppData%\Microsoft\Teams
The file Logs.txt should show your URL. I searched for the word "failed" to find mine, but it's not clear exactly where is the auto-update URL. I have the following:
"Downloading file from - https://teams.microsoft.com/package ......
Browser Window HTTP: Get Data HTTP with url:https://teams.microsoft.com/package/desktopclient/update/1.2.00.32462/windows/x64?ring=general ......
Browser Window HTTP: Push url in request queue:https://teams.microsoft.com/package/desktopclient/update/1.2.00.32462/windows/x64?ring=general ......
Browser Window HTTP: Download URL:https://teams.microsoft.com/package/desktopclient/update/1.2.00.32462/windows/x64?ring=general ......
Downloading Browser Window HTTP:x64.json ......
Browser Window HTTP: Resolving. Download completed for:x64.json ......
From this, I'd suspect if you blocked "https://statics.teams.cdn.office.net/*" then it wouldn't download any more. However in theory its only a matter of time before our Teams clients are out of date and won't work any more!!
Interestingly, it seems that after trying these 'delta' updates, it tries to download the full installer and it states this FAILED, even though the file is appearing in Downloads, fully completed:
-- info -- Browser Window HTTP: Get Data HTTP with url:https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.13565/Teams-1.3.00.13565-full.nupkg
-- error -- Browser Window HTTP: Reject URL in request queue. URL:https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.13565/Teams-1.3.00.13565-full.nupkg
-- info -- File download error - Request with url: https:// is present in queue
-- error -- update download failed
-- error -- Download package failed
What are the Teams update URLs to block on the firewall?
Any solution to block the auto download nupkg files? This will causing hdd sizes full if keep using it for long term.
The certificates on the update.exe appear to have both expired with date 02/05/2020 (UK format - 2nd of May). Could this be causing an issue? That would tie in with about when I started to see this problem.