Stuck in a login loop after password change
I recently change my system password, with MS Teams is already up and running in the background. I open Teams to check new messages, and it locks the app with the pop up "Can you please sign in again? Sorry for any inconvenience. Login Now"
I click Login Now but all it does is restarting MS Teams and show me the same message. I am unable to re-authenticate. I've tried restarting the application, that didn't work.
I had to right click on the systray icon to logout and re-login. I should be able to re-login when the app prompted "Login Now"
Mahesh HS commented
Still facing this problem, solutions highlighted below is not working :(
Mobile app working fine , but in laptop it's killing me
John Barela commented
Having to uninstall, force stop, or any other similar nonsense action is unacceptable. This is not a new problem.
Brian Walker commented
Anyone have a solution for mobile app?
UPDATE: Reinstalling the app apparently circumvents this issue. I also have Outlook app installed and Password Reset worked ok there. I was wondering why teams app would automatically be reset at the same time. After reinstalling the Teams app it logged me in without 2nd factor auth. idk... flaky... goes with the territory.
Faced the same problem today, though not after resetting Password.
Instead it happened to me when my Multi-Factor Authentication prompted me to allow it.
I have had this happen to a colleague before and followed Eric's steps from July 3rd which worked.
A quicker alternative that worked for me this time was to:
- Wait until it said there was an issue logging in
- Right-click on the Icon in the System Tray and select 'Sign Out'
- Teams then prompted me for Credentials and it logged in fine.
Yes we have a work-around, but why is this still not fixed after more than two years?
Some of us were perfectly happy using Skype for Business but Microsoft forced users across to Teams with glaring bugs like this still in production.
Gloria Tapp commented
The solution offered by Eric on July 3, 2019 worked for me.
Thank you Eric. It did not go exactly as you specified, but it got me out....and back in. Thank you sir.
just ran into this
first pwd reset...
I am shocked how this behavior is still unfixed since 2017!!!!
J A commented
Thank you!! I am appalled by this UX oversight from MS
Props to Eric. If I could upvote I would. His solution worked perfectly.
Thank you Eric, that worked for me...
I guess that knowledge is going to make me now the 'go-to' person in my office!!!
I used the solution provided by Eric and it works no problem. Cheers
foolproof SOLUTION based on all your comments, that I came up with because well I got the same issue:
1) close / kill teams.exe
2) delete all msteams_adalsso/* in "Manage Windows Credentials"
3) start teams but do not enter a password, close (red cross) the password popup window
4) Teams windows will update saying smth went wrong and THERE you have sign out link
5) clik on sign out, then you will have access to the original sign in window
6) click log in button, then fill in you password in the password popup window
This step by step solution is guaranteed to work
Add another disgruntled user to the list.
Chris Soukup commented
This issue has started to pop-up more often in the last days to to a password change reminder. Meanwhile we figured out two dirty-hack solutions:
1. In Windows "Credential Manager" we deleted all "msteams_adalsso/..."* entries so the client lost it's sing-in information - there are about 20+ of them ! (*)
2. Or...during the start sequence of the native Windows MS Teams client we used th singn-out function of the system tray icon (needs to be well timed)
(*) I'm actually wondering why the client needs to create soooo many entries (more that 20) in the Credential Manager. Most of them are time stamped "Modified today"
Jon C commented
This just happened to me as well...here I was so excited to finally get rid of Skype and all it's flaws and now this! I thought I would vent while I reinstall per the instructions below. : )
Ryan Spooner commented
This is one of the main infuriating parts of Teams and affects a few of my users every week. Only way I've found to fix it is to uninstall and reinstall the Teams application.
Add to that the complete and utter ridiculousness of making the MFA enrolment process incompatible with Internet Explorer (IE users just get "Unexpected Error" messages) so if a user needs to re-enrol in MFA for some reason and they are a Windows 7 user with only IE installed, they can't and IT have to them go down and install Chrome.
It seems Microsoft can't even get the basics right, yet we're getting the ability to react to a post with a love heart. Nice to see they have their priorities right.
Sam Boling commented
Howdy from 2019! This still affects Microsoft Teams 1.2.00.13765.
Yep me too, thanks sam
what a good product
the systray logout worked for me. But yes, goofy this still exists.
Oh wow - just got hit with this - how crazy that a simple bug like this exists after a few years of users changing passwords.