Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)
SOLVED

Teams Install reverting from 64-bit to 32-bit every morning - why?!

%3CLINGO-SUB%20id%3D%22lingo-sub-143854%22%20slang%3D%22en-US%22%3ETeams%20Install%20reverting%20from%2064-bit%20to%2032-bit%20every%20morning%20-%20why%3F!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143854%22%20slang%3D%22en-US%22%3EHi%20All%2C%20I'm%20wondering%20if%20anyone%20has%20eperienced%20the%20following%20issue%2C%20%26amp%3B%20resolved%20it.%20We%20are%20part%20of%20an%20MS%20Teams%20pilot%20group%2C%20and%20have%20started%20to%20use%20Teams%2C%20but%20have%20noticed%20a%20very%20strange%20issue%20on%20daily%20start%20of%20the%20application.%20On%20startup%20every%20morning%2C%20we%20get%20Teams%20notifying%20us%20that%20there%20is%20a%20newer%2064-bit%20build%20avialable%20-%20which%20is%20useful.%20So%20-%20we%20have%20(manually)%20downloaded%20the%2064-bit%20version%20from%20the%20MS%20website%20(%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2Fdownloads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2Fdownloads%3C%2FA%3E)%2C%20and%20installed%20this%20(using%20the%20relevant%20permissions).%20This%20now%20shows%20us%20that%20we%20are%20running%20the%20latest%2064-bit%20version%2C%20updated%20this%20morning.%20All%20OK%20so%20far...but%2C%20when%20we%20restart%20our%20systems%20the%20following%20morning%20-%20the%20process%20repeats.%20It%20appears%20that%20clicking%20on%20the%20Teams%20Desktop%20link%20starts%20the%20Squirrel%20Updater%2C%20using%20the%20following%20command%3A%20D%3A%5CUsers%5C%3CUSERID%3E%5CAppData%5CLocal%5CMicrosoft%5CTeams%5CUpdate.exe%20--processStart%20%22Teams.exe%22%20When%20this%20is%20run%2C%20the%20original%20(old)%2032-bit%20Teams%20Install%20magically%20reappears%2C%20complete%20with%20the%20message%20about%20a%20later%2064-bit%20build%2C%20and%20we%20have%20to%20repeat%20the%20process.%20For%20information%2C%20Teams%20is%20not%20installed%20or%20managed%20by%20our%20corporate%20SCCM%20Package%20Manager%2C%20so%20we've%20ruled%20this%20out%20as%20a%20posisble%20install%2Frevert%20source.%20There%20are%20no%20AD%20policies%20applied%20that%20affect%20MS%20Teams%2C%20and%20we%20have%20also%20ruled%20out%20AV%20package%20issues.%20This%20happens%20on%20both%20Windows%207%20%26amp%3B%20(pilot)%20Windows%2010%20systems.%20Any%20assistance%20will%20be%20greatly%20appreciated%2C%20as%20this%20is%20halting%20the%20pilot%20testing%2C%20%26amp%3B%20will%20affect%20wider%20rollout.%20Pete%20Dunn.%3C%2FUSERID%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-143854%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147265%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Install%20reverting%20from%2064-bit%20to%2032-bit%20every%20morning%20-%20why%3F!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147265%22%20slang%3D%22en-US%22%3E**SOLVED**%3CBR%20%2F%3EThis%20issue%20was%20traced%20back%20to%20computer%20policies%20%26amp%3B%20SCCM%20-%20we%20were%20not%20aware%20that%20the%20machines%20in%20the%20test%20groups%20were%20assigned%20to%20differing%20domain%20policies%2C%20linked%20to%20new%20SCCM%20groupings.%20The%20revert%20was%20being%20caused%20by%20a%20'test'%20version%20of%20the%2032-bit%20Teams%20installation%20being%20published%20to%20the%20new%20SCCM%20group%20in%20error.%20As%20soon%20as%20this%20was%20identified%2C%20the%20policy%20was%20amended%2C%20and%20the%20SCCM%20package%20removed%2C%20%26amp%3B%20the%20issue%20was%20resolved.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143903%22%20slang%3D%22en-US%22%3ERE%3A%20Teams%20Install%20reverting%20from%2064-bit%20to%2032-bit%20every%20morning%20-%20why%3F!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143903%22%20slang%3D%22en-US%22%3EWe're%20using%20a%20combination%20of%20Windows%207%20%26amp%3B%2010%2C%20both%20Enterprise%2064-bit.%20We%20can%20confirm%20that%20the%20issue%20only%20happens%20in%20the%20mornings%20(following%20full%20restarts)%2C%20%26amp%3B%20not%20after%20closing%20%26amp%3B%20reopening%20the%20application.%20We%20have%20no%20other%20applications%20that%20show%20this%20behaviour%20(even%20WhatsApp%2C%20which%20uses%20the%20same%20updte%20mechanism).%20It's%20a%20mystery.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143866%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Install%20reverting%20from%2064-bit%20to%2032-bit%20every%20morning%20-%20why%3F!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143866%22%20slang%3D%22en-US%22%3EVery%20strange%3A%20what%20setup%20do%20you%20have%20in%20regards%20of%20OS%3F%20I%20have%20never%20seen%20those%20issues%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115077%22%20slang%3D%22de-DE%22%3ERe%3A%20Teams%20Install%20reverting%20from%2064-bit%20to%2032-bit%20every%20morning%20-%20why%3F!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115077%22%20slang%3D%22de-DE%22%3Eofrfnen%3C%2FLINGO-BODY%3E
New Contributor
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. Pete Dunn.
4 Replies
Very strange: what setup do you have in regards of OS? I have never seen those issues
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.
best response confirmed by Peter Dunn (New Contributor)
Solution
**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.