Windows local account locked after lunch on Lenovo ThinkPad T14Solved

Participant
Discussion
4 weeks ago Sep 28, 2026

One of our Windows devices is a Lenovo ThinkPad T14 using a local account. The user says that after stepping away for lunch, they try to unlock the laptop and get: “The referenced account is currently locked out and may not be logged on to.”

A reboot did not immediately fix it, but after several more attempts and waiting a bit, the login worked again. I checked Hexnode Action History but did not see any warning or failed action recorded for the device.

The laptop has a fingerprint reader and camera, but I’m not sure whether the user actively uses Windows Hello. Could biometric login or Lenovo presence sensing cause a local Windows account to lock like this?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 28, 2026
Marked SolutionPending Review

Hi @akemi,

This can happen on Windows devices using local accounts.

The message “The referenced account is currently locked out and may not be logged on to” usually appears when Windows detects multiple failed sign-in attempts while the device is locked. Since this is a local Windows account, the lockout may clear automatically after the configured cooldown period, which is why the user could sign in again later.

On Lenovo ThinkPad models with fingerprint, IR camera, or presence-sensing features, background authentication attempts can sometimes contribute to this behavior. For example, Windows Hello facial recognition, fingerprint authentication, or Lenovo Presence Sensing/Smart Assist may repeatedly attempt sign-in when movement is detected near the device.

Recommended checks:

  1. Open Settings > Accounts > Sign-in options and temporarily disable Windows Hello face or fingerprint sign-in.
  2. Open Lenovo Vantage, go to Smart Assist, and temporarily disable features such as Zero Touch Lock or Presence Sensing.
  3. Open Credential Manager > Windows Credentials and remove stale or expired credentials that are no longer required.
  4. Ask the user to manually lock the screen with Windows + L before stepping away.

Hexnode Action History may not show anything in this case because the lockout is caused by local Windows authentication attempts, not by a Hexnode remote action or policy execution.

Regards,
Sienna Carter
Hexnode UEM

Save