This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Using Version 1.4.00.2879
All the correct settings are in place - removed the tick next to 'On close; keep the application running'
But on exit the app closes, the task bar icon remains active and processes are still listed on the Task Manager.
One thing I have noticed is that there is now a menu option in that app called 'Accounts & Orgs'
I have not logged on with any other accounts and the menu only lists the current organisation I am using.
Not sure if these are linked!
Any ideas on how to get the teams app to exit fully and close all processes?
Thanks
Derek
For clarity - this behaviour happens if you press the red cross.
Also if you go to the task bar icon and select quit - it does then close down correctly.
Interestingly if the app is running and you quit using the task bar icon, it does close fully first time.
It appears that it is when a close using the red cross is attempted, it results in an incomplete shutdown.
![](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(259.20000000000005, 21%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECA%3C/text%3E%3C/svg%3E)
I have noticed the same behavior in the past few weeks. The tray icon remains after closing the app window and several Teams processes remain in Task Manager. Unchecking the box that says "On Close, Keep the application running" appears to be ignored in the recent builds.
@mrshearer-6228 , @Dzialas, Kai-Uwe , @Trevor Buley , @Ahsan Ali ,
It seem that we take a bit more time to handle this issue.
We recommend you open a ticket to get more efficient support. The support engineer will collect your backend log file and analyze this problem exactly.
Meanwhile, we will continue work on this issue. Any update I will post here.
Thanks for your understanding.
![](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(214.4, 67%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Teams Version: 1.4.00.11161
Windows version: 20H2, build 19042.985
Logged into 2 orgs
Observed Behavior:
MS Teams not shutting down after user clicks on close button (X).
Said action correctly shuts down window frontend however it will transfer MS Teams to background processes.
This causes partial functionaliy loss (main window frontend is never re-created yet the app responds to context menu > Quit).
This is with disabled "run on background".
![](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(124.80000000000001, 6%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
can confirm that this is still happening in March 2022. SO ANNOYING
i didnt even know that exiting through the taskbar worked. microsoft get on your game.
![](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(12.8, 39%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGR%3C/text%3E%3C/svg%3E)
Thanks to user Shaaaaazam on Reddit for this fix that worked for me:
"Run in compatibility mode for win7"
Link to original Reddit post: https://www.reddit.com/r/MicrosoftTeams/comments/munus6/teams_wont_reopen_after_closing/gv7uk67/
User was on 21H2 and still having the issue.
So Teams was working properly but like a nasty infection, this behavior seems to be back, at least in version 1.6.00.11655. :rolleyes:
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
[FIXED]
In 2023, this issue is fixed by downloading the latest Windows client at the URL below and installing it :
https://statics.teams.cdn.office.net/production-windows-x64/1.6.00.22378/Teams_windows_x64.exe
For further details or alternative OS version, see methods described at the following URL:
https://techcommunity.microsoft.com/t5/microsoft-teams/force-teams-desktop-client-update/m-p/2056566
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
2 deleted commentsComments have been turned off. Learn more
![](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(153.6, 52%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDK%3C/text%3E%3C/svg%3E)
Same here with 1.4.00.8872 (64-Bit) on Win10 20H2 (64-Bit).
Checkbox "On close; keep the application running" is unchecked and on close tray-icon and task remain.
![](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(182.40000000000003, 28.999999999999996%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Can confirm it is still happening as of 29/04/2021.
MS Teams version 1.4.00.8872 (64Bit).
Win 10 20H2 (Build 19042.928).
![](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(265.6, 21%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Yes it's still there, I'm using teams (Version: 1.4.00.8872 (64-bit)), and it needs to close the teams from the task manager to fully close it.
![](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(96, 90%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Same issue here. Pleae fix this asap!
![](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(153.6, 20%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIG%3C/text%3E%3C/svg%3E)
Yes still occurring 14 July 2021 and 5 months since first post.
What is ETA please for update to stop this occurring/ to fix the broken option to close on exit.
![](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(304, 35%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Does seem like this will be changed and operate in the way a user would expect. i.e. Selected close on exist, so "close on exit", right!
I contacted Microsoft support and they advised ...
After confirming with several colleagues, we've determined that this seems to be an intended feature implemented in newer versions of Teams 64bit.