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 added the exclusions in out av solution (even though it hasn't detected anything in that folder) and deleted "C:\Users\<username>\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy" for every user that had this problem. After that, outlook asks for the password one time and works just as it should.
I have been working on this problem for almost a year now and going through some of the possible solutions found here including yours. Thankfully I came across this thread and was able to show my clients that it is indeed an issue that many are struggling with. My main client experiencing this, the issue occurs sporadically. He will run fine for a week... even two or three and then boom, he opens outlook and at the bottom, it says it is not connected to exchange and that it "Needs Password" yet we don't have the ability to enter a password. The quick solution is a complete system reboot and he is back up for maybe another week or two. I have applied this suggestion (removing \microsoft.aad.brokerplugin) today. I'll know in a few weeks if it worked or not.
- Thank you. I have tried so many things with the tech reps and nothing has worked permanently. I look forward to hearing if your solution works long term.
- Several months ago I reinstalled windows 11 and that fixed the issue. No more "Needs Password" and constant rebooting.
MonikaS0913 thanks for the suggestion. Unfortunately this clients pc won’t run Win11. They are in the process of budgeting for new systems so here is hoping the problem goes away once they do. Crazy thing with this issue is, everyone else with the same exchange settings etc., does not experience this issue. Having said that, one user had it appear once and it has never returned for them since. Spent hours trying to see differences… quite a rabbit hole.
