Bits of .NET

🪟 The Face That Windows Suddenly Stopped Recognizing

Face recognition sign-in is tied to an enrollment that depends on the specific camera driver and the biometric service’s running state at the time it was set up. A Windows update that replaces the camera driver, or that restarts the biometric service in a different configuration, can leave the stored enrollment pointing at a setup that no longer matches what is actually running, so sign-in fails or drops straight to a PIN prompt after every scan attempt – not because your face changed, but because the driver or service state the enrollment depended on did.

🔎 The Problem

Symptom:
  Face recognition sign-in fails or drops straight to a PIN prompt
  after every attempt, right after a Windows update finished
  installing - the infrared camera still shows a live preview in
  Settings, so the hardware itself appears to be working fine.

Settings > Accounts > Sign-in options > Facial recognition is where
the existing enrollment lives, and it does not automatically re-bind
itself to a camera driver or biometric service state that changed
underneath it:
  - Device Manager: check the Windows Hello / infrared camera entry
    specifically (not the regular webcam, if the laptop has both) for
    a driver flagged as updated around the same date recognition
    stopped working
  - services.msc: "Windows Biometric Service" can end up running in a
    stuck or inconsistent state after an update, which makes even a
    brand-new enrollment fail the same way the old one did

✅ Fix: Remove and Recreate the Enrollment After Checking the Driver and Service

• Remove the existing facial recognition enrollment entirely and set it up again from scratch – a fresh enrollment forces it to re-bind to whatever camera driver and biometric service state is current after the update, rather than trying to reuse a now-stale one.
• Check Device Manager for the infrared or Windows Hello camera specifically for a driver flagged with an error or showing as recently updated – rolling back or reinstalling that specific driver often resolves it without touching the enrollment at all.
• Restart the Windows Biometric Service before re-enrolling – a service running in a stuck or inconsistent state after an update can make even a brand-new enrollment fail the exact same way the old one did.

⚠️ Why This Is Easy to Miss

• The failure looks identical to a camera hardware problem or simply not being recognized anymore, so it is easy to spend time adjusting lighting or camera angle before realizing the enrollment itself, not the camera’s image quality, is what actually broke.
• Windows Update does not surface anything saying this update may affect your face recognition enrollment, so there is no obvious link between the update that just finished installing and recognition suddenly failing right afterward.