Forum Discussion
Outlook (365) Need Password - Issue
- Hi Muhammed,
Add the Registry key as advised in the article
We've been seeing this for more than 6 months sporadically and again same for one computer today. There was no recent password change but suddenly behavior as described here. Adding this key and setting it to 1 fixed the issue with no reboot. We're seeing this reported by a very small number (half or a quarter percent maybe?) of the clients that we manage.
Best, Chris
I tried all the solutions on this thread and it was only when I attempted to add the AAD.Broker plugin that I got a meaningful error message, namely that the Web Account Manager service was not running. I started this and then the password dialog correctly appeared and I could sign in (to Word 365 in this case.
Hope this helps someone.
I had three machines with this same problem, and I too, followed all of the suggestions and spent countless hours over three years with multiple support techs. One of those machines is now a Win11, and the prob is gone, but the other two I have just gotten into the habit of restarting them every other day. I look forward to trying out your suggestion too.
Can you provide any more detail on your solution?
Thank you.
- I have a machine doing the same thing - affects Teams and Outlook. They're on separate accounts, so I don't know if that's possibly connected. One thing that *is* strange is that BackBlaze (cloud backup service) quits updating/running hourly backup checks at the same time that "need password" bug shows up or "sign in" in Teams.
I've tried the registry "fixes", no improvement. I've deleted the AADbroker files, no help there either. This is a very frustrating issue, and feels like some background cryptographic service is failing after a few hours or days. Of course, no help in event viewer either, nothing of use is visible there. I'll check next time BackBlaze quits and look at event logs around that time, maybe there will be something more useful, but nothing shows up in event log when "need password" shows up in Outlook or Teams refuses to work with my account.Okay, so here's a real head-scratcher. I tried both registry fixes, deleted AADbroker, all to no avail. BUT - I deleted both registry entries described in the "fixes", and now the system has been flawless ever since. What?? No issues in Teams, no issues in Outlook. Uptime is now 10 days. Most I could ever get before was about 3 days before one of the Microsoft services would quit. I have no way to tell if this actually corrected it or not, but if the "fixes" don't work for you, try them, and then remove those two registry keys. Who knows, maybe it'll break on the next reboot, but for now, the problem is solved. I still do run into some pretty massive memory leaks, where Explorer consumes about 1.6 GiB of RAM, but at least it runs stably.
I have been following this thread and have tried everything mentioned. My customer, with the registry adds, goes down every 2 weeks (give or take a day). Reboot usually brings him back. Got him back up today so in a couple of weeks, if this happens again, I'll remove those registry edits. Crazy problem...
