Hello
Thank you for posting on the Microsoft Community.
The issue you're experiencing seems to be related to account lockout policies, some compatibility settings for Windows 11 and Windows Server 2016. When a user tries to log on after the computer has been inactive for more than 10 minutes, the system displays a "The referenced account is currently locked and may not be able to log in" error. This question is usually related to the following:
- Conflicting account lockout policies
Because you have an account lockout policy enabled (for example, an account is locked after 10 minutes), if a user tries to sign in after the policy is triggered, they may not be able to sign in because the policy is triggered. If the issue is with an individual user, it is possible that the user's account or device is conflicting with the lockdown policy, especially in a new device or operating system environment.
- Windows 11 sleep mode and network connection issues
If the user's Windows 11 computer goes into sleep mode or hibernation, the computer may experience some lag or connectivity issues when he tries to log in, causing the lockdown policy to not sync correctly. Especially in enterprise environments, there may be a delay in the locking and unlocking behavior of Windows computers and the synchronization of domain controllers.
I hope the above information is helpful to you.
Regards
Runjie Zhai