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
We have yet to find a solution to this issue. We are not using Trend Micro. We did add exclusions to our AV, SentinelOne. No change. We've even tried a test PC without AV on it. No change. We can 'resolve' the issue by deleting the C:\Users\username\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy folder when the user is logged off. But we can't keep doing this over and over. This issue is a bane of our Help Desk. Any other thoughts on how to resolve this issue?
peter-supply I have been working on this problem for nearly three years. I have worked with at least four different MS technicians and the only thing they come to is that I need to start over and reinstall the OS from scratch. Obviously, I can't do that, so I am left with having to reboot my desktop computer about every 36 hours.
I wish they could get this resolved.
Brett
Just a heads up that doing a PC wipe and reinstalling windows will not fix the issue. We have brand new PCs that get the issue within a week or two of deployment. Same goes for older PCs that have been wiped.
We encounter this issue in a Citrix server environment. We are using Server 2022 and Office 2021 LTSC. We tried Microsoft 365 Outlook- same problem. We've tried Citrix UPM and FSLogix for account management- neither work to fix this issue. Deleting the C:\Users\username\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy folder while the user is logged out is the only solution we've found. But this is time consuming for everyone. We've worked with Citrix support and Microsoft support- neither have provided a solution. For us, I think the problem involves Microsoft's switch from Azure Active Directory Authentication Library (ADAL) framework-based authentication to Web Account Manager (WAM). No one seems to know how to fix it. Very frustrating.
