"Windows needs your current credentials [...]" pop-up still there after group policy update

Question

_{Thursday, November 7, 2019 10:35 AM}

Hello, 

I hope here is the good place to post my issue, I tried on MS community but they suggested me to post it here.

I currently run on Windows 10 and I connect to my user session through my company's AAD and I have always had this pop up "Windows needs your current credentials. Please lock this computer, then unlock it using your most recent password or smart card." that is now driving me crazy, it pops twice everytime I log on my session, so at least 10 times a day.

I disabled the "Connection with PIN code" and "Always wait for network [...]" group policies but I can still connect via pin code to my session (even after reboot) and the pop up is still there.

If you have any solution I would be very grateful.

Best regards,
Charles

All replies (2)

_{Friday, November 8, 2019 2:46 AM ✅Answered}

Hello Charles,

From my search, some users’ AAD joined devices were prompting for credentials each time the device was unlocked. As soon as they changed the DNS settings to using Google instead of their internal DNS, problem went away. You could try this method.

Source:

https://www.reddit.com/r/Intune/comments/aha7cc/windows_needs_your_current_credentials_anyone/

In fact, for AAD environment question, the best place you can post is here

https://techcommunity.microsoft.com/t5/Azure-Active-Directory/Windows-needs-your-current-credentials-Loop/m-p/183250

You will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn. 

Thanks for your understanding and cooperating.

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, November 21, 2019 10:16 AM}

I just changed it and it seems to be working, thank you so much !!