Hello,
I have Azure AD Joined + MDM managed device + Azure cloud MFA enabled for user.
Recently updated PC to the 2004 Feature Update,
After the update cannot fix accounts under "Shared experience settings", the authentication screen appears for less than a second and then disappears and loops many times.
Anyone experience the same issue?
Yesterday got this issue after recent updates on the 1909 version.
Found AAD logs on PC that something related to MFA token renewal + the IE frame not loading correctly. (If MFA disabled, the user MFA and Conditional Access MFA, then all works fine)
I could fix this on 2x PC's only by fully re-building Windows Profile.
So something happening that seems something new...
See here how to deal with Fix Account in Shared Experiences Settings:
https://www.windowsdigitals.com/microsoft-account-problem-notification-message-popup-windows-10/
（Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.）
Feel free to ask back any questions and let us know how it goes. I will keep working with you until it's resolved.
Best regard,
Sylvia
Hello Sylvia,
Thanks for the article, but I don't want to turn it off, I want that it works fine as it was working before the 2004 update.
After the 2004 update, the login screen loops very quick and then stop,
This bring all my Microsoft-Office Apps unauthenticated and I need to authenticate every app manually with MFA.
ok, let us try the methods provided by this link.
https://windowsreport.com/you-need-to-fix-your-microsoft-account/
（Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.）
Best regard,
Sylvia
Hello Sylvia,
I try to follow steps, but none of them fix the issue.
The issue btw is strange, as soon as I click "Fix now" some screen (no text, just a grey-blank screen) shown for a few seconds and disappears and this repeats some 5 times.
Installed new PC without a 2004 update, made the same AAD+MDM, same MFA user, and then updated to 2004, then no issue appears. So maybe it is not the 2004 update issue.
Maybe my question would be here, is it possible that this update could cause this?
Interested because we need to plan to release this 2004 update to 1000+, wondering if similar issues can occur.
I just updated to windows 10 2004 and I'm having this issue too. We also have another end user at our company with the problem. I have a feeling its a bug in 2004.
Anyone ever figure out a fix for this? It's occurring to me right now with Win10 Pro 64-bit 21H1. Thanks!
I have fixed myself last time, try to exclude the user from MFA, wait a few minutes, and test via an in-private session that it is really off, then click on "Fix now", it should stop pop-up, then reboot PC once, then enable MFA back. Then for the test can revoke the MFA session of the user, it should trigger again the "Fix now" from "Shared account experience", if the issue appears again, then try the un-join device, delete user profile from Advanced System Settings (so user folder gone c:\users{username}), and then join device back.
14 people are following this question.
