Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 13, 2015 5:06 PM
I just upgraded to Windows 10 and how I am running into a strange issue. Every so often I will get a windows Authentication prompt in the IE window and a windows Alert "Windows needs Your Current Credentials: Please lock this computer, Then unlock it using your most recent password or smart card". If I immediatly lock my PC and unlock it I am fine but If I wait then it locks out my Active Directory Account. This did not happen on Windows 7,8 or 8.1. My event viewer under security is only throwing generic errors of
Application:
ID 0: ARC.EventSource
Security:
ID 4673: Sensitive Privilege Use
ID 5152: Filtering Platform Packet Drop.
I cannot find any one else having this issue on the web. My partner at work is experiencing the same thing.
Any ideas on how to troubleshoot would be great.
All replies (11)
Friday, August 14, 2015 9:31 AM ✅Answered
Hi,
Based on Event ID 4673 and 5152, it’s difficult to specify the lock out reason. We may try to narrow down this problem step by step:
Try other domain account on this computer and confirm that if this only occurred on specific user account or computer.
If other user account has the same problem, try to restart the computer in safe mode and clean boot, to identify if a 3rd party process has effect on this.
If problem only happen on specific user account, you may try to change the password.
More reasons that may cause account lock out you may reference link below:
https://technet.microsoft.com/en-us/library/cc773155(v=ws.10).aspx
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, August 19, 2015 7:42 AM ✅Answered
Hi,
Thank you for your added instructions. I will try to reproduce this problem on my test environment, and feedback this problem to related department if necessary.
Besides, since Windows 10 is released recently, you may provide the feedback/suggestion with built-in feedback app, this might be helpful for improving the product.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Friday, August 14, 2015 12:16 PM
My situation is identical. I had no issues running any previous version of Windows. My Windows 10 installation (enterprise) was a clean install (not an upgrade). No account information has changed since doing the installation - my password hasn't changed since before this computer was joined to the domain. I have not installed any 3rd party software that should be causing the lockout, and I have verified that there are no saved passwords in any browsers. Historically, when something has a bad password cached it simply locks the account, Windows doesn't warn me that it needs my current credentials.
I just changed my password and will see if that changes the behavior.
Ralph Bley
Friday, August 14, 2015 3:59 PM
Changing my password did not resolve it - my account got locked about 2 hours ago, and I received the "windows needs your current credentials" prompt just now.
Ralph Bley
Friday, August 14, 2015 5:52 PM
FWIW, I found this article. It may be a workaround, but it is not a long-term fix.
Ralph Bley
Friday, September 11, 2015 7:53 PM
I also have this exact same problem...
After a bit my AD account is locked out. I have to RDP to DC and unlock my account.
About 2 - 3 times a day.
it's really a pain.
Monday, October 12, 2015 7:30 AM
Same issue here. And we are 3 people at work with the same issue now.
Wednesday, August 3, 2016 6:00 PM
in AD, for that account, Enable "Do not require Kerberos Preauthentication".
Wednesday, August 3, 2016 6:03 PM
IN AD for that user:
Enable "Do not require Kerberos Preauthentication"
Thursday, August 4, 2016 6:25 PM
Weird. I had this problem with one of the very early versions of Windows 10 (prior to 1511), but some update fixed it.
That stinks that it is back.
Thursday, February 23, 2017 2:59 PM
Your workaround is a security concern