Hi All, I'm wondering if anyone has eperienced the following issue, & resolved it.
We are part of an MS Teams pilot group, and have started to use Teams, but have noticed a very strange issue on daily start of the application. On startup every morning, we get Teams notifying us that there is a newer 64-bit build avialable - which is useful.
So - we have (manually) downloaded the 64-bit version from the MS website (https://teams.microsoft.com/downloads), and installed this (using the relevant permissions). This now shows us that we are running the latest 64-bit version, updated this morning.
All OK so far...but, when we restart our systems the following morning - the process repeats. It appears that clicking on the Teams Desktop link starts the Squirrel Updater, using the following command:
D:\Users\\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe"
When this is run, the original (old) 32-bit Teams Install magically reappears, complete with the message about a later 64-bit build, and we have to repeat the process.
For information, Teams is not installed or managed by our corporate SCCM Package Manager, so we've ruled this out as a posisble install/revert source. There are no AD policies applied that affect MS Teams, and we have also ruled out AV package issues. This happens on both Windows 7 & (pilot) Windows 10 systems.
Any assistance will be greatly appreciated, as this is halting the pilot testing, & will affect wider rollout.
We're using a combination of Windows 7 & 10, both Enterprise 64-bit. We
can confirm that the issue only happens in the mornings (following full
restarts), & not after closing & reopening the application. We have no
other applications that show this behaviour (even WhatsApp, which uses
the same updte mechanism). It's a mystery.
**SOLVED** This issue was traced back to computer policies & SCCM - we were not aware that the machines in the test groups were assigned to differing domain policies, linked to new SCCM groupings. The revert was being caused by a 'test' version of the 32-bit Teams installation being published to the new SCCM group in error. As soon as this was identified, the policy was amended, and the SCCM package removed, & the issue was resolved.