This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 90%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
I am trying to remove an old version of Teams machine-wide installer and replace with a new version. After following steps in https://learn.microsoft.com/en-us/microsoftteams/msi-deployment (refer "Clean up and redeployment") I am finding that when the user logs back in, Teams is updated to the new version installed - however the "Microsoft Teams" shortcut is missing from %AppData%\Microsoft\Windows\Start Menu\Programs
I have viewed the squirrelsetup.log within %appdata%\squirreltemp however there are no obvious errors here.
I have looked at the %appdata%\Microsoft\Teams\logs.txt and noticed there is no entry of the following:
So perhaps this is what is missing, only I am unsure how to force this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Have you enable the following settings in your Registry Editor?
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run]
"TeamsMachineInstaller"=-
In this case, it also discuss about this question. For more details, you could refer to:
Thanks for the advice however our computers have the following setting for that reg key:
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run]
%ProgramFiles%\Teams Installer\Teams.exe --checkInstall --source=default
Which I believe is the default for the installation of Teams.
Thanks for your feedback. I will check if there is any other setting affect it.
Hi ,
This may be caused because Teams is never uninstalling correctly. Have you checked this article:
https://learn.microsoft.com/en-us/microsoftteams/troubleshoot-installation
-----------------------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept as answer--
As a workaround, you may use the old MSI file to install and update to the latest version( auto-update is OK if you didn't disable it).
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
I have looked at the article troubleshoot-installation to understand any problems during the re-install of the Teams machine-wide. That is where I got the idea (in original post) of checking %localappdata%\squirreltemp\squirrelsetup.log and %appdata%\Microsoft\Teams\logs.txt
with only the following entry seemingly suspicious in logs.txt
Executing squirrel command: --createShortcut=Teams.exe
I did notice that on 2 test computers for this after several days the "Microsoft Teams" shortcut is now there in the start menu.
Perhaps after the User has downloaded a Teams Update, the "Microsoft Teams" shortcut is recreated? I will perform some more testing and advise.
No thank you @JimmyYang-MSFT it appears that so far further testing is showing basically positive results, usually immediately.
Thanks for your reply and helpful to see the test result is no issue! If the reply is helpful to you, you can try to mark it as a answer to close the thread.
