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"
ASININE that this is still happening to me, today, December 9, 2019.
Fix it Microsoft! Chop Chop!
Bill P commented
Two and a half years and this is STILL an issue. Seriously?!? C'mon, Microsoft, fix your broken $h!t...
Himmat Solanki commented
What worked for me
"Uninstall MS Teams, & Install it again"
I wasted couple of productive hours on the below solutions, hence suggesting others not to waste.
Nothing of below worked
1) Sign out from system tray (two times) and then login screen appears but it is not asking for password
2) Deleting %AppData%/Roaming/Teams/Cache (or Application Cache) folder, no effect
3) Removing all MS teams entries from the Credential manager(I have removed almost all entries which seems like used by MS Teams), but not a success
This right-click solution helped a lot. Thanks. But now its end of 2019, and I see this was reported in April 2017.. thats really lame.
Vincent R commented
After you right click and sign out, you will see the background under the sign in screen go blank. After that happens, go to the icon again and right click sign out and you should get the beginning login screen that asks for your your name and then login. It worked for me, but some of this is pretty quirky. I also flushed my browser history, but that didn't seem to help.
Mike W commented
Thank you so much Dave Poole. Was stuck in the dreaded loop. This was incredibly helpful
thanks for the fix but the fact that this has been an issue for so long and has not been fixed is pretty terrible on Microsoft's part.
Yes the fix is simple but how many regular users will google to find the answer rather than call the helpdesk (hint: ZERO)
Putting Dave Poole's solution at the top again:
"I found an unconventional fix to this:
1. Whilst MS Teams is open, right click in System Tray and hit sign out.
2. You will then be taken to a login page with your email address autofilled. Deliberately enter an INCORRECT email address (.ukk or .comm) and hit sign in.
3. You should then be taken to a different login window, where you have the opportunity to re enter your email, which should then take you to a password window where you can complete your new credentials.
Matthew Brent commented
Still an issue
FYI Deleting the teams cache did NOT work: %AppData%\Microsoft\teams\application cache\cache
Had to log out, opt to sign in as a new account, and then reenter your user name and credentials.
I.e. Dave Poole's instructions from earlier thread posting.
Still an issue, way to stay on top of it Microsoft
Martin Moser commented
fix your **** microsoft.
Riaan du Toit commented
Maybe implement a counter or ticker? So, after maybe 2-3 attempts of the Sing In loop force the app to ask for the password.
In the interim Dave Poole's solution worked and is non-invasive and not "techy". So, most users should be able to attempt it without needing Admin rights or potentially breaking their windows :)
Delete the contents of the MS Teams cache folder:
........and it will work
#DavePoole My Hero!
Dave Poole's solution did it for me as well!
We were experiencing this issue and doing what Dave Poole's recommended work, but wasn't something we would want continue doing. What worked for us was the registry for the office 15 hive, we had originally set for office 2013 users, but since we no longer have 2013 users and on 0365/2016. We changed the value from 1 to 0, and after a change password it doesn't present the login loop any more with teams.
HKCU\SOFTWARE\Microsoft\Office\15.0\Common\ Identity\EnableADAL. REG_DWORD. 0
Dave Poole's solution worked for me as well.
sriraam raja kumar commented
Dave Poole's solution worked